Back from the Yards: Gameprints Repair of the 12″ USS Zuikaku

Back in March 2018, when Gameprint & Cryptic started to offer personalize printed Star Trek Online ships, looking exactly how your ship looks in-game. I, like many other Star Trek Nerds, most likely giggled like little school children (come on admit it, you did 🙂 ). So,with the new service being offered. I ordered my flagship, the Tier 6 Fleet Intel Assault Cruiser USS Zuikaku, flagship of the 101st fleet.

Several weeks went by, and in early May 2018, one day the package arrived. I was so excited, as I had been dealing with a lot of things in my personal & work life. Having the model arrive, was a bright spot on an otherwise bad period.

Little did i realize, that i would be most likely one of the first orders, who would experience a major break of their model.

Zuikaku

Needless to say, I was crushed. Barely able to take one photograph before I reboxed everything, and contacted Gameprint to let them know what had occurred, and to also request a repair.

I also informed Reddit/STO, one of the main community locations for discussing Star Trek Online. Thread in hand, I let them know what had occurred

The support I received from them was great. I also got support from the main Cryptic Community Manager Ambassador Kael who contacted Gameprint. In an effort to ensure that this would never happen again to anyone else.

Several days went by, and I organized with Gameprint to have my ship sent back to be repaired. After I turned down their initial offer of them telling me how to conduct the repair myself. It took several weeks to get the package sent off. However, that was no fault of Gameprint or their delivery company. But more the fault of my local delivery company who delayed the send back by 2 weeks.

And so, ship sent back. I waited….

Repairs Underway

June became July, and I communicate back and forth with Gameprint with periodic e-mails requesting updates as to the repair. Then, on July 25th, a new e-mail came in. This e-mail, made me both excited, and worried at the same time.

We are working on your ship at this moment and we managed to cut your ship in half (sound scary but don’t worry she will be fine simple_smile)
We have reprinted the bottom half in tough resin. The modelling team just finished gluing and cleaning the ship. Now it’s in painting.
The phase “cut in half” doesn’t make any ship captain feel good at all. But I trusted the Gameprint team to get the job done.
Then two weeks later, I was informed the ship had been repackaged, and was on her way back to me.
Ship return & Review
A week later, the USS Zuikaku returned home. As one could expect. I was worried. Scared that unboxing her again would show another massive failure or break. Like the USS Reprisal mentioned in another blog, she was extensively protected. One could say over protected. But considering the cost, and the model and customer target base. I was glad.
It also seemed, that the USS Zuikaku incident may have been the trigger for a completely new way of packaging and sending ships to clients. If that hypothesis is true, then I am OK with what happened.
DSCN1706
Ship unpacked, and she looked beautiful. The one slight issue was a slightly bent nacelle. But considering the width of the nacelle struts even in resin (1mm thick, if that) I am not surprised the weight of the nacelles might have caused a slight “bend”.
A better angle, shows the slight “bend” of the nacelle.
DSCN1711
DSCN1721
As you can see, the bend is pretty slight. The nacelle in question that is bent is on the port side of the second picture. The nacelle pylons still feel like they are flexible and can bend and twist. This does not surprise me, even considering that they cut my ship in half, some sections would still need to be flexible in order to have some give.
This is especially true, that while the model is light, the nacelles themselves considering their location and supporting pylons are still a heavy load.
Now, Gameprint mentioned that they cut my ship in half. However, I seriously cannot tell where that occurred. The repair (at least because of my paint job selection) is so well hidden, there are no clues to its probable location.
DSCN1727
Considering how she was returned, a slightly bent nacelle is something I am more than willing to live with.  The timeframe from when Gameprint received my ship, to when the repair was completed seems to be 1 month. But considering how busy Gameprint have been with all their orders, as well as the seriousness of the damage, that timeframe is more than understandable.
Conclusion
I have to say, Gameprint really did their best to ensure my issue was resolved. Additionally, they were pretty responsive when i requested updates about the repair status, as well as requesting updates about what they could do for me regarding options to fix or replace the USS Zuikaku. Or, alternatively the return of the money i paid.
I also didn’t go into detail regarding how this ship looks compared to my in-game USS Zuikaku. This was because this blog was more about the repair & support, than the ship herself.
Thanks to all the Reddit/STO community & especially Ambassador Kael of the Cryptic team for their support and assistance with getting this resolved.
Now the USS Zuikaku is back home, I am going to ensure I have a quiet period. However, knowing this ship, I basically know I am going to be back in trouble again within a week. This ship just seems to attract trouble.
I wouldn’t have it any other way 🙂

Flashback: Deep Space Encounters

OldESD
Earth Spacedock, as it appeared from 2010 until April 2014. Image Credit: RachelGarrett | sto.gamepedia

In 2010, Star Trek Online was a far less forgiving game than the one is played today. Today it is possible to travel through each of the galaxy’s four quadrants in single trips as part of a large, open map. But at the time of the game’s launch, it was a very different story.

At the outset of this opinion piece, I will say: I think Star Trek Online has lost a potentially amazing experience that cannot be repeated again in the game as it exists today. And I shall explain why.

This is my story of how an exercise in dipping my toes into the pool became an eight-year journey that continues today.

