This is my first BGA development, and my first game has entered Alpha. I have an etiquette question about deploying "game breaking" fixes during Alpha.
I had a bug that invalidated any games already running, as the old game logic was wrong versus the game's rules. Unfortunately, I couldn't figure out how to do the fix without also breaking games in progress.
Beyond trying to minimize these game breaking updates, and announcing to the game group when I do have to do so, is there anything else I should be doing during Alpha phase when that situation occurs? For example, during Alpha, am I supposed to lock out table creation for a day or two before deploying a major fix that might cause games in progress issues?
Note: I have the logic implemented to inform the players to do a F5 refresh when client / server software versions don't match. Unfortunately, that wasn't able to prevent this last update from breaking games in progress.
I had a bug that invalidated any games already running, as the old game logic was wrong versus the game's rules. Unfortunately, I couldn't figure out how to do the fix without also breaking games in progress.
Beyond trying to minimize these game breaking updates, and announcing to the game group when I do have to do so, is there anything else I should be doing during Alpha phase when that situation occurs? For example, during Alpha, am I supposed to lock out table creation for a day or two before deploying a major fix that might cause games in progress issues?
Note: I have the logic implemented to inform the players to do a F5 refresh when client / server software versions don't match. Unfortunately, that wasn't able to prevent this last update from breaking games in progress.
