(edited by BillFreist.1527)
Nothing is trivial when it comes to spawn code.
I nailed down what was causing this, it wasn’t just something with this specific spawn. The problem was related to the cage that the spawn goes in. There was a problem with the way we enable/disable the collision for the cage when the dude would get released at the end of the event. Ultimately this was preventing the area inside the cage from being ‘spawn-able’.
I’m sure this same bug was causing all sorts of other random failures across the game.
Anyways, the fix is slated for our next build unless we identify any issues with the fix between now and then and have to yank it out. I’m making zero promises here.
-Bill
Restoring access, please check to see if you are now fixed
Alright its finally that time. I’m doing a preliminary test on my own account before firing away on your accounts. Europe will be the first to get the fix because there’s only a few people affected. Once I evaluate that all went well, I’ll do accounts in America and it should be a really short downtime for those people.
Sorry for the delays. Its almost like I’m be cautious or something 
I just finished doing a trial run and verifying that we can now move forward. As of right now, I plan on briefly blocking access to affected accounts tomorrow morning between 8am and 12pm PST. If all goes well, the block to the affected accounts will only last around 15 minutes – if not, it could be up to an hour or so.
I tried to get this done within work hours to ensure we have everyone available if something goes wrong, but because I’m such a paranoid person my testing took much longer because of how thorough it was 
We’ll send a warning to those affect in advance of disabling the account.
-Bill
Ok Ok… I have heard enough… Its time Anet replaces Bill with a Bristleback…
I’ll just leave this here
Attachments:
Sure, but that’d mean a feature from HoT would have to be cut in order to make up the lost development time. Is that something you could live with?
Yes. ._.
Well then, so much for this awesome feature: Bill The Troll Minipet. Such a shame
Sure, but that’d mean a feature from HoT would have to be cut in order to make up the lost development time. Is that something you could live with?
Attachments:
(edited by BillFreist.1527)
More improvements coming with our next release. As always, I’d love to hear if anyone notices an improvement. This one should be much more significant. A lot of the improvements so far haven’t been very visible to players, but behind the scenes have really made an impact.
I’ll be shifting my focus back to this in the next couple weeks so I can hopefully get more improvements into the release after next. I’ve been trying to tackle other issues plaguing the client like out of memory crashes and frame-rate hitching in the past week.
As much as I might like to dress up in full costume in my spare time, I’m not superman. One thing at a time
-Bill
I put together a fix for a pretty nasty performance issue on our game servers. This should make it into our next release so I’d be curious to see if it makes a noticeable improvement. The bug looks like it was introduced around when this thread popped up.
I also got a couple client improvements that should help reduce framerate hitching with lower-mid range video cards and/or higher shader settings. Coming next release, too.
-Bill
Wvw improved for me after you did maintenance some days ago, PvE got worse, the mobs ported all over the place. That’s gone, I think since wvw reset last night but the wvw “lags” (it’s not really lags, I just can’t properly hit and my opponents seem to port from time to time) are back.
I hope that weren’t the changes you meant but the real ones are still to come
Nope. Changes to the game server almost always (aside from when we do things like disable content, etc) come from a new game build. The server maintenance the other day wasn’t part of the game server whatsoever.
-Bill
(edited by BillFreist.1527)