In 2010, the galaxy was divided into sector blocks – each of which was level-banded and matched to the levels you were expected to hit when you reached those territories in the course of story missions. This was far more in line with the open worlds of other MMOs: journeying through sector space to your next destination was fraught with risk and danger. Sector space was filled with hostile NPCs who would follow your vessel if you flew too close to them, and drew their attention. Of course, these NPCs were the same level band as the sector block they patrolled. Those around Federation space in the Vulcan sector were low level opponents, while those in the end-game regions around Deep Space Nine and Gamma Orionis were much higher; at levels 40 to 50.

Star_Trek_Online_Galaxy_map
The original sector blocks of Star Trek Online, showing the Alpha and Beta Quadrants, and their discreet divisions. Image Credit: Cryptic Studios, 2011.

Needless to say, for tyro captains in their first Miranda-class light cruiser, venturing (or more accurately, straying) into a sector well outside your level bracket was a hazardous and naively foolish thing to do. You could potentially find your Miranda venturing through Borg space at warp five, while a Borg Cube pursued you at speed better than warp nine. If you were not prepared for this, then what happened next was usually regrettable.

If you were intercepted by these hostile NPCs in sector space, you would be automatically dragged kicking and screaming into an open-instance deep space encounter wherein you would need to defend yourself against enemy ships, and then destroy them.

Either that, or they destroyed you.

And so it was in 2010 that the intrepid and daring Lieutenant James Hawkins of the starship USS Hyperion decided, after defeating the Borg at Vega colony, (ah, yes, the foolish delusions of badassey at level 10) and rescuing the badly-damaged USS Khitomer, that the single most important thing he could do in his fledgling Starfleet carrer was to see the universe and visit the most famous space station in the galaxy: Deep Space Nine.

Deep Space Nine, of course, resided right in the middle of a level-40 True-Way-infested rats nest of Cardassian and Terran piracy called the Beta Ursae Sector Block.

With orders from Spacedock to go investigate some silly Vulcan monastery on P’Jem, Hawkins instead ordered the Hyperion to take a right turn after leaving Earth and thus entered Cardassian space. Immediately, he set a course for Deep Space Nine. It didn’t take long for the ridiculously out-of-place Miranda-class starship to be spotted by Terran Empire starships that patrolled sector space, and it was pulled into a Deep Space Encounter at the sort of odds that even the imperious James Kirk might have thought better of.

Alas, there was no way the badly outdated engines of the Miranda class could escape the Terrans, and Hawkins resolved himself to the simple fact that in his brazen impatience to see Deep Space Nine, he was probably going to be atomized and have his debris scattered over the better part of a sector. Not without a fight, of course. (Indeed, this entire excursion probably began with the words ‘never tell me the odds.)

Fate, however, deigned that better things awaited the tyro Lieutenant.

The young and inexperienced captain couldn’t do much as the first wave of Terran ships that awaited him in this encounter opened fire. Level 40 phasers against a Mark-II uncommon standard shield array need to only fire one or two shots before your ship has sufficient air holes in its engine room (we swear it makes it go faster) to personally wave your head out of the hole and wave a white flag from the safety of a space suit.

Actually, that last part isn’t true. This was a dark age of Star Trek Online that predated the Nukara Strike Force, and thus I am entitled to say that back in my day, we didn’t have these fancy space suits (No, really. EV suits didn’t exist at this point). We had a plastic bag (which is now banned) and a fire extinguisher from ‘Researcher Rescue’. And we had to share the extinguisher.

The point is that my ship was unquestionably exploding, and there was absolutely nothing I could do about it.

As shields failed and the hull was breached, a voice could be heard in the back of Hawkins’ mind. “Sir… there’s another ship coming in…”

I will take a moment in the retelling of this story to make something very clear: This actually happened.

Sweeping in front of the mauled USS Hyperion, a huge level-45 Sovereign-class assault cruiser let fly with more firepower than I thought was ever reasonable for a spaceship to have in a Star Trek game. Beams and torpedoes lanced through the attacking Terrans as the Assault Cruiser put itself between them and the appallingly out-matched Miranda. Before long, the Terrans were destroyed, and the Sovereign pulled alongside the ruined Miranda and began sending over as many engineering teams and hazard emitters buffs as it could find. I received a message from the captain of the Sovereign that was rather blunt. “You shouldn’t be here.”

I wasn’t exactly in a position to disagree.  I’d made a terrible mistake and promptly accepted the Sovereign player’s very kind offer to escort me back to a safer region of space. Dutifully, the kind player did indeed invite me to a team, bumped my level up to 45 to avoid the aggro of the other NPC mobs in Beta Ursae, and took me all the way back to the Sirius Sector Block, and the relative safety of Federation space.

Let it also be said that some of my fondest memories come from the occasions where I got to be the hero, and made some anonymous Star Trek fan’s day just a little bit brighter in deep space.

A couple of years later, Cryptic would finally remove these roving deep space encounters and replace them with the queued system for encounters that we have now. Too many players had decided that random pursuits through sector space were ‘ruining their fun’, and more’s the pity. The encounter of a vastly powerful Sovereign class starship swooping into save a hapless low-level Miranda is the kind of thing Star Trek is made of, and I hold that it’s a terrible shame that players will no longer be able to experience that sort of moment.

I took away one enduring determination from the encounter with that Sovereign. Oh yes… I would have that ship, and then it would be me doing the rescuing. Let it be said that some of my fondest memories in this game from the occasions where I got to be the hero, and made some anonymous Star Trek fan’s day just a little bit brighter in deep space.

That Assault Cruiser – whose name has been unfortunately lost to time – left an indelible impression on the kind of ship I’d want to fly.

That was when a brief look at a game that piqued my curiosity garnered my complete and undivided attention.