Apt as it may be in preparation for an event called 'Radio Silence ' some response regarding the lack of today's expected mini-event start (& an indication of what new timline we can expect to be following instead) would be nice...
Apt as it may be in preparation for an event called 'Radio Silence ' some response regarding the lack of today's expected mini-event start (& an indication of what new timline we can expect to be following instead) would be nice...
It's 745am EST and WRG is based in the Eastern US. Since we know they don't have staff working overnight, it's not exactly shocking that there's been no response as I guarantee no one has logged in yet.
Apt as it may be in preparation for an event called 'Radio Silence ' some response regarding the lack of today's expected mini-event start (& an indication of what new timline we can expect to be following instead) would be nice...
It's 745am EST and WRG is based in the Eastern US. Since we know they don't have staff working overnight, it's not exactly shocking that there's been no response as I guarantee no one has logged in yet.
This is the whole problem in a nutshell. When you have something going live outside of office hours, you need to have someone on call to make sure it goes smoothly. At the very least, they need to be able to communicate with your customers and let them know what's going on and when they can expect a fix. That's just basic good business practice for any IT company, and the fact that WRG have let this happen again shows that either they don't care about their business or they just have no idea what they're doing.
Letting this happen once was incompetent but letting it happen twice is inexcusable.
I find repeat mistakes like this especially annoying. The last time this happened should’ve been the last time it happened ever. Don’t promise things that you can’t ensure delivery of.
If it were for a feature that everyone is anxiously looking forward to, but having bugs involved in a teadious "event" that is nothing more than hoarding upfront (fusable crew etc) and delaying daily activities until some block is removed is just annoying. Please reconsider those "events" alltogether!
Maybe WRG should issue laptops to employees to take home in case something arises that needs immediate attention. Maybe offer email for mobile devices as well.
There’s no reason to go there, it will get fixed and move on. There’s far more important things to worry about.
This is the second time since we have been their unpaid interns beta testing for them that this has happened. Maybe at some point ongoing problems really are an issue?
"The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
Maybe WRG should issue laptops to employees to take home in case something arises that needs immediate attention. Maybe offer email for mobile devices as well.
I would assume, given the ongoing state the world is in right now, that they all have the ability to work from home already.
And the whole purpose of a beta test is to find, identify and fix (attempt to fix) any issues.
We all have a choice about participating in any beta testing: if you don’t mind the bugs, take part. Otherwise, don’t take part until [insert feature] is more reliable.
To the point that the developers, engineers or whoever have the ability to work from home. You’re likely correct however, despite and - perhaps - increasingly importantly - because of that, it’s also important for everyone to have a ‘work life’ balance. Surely none of us would expect the engineers to be on standby 24 hours a day?
Let’s be honest, this is a game for relaxation and, if it winds people up this much, perhaps they need to find a way to relax, play another bane for a short while, sit back and wait for WRG to let us know what’s going on, what they’ve done about it and leave it to them, the project managers and the engineers to put things right.
There’s no reason to go there, it will get fixed and move on. There’s far more important things to worry about.
This is the second time since we have been their unpaid interns beta testing for them that this has happened. Maybe at some point ongoing problems really are an issue?
And they have never said it wasn't an issue. This is even acknowledged as a beta test where you should assume bugs will happen.
But there was only one time where they blamed players. And it was a year ago. Maybe it's time to stop beating a dead horse.
And the whole purpose of a beta test is to find, identify and fix (attempt to fix) any issues.
We all have a choice about participating in any beta testing: if you don’t mind the bugs, take part. Otherwise, don’t take part until [insert feature] is more reliable.
To the point that the developers, engineers or whoever have the ability to work from home. You’re likely correct however, despite and - perhaps - increasingly importantly - because of that, it’s also important for everyone to have a ‘work life’ balance. Surely none of us would expect the engineers to be on standby 24 hours a day?
Let’s be honest, this is a game for relaxation and, if it winds people up this much, perhaps they need to find a way to relax, play another bane for a short while, sit back and wait for WRG to let us know what’s going on, what they’ve done about it and leave it to them, the project managers and the engineers to put things right.
Nobody's asking for the whole team to be available 24/7. But somebody should at least check that the new feature that's meant to have gone live has in fact gone live, especially when past performance has shown that these things haven't always gone as planned.
Taking responsibility for the work that you're meant to have done is important. And I'm saying this as someone who's been in the office for software rollouts at 4AM in the past. It's not pleasant, and I wouldn't do it on a regular basis, but occasionally it is required. But that wouldn't have been required here. It obviously wasn't a serious issue, since it only took about half an hour to fix, just like last time.
No professionalism. No pride in their work. No respect for the customers. That's the message that this puts across. Again.
There’s no reason to go there, it will get fixed and move on. There’s far more important things to worry about.
This is the second time since we have been their unpaid interns beta testing for them that this has happened. Maybe at some point ongoing problems really are an issue?
It basically shows that TP has been unable to fix its problems. They systems they have in place are not effective outside of things they originally considered (if at all).
No professionalism. No pride in their work. No respect for the customers. That's the message that this puts across. Again.
This sums up the whole thing from my perspective. And its not an isolated incident. This has been ongoing since Disruptor Beam sold the game to WRG/TP.
I can understand the people who say there are bigger things to worry about, but in all honesty that type of rhetoric is like putting a frog in a pot and slowly bringing the water to a boil. I try to keep an objective perspective and I can tell you that looking at the fact that TP/WRG has still not addressed the privacy concerns brought up by @NoNameNamer , had a poor execution, or heck, even acknowledgement of the 6th year anniversary, followed by a failure of an objective event start, is serious cause for concern.
for those who say that objective events are still beta, yes, thats true. But this is like the third or fourth week of them. I would imagine that something as critical as having the darn things start on time would have been ironed out at this point.
Comments
It's 745am EST and WRG is based in the Eastern US. Since we know they don't have staff working overnight, it's not exactly shocking that there's been no response as I guarantee no one has logged in yet.
If it happens 1 time…okay….but how often did this happen already?
More and more ppl of my fleet are taking a break or are done for good.
Such constant mess ups don t help.
This is the whole problem in a nutshell. When you have something going live outside of office hours, you need to have someone on call to make sure it goes smoothly. At the very least, they need to be able to communicate with your customers and let them know what's going on and when they can expect a fix. That's just basic good business practice for any IT company, and the fact that WRG have let this happen again shows that either they don't care about their business or they just have no idea what they're doing.
Letting this happen once was incompetent but letting it happen twice is inexcusable.
Whoa, please don't lump the Big Book's quality assurance and customer support in with WRG's. We take pride in our work.
Considering it's "Convergence Day", a nice reward would be canceling the OE and just giving everyone the rewards as if they had participated fully.
I totally agree with Automaton. For me, there are worlds between them.
The Big Book folks do what they do because they love doing it. Not seeing much evidence that’s true of WRG.
Speak for yourself, I half **tsk tsk** everything I do.
Edit: gonna leave that there for intepretation.
Probably it is the players' fault. That seems to be a new go-to......
This is the second time since we have been their unpaid interns beta testing for them that this has happened. Maybe at some point ongoing problems really are an issue?
I would assume, given the ongoing state the world is in right now, that they all have the ability to work from home already.
We all have a choice about participating in any beta testing: if you don’t mind the bugs, take part. Otherwise, don’t take part until [insert feature] is more reliable.
To the point that the developers, engineers or whoever have the ability to work from home. You’re likely correct however, despite and - perhaps - increasingly importantly - because of that, it’s also important for everyone to have a ‘work life’ balance. Surely none of us would expect the engineers to be on standby 24 hours a day?
Let’s be honest, this is a game for relaxation and, if it winds people up this much, perhaps they need to find a way to relax, play another bane for a short while, sit back and wait for WRG to let us know what’s going on, what they’ve done about it and leave it to them, the project managers and the engineers to put things right.
New Error?
Probably rescheduled to end right before the Event so people will have plenty of time. Like, a compensation thing.
And they have never said it wasn't an issue. This is even acknowledged as a beta test where you should assume bugs will happen.
But there was only one time where they blamed players. And it was a year ago. Maybe it's time to stop beating a dead horse.
As with most things in this game, if something looks or acts strange, rebooting the app usually fixes the problem
Nobody's asking for the whole team to be available 24/7. But somebody should at least check that the new feature that's meant to have gone live has in fact gone live, especially when past performance has shown that these things haven't always gone as planned.
Taking responsibility for the work that you're meant to have done is important. And I'm saying this as someone who's been in the office for software rollouts at 4AM in the past. It's not pleasant, and I wouldn't do it on a regular basis, but occasionally it is required. But that wouldn't have been required here. It obviously wasn't a serious issue, since it only took about half an hour to fix, just like last time.
No professionalism. No pride in their work. No respect for the customers. That's the message that this puts across. Again.
It basically shows that TP has been unable to fix its problems. They systems they have in place are not effective outside of things they originally considered (if at all).
This also works with 80% of Microsoft’s bugs.
This sums up the whole thing from my perspective. And its not an isolated incident. This has been ongoing since Disruptor Beam sold the game to WRG/TP.
I can understand the people who say there are bigger things to worry about, but in all honesty that type of rhetoric is like putting a frog in a pot and slowly bringing the water to a boil. I try to keep an objective perspective and I can tell you that looking at the fact that TP/WRG has still not addressed the privacy concerns brought up by @NoNameNamer , had a poor execution, or heck, even acknowledgement of the 6th year anniversary, followed by a failure of an objective event start, is serious cause for concern.
for those who say that objective events are still beta, yes, thats true. But this is like the third or fourth week of them. I would imagine that something as critical as having the darn things start on time would have been ironed out at this point.