[Savestates] Store EntityAI in savestates#298
Draft
ScribbleTAS wants to merge 3 commits into
Draft
Conversation
ScribbleTAS
force-pushed
the
savestates/entity-ai
branch
from
July 12, 2026 19:25
ddae918 to
959c0fa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A big problem for TASing in general is the fact that entity AI is not stored in the world files... All entities will reset once a world is loaded, which makes savestates around entities very inaccurate. So much so, that the EntityRNG will desync between savestates.
To fix this, I would need to write custom serialisation for ~60 different classes, each doing something slightly different...
Not fancying that, so instead I employed the help of everyones least favourite json library gson!