#104761: "Undo function generates Unexpected Error"
Waarover gaat dit rapport?
Wat is er gebeurd? Selecteer uit het onderstaande
Gedetailleerde beschrijving
• Welke spelactie wilde je uitvoeren?
Undo the placement of a tile• Wat probeerde je te doen om deze spelactie te laten optreden?
Placed a tile, then clicked Undo button at top of screen• Wat gebeurde er toen je dit probeerde te doen (foutboodschap, melding op de statusbalk van het spel, ...)?
Error displayed, eg.: "Unexpected error: Sorry, another player made the same action at the same time: please retry. (reference: GS10 25/11 21:01:51)"
The game then went buggy:
- The problem tile stayed on the board and the player's turn continued (i.e. undo didn't work)
- The game wouldn't allow any other tile to be joined to the problem tile (for that player's turn)
- Other tiles from the player's reserve could be placed, but only on their own• Welke browser gebruik je?
Mozilla v5
Rapportgeschiedenis
Workaround found:
Place all possible tiles from the player's reserve onto the board. The top of the screen will display options to confirm or cancel. Pressing Cancel at this point will correctly undo all the pieces placed in that turn, and tile placement should be normal again (unless undo is clicked).
Players used the Undo function several times, which gave the same error message as before but otherwise worked correctly.
Then towards the end of the game, one player used the Undo button and the error message didn't appear. However, Undo didn't work. The tile they placed in error was still on their grid (playing area), and not connected to any other tile (which is not allowed by the rules). But everyone else saw that same tile was returned back to the player's reserve and not on their grid at all. So Undo had worked server-side, but not on that one client. The player was unable to select the problem tile in any case. This is the same as the previous report, but happened to a different player.
Pressing F5 solved this tile placement problem, confirming it's client-side only.
The error message is therefore a server-side separate bug with the same root cause.
Dit rapport aanvullen
- Andere tafel ID / zet ID
- Loste F5 het probleem op?
- Kwam het probleem meerdere keren voor? Altijd? Willekeurig?
- Als je een schermafbeelding van deze bug hebt (goede gewoonte), kun je Imgur.com gebruiken om deze te uploaden, de link kopiëren en hier plakken.