Hotfix - Request for Advanced Notification

Kindly,

A Hotfix is a planned maintenance activity. It isn't a unplanned outage. The two are very different. Multiple employees in the BP/DSO IT staff were certainly aware far in advance that a patch was planned. I highly doubt that a single individul drove to work and said "I think I'll reboot all of our server assets". It was most certainly a coordinated activity under rigid change management.

In the future,
1) please consider notifying the community at least 24 hours in advance
2) please consider indicating the estimated time of availability (ETA)
3) please consider applying patches on a specific time and day of the week
4) please consider leaving the forum up and available during all outages.

I do realize and appreciate that the forum moderators may not have this information any sooner than is posted. I understand and respect that. What I ask is that you kindly reach out to the Developers and let them know the primary mission of the forum is to inform the users. I certainly hope the primary mission is not to vote on Halloween Costumes.

Thank you for your consideration.

 

could the team please "Decide" to fix the position bug.
thanks

 

I have to wonder how much anything related to the game is actually "planned" by the developers or anyone else. Just look at the recent history -- Release 132 introduced bugs so severe they were crashing the game engine (Nebula errors), so there was a perceived need to rush out a couple of Hotfixes. Perhaps a better plan would have been to roll back to Release 130?

And now Release 133 has introduced bugs that make it difficult or impossible for some people to log into the game. I wonder what Release 134 (or 135 if they have to skip another release) will bring? Maybe a bug that will randomly wipe out user data? Or maybe a bug that makes a complete hash out of the networking code?

I can offer some advice (not that anyone at BigPoint will take any), and that would be: Whatever code development methodology you're using right now is NOT WORKING WELL, so it's time to re-group. Cancel the next event, put the Halloween plans on hold, and figure out how you hope to stop introducing deadly bugs in your releases

 

Instead of constantly asking us to delete the DSO temp file, why doesn't BP just correct it with an update or reload?
Or maybe players are just a game for the developers and managers?

 

Guys, you've veered off topic. The purpose of this thread was to respectfully ask our CM to reach out to DEV and request planned maintenance outage notifications. Your points are interesting but probably belong in a different thread.

 

Oh DeserKoala, in an ideal world this would be sooooooooo helpful.
Believe me, we would LOVE that.

However, the reality is that - when it comes to hotfixes this is not always applicable (unfortunately). (lets take the example from monday 1st of September) the previous patch was applied Thursday 29th of August, the problem was detected over the weekend and the only chance to fix it ASAP was on monday.
And believe me - we had our fair share of "look how the fans responded".

I am on the same page as you though - usually we are aiming for a 24h 'heads up' in advance. that is true for patch notes publications and for some changes we even talk to you before that.

Btw, the costume contest is something totally not relatable - we the CMs came up with it and are accompanying it - and see, the communication of it goes well and relaxed

 

Thank you for the candid reply. It is very appreciated.

 

If a planned event isn't posted, how is it different than an emergency or an accident to the surprised?

It does seem that every scheduled maintenance requires a new upload for the thin client. Or is it just coincidence?