So I got booted out like everyone else, claimed all of my Voyager schematics successfully, then tried three days worth of NX-01 schematics, but only got 2 sets of schematics, and 1 set of I.S.S. Enterprise schematics.
So I got booted out like everyone else, claimed all of my Voyager schematics successfully, then tried three days worth of NX-01 schematics, but only got 2 sets of schematics, and 1 set of I.S.S. Enterprise schematics.
*shrug*
No - not 'shrug'. How many ways can DB **tsk tsk** things up? When was the last time they got something right? I am right on the very edge of getting rid of the game; I am SICK of the incompetence.
And I hoarded 3 e-mails with 120, 100 and another 100 ISS Enterprise schematics waiting for them to automatically convert to NX-class. Once they did (and it clearly showed NX-class and also text indicated so), I assumed the update was through, claimed the stuff ... and didn't get them (probably more ISS Enterprise schematics, but I didn't even bother checking my inventory as I didn't know how many ISS Enterprise schematics I had before I claimed the mail contents).
"Everything about the Jem'Hadar is lethal!" - Eris (ST-DS9 Episode 2x26 "The Jem'Hadar")
they're flipping back and forth for me still. got some of what i wanted and some old.
Jean-Luc Picard: "We think we've come so far. Torture of heretics, burning of witches, is all ancient history. Then, before you can blink an eye, suddenly, it threatens to start all over again."
Hehehe, I exited at 10 and haven't gone back in yet. Because 10am et means in Db'nese
"Some time tomorrow morning we think.."
And 10:30am et means "most likely early afternoon"
That's how I'm gonna try to read all posted times and timers from now on..
"Event start time Thursday Noon
Event End time Monday Noon"
Will translate in my brain to
"Event starts Thursday early afternoon
Event ends Monday...ish, we think !" Lol
Just gotta read the notices like a 90 year old is telling you about them.
"It'll end when it'll end and you'll know it's over when it's over now stop asking me so many questions I have to ignore and get me some *** ***** Jell-O you smarmy *** whipper snappers"
Llap
"Llap ? What's wrong with you ? You can't expect me to give you a lap dance no matter how much Jell-O you bring me ya little freak"
Some update!
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Some update!
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Shan, any comment on the inbox rewards not consistently awarding the correct schematics?
Some update!
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Shan, any comment on the inbox rewards not consistently awarding the correct schematics?
I will bring it up but as far as I can tell it is likely due to the maintenance not being fully done when rewards were collected.
This is going to come off as facetious--- I know it is, but I gotta say, with things like Events you've already as an organization stated that y'all are too busy trying to get things right to give advanced notice for things.
How is this different type of situation going to be dealt with differently than the weekly event notifications to truly give further advanced notice when this option will be exercised?
I apologize if I gave the impression we're going to do regular game downtime/outages going forward.
What I meant was going forward, if we believe downtime/outage is in the best interest of the players, we'll do better than a 17-hour heads up.
So, if you DON'T do better than a 17 hour heads up, like when it's late and not announced its going to be late, that means it's not in the best interest of the players?
Some update!
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Shan, any comment on the inbox rewards not consistently awarding the correct schematics?
I will bring it up but as far as I can tell it is likely due to the maintenance not being fully done when rewards were collected.
Y'know, when maintenance down time is ANNOUNCED and SCHEDULED, problems like claiming schematics before maintenance is complete could be AVOIDED simply by STICKING TO the ANNOUNCED SCHEDULE.
Today's latest foul up certainly does NOT fall into the category of better communication! Instead, it just emphasizes, once again, that DB has absolutely NO IDEA what the concept of "clear communication" means!
Honestly, I'm for one ready to let this piece slide this specific time with one true and honest suggestion/direction.
And I'm going to go all Trekkie on this one:
Step 1) All DB Developers and communications personnel should be required to watch the TNG Episode "Relics"
Step 2) Discuss the difference between Geordi and Scottys approach on outage communications.
Step 3) Embrace the Scotty approach. Give yourself larger bubbles of time than you think you need as either a) Murphy will help use up the time or b) You'll come off as the hero getting things done earlier than advertised.
As a former TS and CS rep and manager, and former network engineer now project manager, I've learned to embrace this concept.
Now admittedly I have LeVar Burtons autographic pic in my office (and when he heard it was going to my work place, signed it "(my name) Get back to work!") So I embrace LaForge's work ethic in other aspects.
Some update!
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Shan - Please be aware that the manner in which this maintenance was conducted has impacted individual players DIFFERENTLY! For some, their voyage was auto-recalled and immediately available for a new voyage as was communicated by DB yesterday.
However, for others (myself included), my voyage was NOT recalled at all. Instead, my voyage was initially stalled (an hour+ passed with NO time elapsed on my voyage) and then the timer on my voyage continued to run again. Furthermore, my voyage is not collecting any rewards nor is triggering any dilemmas (I just passed the 6hr mark with no dilemma or anything).
However, the BIGGEST issue is that I'm now UNABLE to recall the voyage! All attempts to click the [Recall] button have no effect.
So, while some players benefited from an instantly returned voyage and already started collecting rewards from a new voyage, I have neither...I was denied the benefit of an instantly recalled voyage, and now I am unable to recall the voyage myself! So, in essence, I have been banned from participating in voyages altogether, and unfairly being punished while other players fully benefited.
While this notification is needed and appreciated, it points out that there is still no response to the current Picard fire raging through the community.
That said, some heads up is better than none. Also, maybe CS can be on the look out for the rare extreme cases like Dr Rgne's and be told to compensate him accordingly.
The sense I get from DB's current communication is that they know they've screwed up with MirrorPicardGate, but they haven't figured out what "not screwing up" looks like yet, so they're on lockdown until they're all on the same page on how they're going to screw up next fix it.
Honestly, I'm for one ready to let this piece slide this specific time with one true and honest suggestion/direction.
And I'm going to go all Trekkie on this one:
Step 1) All DB Developers and communications personnel should be required to watch the TNG Episode "Relics"
Step 2) Discuss the difference between Geordi and Scottys approach on outage communications.
Step 3) Embrace the Scotty approach. Give yourself larger bubbles of time than you think you need as either a) Murphy will help use up the time or b) You'll come off as the hero getting things done earlier than advertised.
As a former TS and CS rep and manager, and former network engineer now project manager, I've learned to embrace this concept.
Now admittedly I have LeVar Burtons autographic pic in my office (and when he heard it was going to my work place, signed it "(my name) Get back to work!") So I embrace LaForge's work ethic in other aspects.
Yes, stick to the original plan with wide margins or error to give the appearance of a miracle worker... mind you, Scotty charged up phaser banks just for fun when he was supposed to be fixing impulse engines...
Stick to the original plan.... no bloody Plan A... B... C... or D... and don’t even think about F 😂
The game is up and running on our end, with no issues.
If you are unable to login and or have a different issue please submit a ticket and do not hesitate to create a post in Engineering Room.
I got my three lots of NX-01 fine. An error message did come up on the first claim click, but the schematics were credited anyway. This was just after 4pm GMT.
Level 99. Latest Immortal (957): Chancellor Gowron - October 2023.
The new ships were displayed when I went to claim in the arena rewards mails when re-entering the game today. But when I claimed one, like Eris it gave the old schematics instead of the new. Verified this in the ship menu. Then the rest of the mails displayed the old ships instead again. Waited another hour or to to claim the others once they were again displaying the new ships, and they were the new schematics.
Comments
*shrug*
No - not 'shrug'. How many ways can DB **tsk tsk** things up? When was the last time they got something right? I am right on the very edge of getting rid of the game; I am SICK of the incompetence.
"Some time tomorrow morning we think.."
And 10:30am et means "most likely early afternoon"
That's how I'm gonna try to read all posted times and timers from now on..
"Event start time Thursday Noon
Event End time Monday Noon"
Will translate in my brain to
"Event starts Thursday early afternoon
Event ends Monday...ish, we think !" Lol
Just gotta read the notices like a 90 year old is telling you about them.
"It'll end when it'll end and you'll know it's over when it's over now stop asking me so many questions I have to ignore and get me some *** ***** Jell-O you smarmy *** whipper snappers"
Llap
"Llap ? What's wrong with you ? You can't expect me to give you a lap dance no matter how much Jell-O you bring me ya little freak"
I used to think them signing off tickets LLAP was cute.
Now I think it's their code way of saying "**tsk tsk** you"
The maintenance is done, and as it turns out it didn't result in a downtime as we expected. It also lasted longer than we anticipated, and we will take that into account should we need to go through a similar process again.
I can confirm the following:
- the new Battle Arena Rewards are live
- crew slot sale has ended
- Dabo Wheel sale has ended
Shan, any comment on the inbox rewards not consistently awarding the correct schematics?
I will bring it up but as far as I can tell it is likely due to the maintenance not being fully done when rewards were collected.
So, if you DON'T do better than a 17 hour heads up, like when it's late and not announced its going to be late, that means it's not in the best interest of the players?
Yeah, I can see that.
Y'know, when maintenance down time is ANNOUNCED and SCHEDULED, problems like claiming schematics before maintenance is complete could be AVOIDED simply by STICKING TO the ANNOUNCED SCHEDULE.
Today's latest foul up certainly does NOT fall into the category of better communication! Instead, it just emphasizes, once again, that DB has absolutely NO IDEA what the concept of "clear communication" means!
Ok, let Black Pebble's spin commence.
And I'm going to go all Trekkie on this one:
Step 1) All DB Developers and communications personnel should be required to watch the TNG Episode "Relics"
Step 2) Discuss the difference between Geordi and Scottys approach on outage communications.
Step 3) Embrace the Scotty approach. Give yourself larger bubbles of time than you think you need as either a) Murphy will help use up the time or b) You'll come off as the hero getting things done earlier than advertised.
As a former TS and CS rep and manager, and former network engineer now project manager, I've learned to embrace this concept.
Now admittedly I have LeVar Burtons autographic pic in my office (and when he heard it was going to my work place, signed it "(my name) Get back to work!") So I embrace LaForge's work ethic in other aspects.
Shan - Please be aware that the manner in which this maintenance was conducted has impacted individual players DIFFERENTLY! For some, their voyage was auto-recalled and immediately available for a new voyage as was communicated by DB yesterday.
However, for others (myself included), my voyage was NOT recalled at all. Instead, my voyage was initially stalled (an hour+ passed with NO time elapsed on my voyage) and then the timer on my voyage continued to run again. Furthermore, my voyage is not collecting any rewards nor is triggering any dilemmas (I just passed the 6hr mark with no dilemma or anything).
However, the BIGGEST issue is that I'm now UNABLE to recall the voyage! All attempts to click the [Recall] button have no effect.
So, while some players benefited from an instantly returned voyage and already started collecting rewards from a new voyage, I have neither...I was denied the benefit of an instantly recalled voyage, and now I am unable to recall the voyage myself! So, in essence, I have been banned from participating in voyages altogether, and unfairly being punished while other players fully benefited.
@Shan Can we write a ticket if we collected the rewards after the icons and descriptions clearly changed and we assumed the new rewards were in place?
Had 3 batches of NX-class inbound, none of them turned out to be NX-class, but ISS Enterprise instead. Totally it was 320 schematics (1x120, 2x100).
The sense I get from DB's current communication is that they know they've screwed up with MirrorPicardGate, but they haven't figured out what "not screwing up" looks like yet, so they're on lockdown until they're all on the same page on how they're going to screw up next fix it.
Yes, stick to the original plan with wide margins or error to give the appearance of a miracle worker... mind you, Scotty charged up phaser banks just for fun when he was supposed to be fixing impulse engines...
Stick to the original plan.... no bloody Plan A... B... C... or D... and don’t even think about F 😂
It is telling me to try again later.
This is what I get after reinstalling on all my devices...
If you are unable to login and or have a different issue please submit a ticket and do not hesitate to create a post in Engineering Room.
~· Fly with the Subspace Eddies! ·~
Sorry for the delay, yes you can submit a ticket for this.
Thank you Shan! It is much appreciated!