Zoning bug
Posted on: Sat, 09/20/2008 - 8:55am
Looks like there is a new bug that Tuesday's patch introduced. Some missions will freeze everyone that tries to enter them. This happened last Wednesday, during the coalition event.
The workaround is to reset the mission. But if there is someone locked inside the mission (game isn't up on the client side but the game server thinks you are there), the mission won't reset. That's what happened to us last Wednesday, when we tried to reset the mission but did that while some were veryfying the image.
Best way to solve it is to wait 3-5 minutes and try again (if possible making sure everyone isn't logged on the server). Again, it's possible to be logged on the server even though your game instance doesn't exist anymore. If you already saw the message "This account is already logged in", that's because your account was logged, even though your client crashed (and that's also when that account session is killed).
So, rule of thumb, ask everyone to restart the game, login, wait 3-5 minutes and try again...
PS: This can also happen to SG bases, not sure how to fix it, probably just enter a mission or wait some minutes.
The workaround is to reset the mission. But if there is someone locked inside the mission (game isn't up on the client side but the game server thinks you are there), the mission won't reset. That's what happened to us last Wednesday, when we tried to reset the mission but did that while some were veryfying the image.
Best way to solve it is to wait 3-5 minutes and try again (if possible making sure everyone isn't logged on the server). Again, it's possible to be logged on the server even though your game instance doesn't exist anymore. If you already saw the message "This account is already logged in", that's because your account was logged, even though your client crashed (and that's also when that account session is killed).
So, rule of thumb, ask everyone to restart the game, login, wait 3-5 minutes and try again...
PS: This can also happen to SG bases, not sure how to fix it, probably just enter a mission or wait some minutes.
__________________@Lord Hexen
__________________