5 Minute Patch Warning
There’s been tons of threads on this. Anet promised a one hour warning a while back and last patch they did that … But it’s since gone back to the surprise patch again it seems.
Here’s another thread on the subject, but there are easily a dozen more
https://forum-en.gw2archive.eu/forum/pvp/wuvwuv/Unexpected-patching-loss-of-golems
(edited by Jayne.9251)
Obviously anet don’t actually have a process n place on this its just at the whim of the devs.
Miranda Zero – Ele / Twitch Zero – Mes / Chargrin Soulboom – Engi
Aliera Zero – Guardian / Reaver Zero – Necro
Ah, the good old late 90’s, pre-ITIL work practices of IT.
“Is the boss or anyone else remotely important in the office?”
“Nope”
“Just reboot that kitten then!”
KnT Blackgate
Obviously anet don’t actually have a process n place on this its just at the whim of the devs.
ANet does not have a centralized process in place for dropping patches. If you listen to the 45 minute video they did back before launch where they describe various aspects of their coding schemes, one of the things they mention is that any group of devs can drop a live patch at their whim without involving anyone else. It’s been pretty obvious since then that they think it’s pretty cool to do so.
Stormbluff Isle [AoD]
Obviously anet don’t actually have a process n place on this its just at the whim of the devs.
ANet does not have a centralized process in place for dropping patches. If you listen to the 45 minute video they did back before launch where they describe various aspects of their coding schemes, one of the things they mention is that any group of devs can drop a live patch at their whim without involving anyone else. It’s been pretty obvious since then that they think it’s pretty cool to do so.
Yea probably when enemy server is about to enter inner Garrison for server Anet dev plays on :-)
Community Coordinator
Hello everyone.
Thanks for your input and feedback up to this point. As there are effectively other threads about this issue, we will proceed to close this one in order to avoid duplicates. We will also forward this to the team today as we understand this is a very frustrating issue.
Thanks!