I would like to update you on the current issue with WvW.
We have identified what is causing the problem and are currently working to resolve it.
Once we will reactivate WvW, the matchups that started last Friday will continue with the correct score.
Please note that all objectives will be reset to their starting state, and all siege weapons that were deployed will be gone.
I currently do not have an ETA for when WvW will be reactivated, but we will let you know immediately once it is up and running again.
Once again – apologies for any inconvenience caused.
I dont understand how this can happen. Why the hell is there no backup of the state wvw was in before the patch!?
The fact that it all resets will probably make the difference in us loosing the matchup this week… great……wait…seriously? You don’t get why they don’t roll back all their servers on a whim? Roll backs are only ever the last resort bro. First step is find the problem, if that problem is integral to the patch, I.e. cannot be removed without destabilizing the program, then you roll back. Otherwise ya find the break in code and patch it closed…it’s why we call them “patches”.
Second of all, if a few hours of a Tuesday morning is going to make your server lose, you probably weren’t going to win anyhow.
Before calling ppl idiots you should try not being an idiot.
-snip-I never called anyone an idiot. Perhaps you have a guilty conscious? If so by all means continue with the QQ.
Just get it all out buddy. It’s all going to be OK.
AND to the kittenin idiot, there is a HUGE difference between rolling back DATA vs rolling back the actual PROGRAM. Specially since in this case no changes have been apparently been made to the data structure of the objects i expect to be restored to their initial state.
Please enlighten us all on the difference between data and a program. I’m dying to know.
I am not the OP, but… rolling back a program requires a new build. So maybe they have a git repository with all of their code and they have patched and then built a new .exe from that source to get where they are now. Then they find the WvW bug, and they have to patch the source and create a new .exe (program). That program will contain all of the last patches changes, and the most recent fix.
Separate from that, they have data stored on their servers that the program accesses to fill in all of the information the GUI displays. Rolling this data back does not require the build to change.
These are separate entities, and changing the program does not HAVE to touch the data, hence why the siege and keeps/towers, etc., for each color didn’t change, but something the program did caused the realm associated with that color/matchup to change. That said, the way the program interacted with the data may require a manual rewrite, making it relatively easy to keep the points where they are while fixing the matchups, but at the expense of individual data for each keep/tower/siege.
I am clearly speculating about why, but what it does mean is that all of the T3 upgrades and defense a server has put into the matchup will be wiped and that gives every server that was unable to keep their towers/keeps new life to get back into it.
Presuming data is archived in real time by the program, modifications to this data, after the point of patching the program, are likely to become dependant to that build if this data set is dependent on any portion of the patch. If data is not archived in real time (likely case) there’s nothing to revert back to other than a default state set by the programming.
Though what I was getting at with my initial statement is that though all data isn’t a program, all programs are in fact data =P
Yup, I definitely didn’t take your initial statement in your intended direction. As far as the data being build-dependent, that is quite possible, but I don’t expect them to explain and I should probably work rather than speculate…