Turnaround time needs to be improved

Previous topic - Next topic

dominion

I think the turnaround time for this kind of system outage needs to be improved. Seems like there is nobody actively monitoring the system. I assume the admin is sleeping since he hasn't been online for over 10 hours. There should probably be someone to act as a backup or communicate with players in a different timezone.

Ingix

Unfortunately, it's a formally 1-person operation with volunteers to help out.

What happened, was the system down over the European night?

AdamH

Quote from: Ingix on 23 February 2022, 08:53:41 AM
Unfortunately, it's a formally 1-person operation with volunteers to help out.

If it's a one-person operation with software that has been plagued with bugs ever since the newest version was released, then the best thing to do would be to REVERT TO THE MOST RECENT WORKING VERSION OF THE SOFTWARE until the newest version has been properly tested.

This release has been an absolute dumpster fire, worse than FunSockets back in the day, but at least they had someone competent at the wheel who realized that you shouldn't have software available to the public that doesn't work. You need to REVERT TO TO THE OLD VERSION until all of this stuff is worked out.

How long is it going to take until we get working Dominion again? It can be done in seconds while all of this work continues.

Ingix

I do hope that the neausating problems can be gotten under control, but I'm not sure how that can be best achived, as the reasons seem not to be clear cut.

AdamH

Quote from: Ingix on 23 February 2022, 10:10:00 PM
I'm not sure how that can be best achived.

Well I have an idea. Why don't you revert the software to a working version so you don't put your paying customers through this, then you'll have a lot more time.

alibby1152

Quote
Why don't you revert the software to a working version

Were the 10 or so rated games I played today just a figment of my imagination? Worked just fine for me, and outside of the outage last night, I've been playing a working version of Dominion since release

AdamH

You're one of the lucky ones who is playing on a device it works on. Probably similar to the single device this software was tested on. For the rest of us, it's a raging dumpster fire.

artsfols

Quote from: alibby1152 on 24 February 2022, 05:01:28 AM
Quote
Why don't you revert the software to a working version

Were the 10 or so rated games I played today just a figment of my imagination? Worked just fine for me, and outside of the outage last night, I've been playing a working version of Dominion since release

This is now my experience.  Admittedly I play only on PCs in a browser.  But if it works well for us, then that means the problems are machine, not design dependent.  And that means it just requires fixin' and everyone should be back to normal - i.e no UI or game logic changes required.
Note I said 'if'. 
Today I upgraded to 'gold' and started working through a few levels playing bots.  A much more enjoyable way to learn new cards and how to use them.

I'm not sure if some optimization of the code occurred or as a result of re-setting the animation slider, but the game play is exceedingly fast.  The other thing that used to bug me quite a bit was the way the black bar covered up the lower 5 cards in supply.  It seems to be less aggravating.
In general, well done.

AdamH

Quote from: artsfols on 25 February 2022, 11:35:04 PM
But if it works well for us, then that means the problems are machine, not design dependent.  And that means it just requires fixin' and everyone should be back to normal - i.e no UI or game logic changes required.

This is simply not true.

but even if it was, there needs to be a list of supported devices and the software needs to be tested on all of those devices before it's released. People have paid money for something that works for them and when that is taken away, there is a problem.

artsfols

Quote from: AdamH on 26 February 2022, 03:56:43 AM
Quote from: artsfols on 25 February 2022, 11:35:04 PM
But if it works well for us, then that means the problems are machine, not design dependent.  And that means it just requires fixin' and everyone should be back to normal - i.e no UI or game logic changes required.

This is simply not true.

but even if it was, there needs to be a list of supported devices and the software needs to be tested on all of those devices before it's released. People have paid money for something that works for them and when that is taken away, there is a problem.

Of course, you are right.  Even for the smallest change there should be a full regression test against a complete device list.  That's standard procedure for anything with thousands or millions of subscribers.
And my argument is preceded with an 'if'.  I really am speaking only from my own anecdotal experience and don't mean to undermine your or anyone else's experience.

But I would urge you to stick with it for a while, or time out and come back after a grace period.  Because if you enjoy the game, and have to stop playing, then the biggest loser is you, not the game publisher.  I still think that what we are seeing is glitches, not a catastrophic failure, but in any case, time will tell which it is, so isn't it worth just waiting out and seeing?

AdamH

I desperately want to be able to play for Allies preview week in two days, which is why I've been taking the only free time I have and playing Dominion on the only device in my house that supports Shuffleit right now, and trying to decrease the nausea I feel when I try to play by just doing it more with a vomit bag at my desk.

Wouldn't it be nice if Shuffleit's incompetence wasn't doing this to me and I could just play the game? And what about all of the people who aren't as obsessed with the game as I am and will just quit or ask for their money back?

The next time Shuffleit's contract expires there will be a competitor made by people who know how to write software. I hope the competitor gets the whole contract.

Ingix

I'm sorry that you are so heavily inflicted with nausea when playing the 1.6 version.

I've been bumping the touchscreen --> fullscreen bug report, but it seems it isn't worked on yet  :(