STOked Episode 108 is up and available for your podcasting pleasure!
Jeremy from Cryptic (formally from STOked) joins us to chat about up coming game changes, like the ground skill revamp, crafting overhaul, a new weapon you’re going to get your hands on for the holidays, and some more behind the scenes details on the holiday event!
Plus why it took so long to fix Voldemort, and the new bug you can help the STO dev’s track down!
Also: Chris’ thoughts on the Holiday Event, and an important tweak he’d like to see made and he kicks the tires of the new Jem’Hadar player ship!
As far as the issues with lots of people trying to get the race guy's attention, the solutions is ridiculously simple: change instance to the map with the least people on it. Thats what I did every time I raced. Sometimes there were maps with only 2 people on them.
On the note of Voldamore, I know several of us (myself included) did in fact send a bug report with step by step ways to reproduce. I still have my ticket number for my report: 1,181,934
And I was pretty sure it was the shields in your inventory being counted as available pool. I had noticed way back (Season 1?) that each shield item kept track of its shield facings. Putting a damage shield into the inventory would remember it was damaged. However, I had also noticed those shields would also heal over time from what appeared to be the natural shield regen tick. When the Voldamore thing surfaced, I speculated that the heal was not one way and was allowing energy from those shields to be pulled back into the currently equipped shields.
As for the BO thing, I have had that happened to me a few times. I cannot force reproduce it, but I think its related to lag, or at least, UI lag. When it happens to me, it is usually me swapping one BO for another and the UI doesn't seem to update; in fact it initially seems like the game didn't even register the change. But when I go to my power list, I suddenly find I have access to the BO I wanted as well as the one the system has.
If I ever find a way to actually reproduce it, I'll send in a bug report. For now, it just seems to happen randomly due to lag (Maybe a race condition?).