Alle Meldungen
Dungeon Roll Meldungen
#25221: "Game gets stuck after upgrading Mercenary to Commander following Delve 1"
fixed: Der Fehler wurde behoben
1
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
An einer Stelle konnte ich die Spieloberfläche nicht erreichen
Detaillierte Beschreibung
• Was wurde auf dem Bildschirm angezeigt, als du blockiert wurdest (weißer Bildschirm? Teil der Spieloberfläche? Fehlermeldung?)
"Updating game situation" at top of screen, selecting "Seek Glory" or "Retire to the tavern" action gives red banner error "Please wait, an action is already in progress"• Welchen Browser benutzt du?
Google Chrome v85
Meldungshistorie
fentesk • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
23. Sep 2020 6:10 • Two times (tables #113620225 and #113623576) playing as Mercenary (solo games), leveled up after the first round. The Mercenary card visually flips to Commander side correctly and then game gets stuck on "Updating game situation...". Delve number still shows as 1. When attempting to "Seek Glory" or "Retire to the tavern", a red error banner appears stating "please wait, an action is already in progress".
The game visually shows it is still in the Regroup Phase of Delve 1, even though the "Retire to the tavern" button was already pressed to end Delve 1. In the player area (upper right corner) the hourglass circles over my player name and my experience (stars) still show 0 above the text "Delve #1". The game clearly knows I earned enough experience to upgrade the Mercenary, but the bug seems to be somewhere in the code between checking to see if enough experience has been earned to flip to the master side, but before the Delve is fully completed and experience is awarded and shown in my current score.
As a side note, hovering over a remaining "Party" die, Treasure, or the Commander card still gives the normal hover text (and the Hero card visual has already been updated to the Commander side).
Refreshing with F5 allows the game to continue as expected so the bug does not fully break the game.
Both times I saw this error were in solo games with the Mercenary leveling up to Commander at the end of Delve 1. I do not currently know if this bug exists with other characters or after leveling following a different delve.
The game visually shows it is still in the Regroup Phase of Delve 1, even though the "Retire to the tavern" button was already pressed to end Delve 1. In the player area (upper right corner) the hourglass circles over my player name and my experience (stars) still show 0 above the text "Delve #1". The game clearly knows I earned enough experience to upgrade the Mercenary, but the bug seems to be somewhere in the code between checking to see if enough experience has been earned to flip to the master side, but before the Delve is fully completed and experience is awarded and shown in my current score.
As a side note, hovering over a remaining "Party" die, Treasure, or the Commander card still gives the normal hover text (and the Hero card visual has already been updated to the Commander side).
Refreshing with F5 allows the game to continue as expected so the bug does not fully break the game.
Both times I saw this error were in solo games with the Mercenary leveling up to Commander at the end of Delve 1. I do not currently know if this bug exists with other characters or after leveling following a different delve.
Artanis A • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
24. Sep 2020 4:55 • This sounds like what just happened to me in a solo game (table #113787808) playing as a Half-Goblin/Chieftain. I upgraded after Delve #2 though.
MGoulet • Der Fehler wurde von den Entwicklern bestätigt:
24. Sep 2020 13:03 •
24. Sep 2020 13:06 • Thanks, In your replay, I saw what happen.
fentesk • Der Fehler wurde behoben:
24. Sep 2020 20:42 • I pulled Mercenary again and everything since the change ran smoothly.
I had also seen this happen with some other heroes (but strangely not all...) and have not seen those since the change as well. The fix is working well!
I had also seen this happen with some other heroes (but strangely not all...) and have not seen those since the change as well. The fix is working well!
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.