
It's a good thing that this was caught during OB and NOT during early access or even the launch proper, but that's not really saying much.
This is a gamebreaking bug. You have thousands of players who are literally completely unable to test anything else because, y'know, they're locked out. Yeah, this is absolutely the highest priority to fix, but what's most disconcerting about it is that it's an issue at the very core of their system. I've never experienced this issue with an MMORPG before - at most I've seen plenty of issues with servers being overloaded, disconnecting, excessive lag, etc., but I've never seen an issue where you are literally locked out of the game by a single bug.
This tells me that there is something very, very wrong with how they're checking for whether or not a player is "logged in". As I read elsewhere, it is likely that the game crashed somewhere and the server has created some kind of paradox where it continually checks for whether or not the player is logged in but completely fails to actually make that check, and thus gets locked in a ridiculous loop where the player is assumed to be online even though there is no connection. The game should be checking for an actual connection, but for whatever reason the code does things differently.
At any rate, as irritated as I am over this, I... Sorry, no, I'm extremely angry at this point. A full day of zero playtime because of a bug this... this ridiculous? Man, I don't even know what to say to that.
This is a gamebreaking bug. You have thousands of players who are literally completely unable to test anything else because, y'know, they're locked out. Yeah, this is absolutely the highest priority to fix, but what's most disconcerting about it is that it's an issue at the very core of their system. I've never experienced this issue with an MMORPG before - at most I've seen plenty of issues with servers being overloaded, disconnecting, excessive lag, etc., but I've never seen an issue where you are literally locked out of the game by a single bug.
This tells me that there is something very, very wrong with how they're checking for whether or not a player is "logged in". As I read elsewhere, it is likely that the game crashed somewhere and the server has created some kind of paradox where it continually checks for whether or not the player is logged in but completely fails to actually make that check, and thus gets locked in a ridiculous loop where the player is assumed to be online even though there is no connection. The game should be checking for an actual connection, but for whatever reason the code does things differently.
At any rate, as irritated as I am over this, I... Sorry, no, I'm extremely angry at this point. A full day of zero playtime because of a bug this... this ridiculous? Man, I don't even know what to say to that.