Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollbacks may be bugged #2072

Open
spjspj opened this issue Jul 13, 2016 · 10 comments
Open

Rollbacks may be bugged #2072

spjspj opened this issue Jul 13, 2016 · 10 comments
Assignees
Labels

Comments

@spjspj
Copy link
Contributor

@spjspj spjspj commented Jul 13, 2016

1.4.13v1 may have introduced bugs with rollbacks. Possible changes that I can think of that broke it were the shrinking of the panel sizes (possible??) or possibly the Ctrl+Click (unlikely)

@dylan1020
Copy link

@dylan1020 dylan1020 commented Jul 13, 2016

Rollbacks seem to be bugged right now. It doesn't roll back everything (like creatures no longer attacking and creatures that have died)

@spjspj
Copy link
Contributor Author

@spjspj spjspj commented Jul 15, 2016

fd60e43 may have something to do with it.

@drmDev
Copy link
Contributor

@drmDev drmDev commented Jul 19, 2016

Another report on the forums regarding it:
"Rollback glitch when playing opponent (human NOT AI).
Person passed the turn, I had end step selected and it rolled right through my turn to the end and went to my opponent's turn. He then selected rollback to start of previous turn. It went back to the start of my turn, after my turn was over it skipped his turn and gave me another turn.

This has now happened with two different opponent's with at least one of us being skipped after a rollback occurs."

@drmDev
Copy link
Contributor

@drmDev drmDev commented Jul 20, 2016

Another report on reddit:
"I've encountered a very situational bug regarding Flagstones of Trokair. I cast Smallpox and sacced Flagstones of Trokair, but before the flagstones trigger resolved, my opponent requested a rollback. I accepted and when the rollback happened, my Flagstones was gone and the trigger was still on the stack, however, the computer didn't allow either of us to have priority."

@drmDev
Copy link
Contributor

@drmDev drmDev commented Aug 15, 2016

With Emrakul, the Promised End: "If you roll back once or twice during your opponent's controlled turn, the opponent will not get an extra turn for some reason. " #2168

@LevelX2 LevelX2 self-assigned this Sep 29, 2016
@LevelX2
Copy link
Contributor

@LevelX2 LevelX2 commented Sep 29, 2016

Creature that dies during combat was not returned to battlefield after rollback to start of current turn after the combat..

@quercitron
Copy link
Contributor

@quercitron quercitron commented Oct 12, 2016

Could not reproduce locally any of rollback bugs using a trivial scenario (some creatures die, then rollback to the current/previous turn start). Any suggestions how it can be reproduced?

@tebo37
Copy link

@tebo37 tebo37 commented Apr 3, 2020

Bump - this is definitely still happening. Upon rolling back, one player is unable to obtain priority ever again until the game ends. The reddit trick posted above did not work for us after 30+ attempts.

@JayDi85
Copy link
Member

@JayDi85 JayDi85 commented Jun 15, 2020

How to fix: remove all changeable data from GameImpl to GameState:
shot_200615_230613

Suspicious data from GameImpl (can be moved to GameState, but need research):

  • checkPlayableState
  • lki
  • lkiCardState
  • lkiExtended
  • shortLivingLKI
  • saveGame - not used
  • permanentsEntering
  • losingPlayer
  • stateCheckRequired - outdated and not used
  • infiniteLoopCounter -- infinite loop check
  • lastNumberOfAbilitiesOnTheStack -- infinite loop check
  • lastPlayersLifes -- infinite loop check
  • stackObjectsCheck -- infinite loop check
  • enterWithCounters
  • concedingPlayers
@LevelX2 LevelX2 added this to open issues in Monitor rollback problem via automation Jun 20, 2020
LevelX2 added a commit that referenced this issue Jul 17, 2020
@LevelX2 LevelX2 moved this from open issues to Verfy if fixed in Monitor rollback problem Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Monitor rollback problem
  
Verfy if fixed
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants