Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I made a transaction system that stores changes so it shouldn't be a nightmare to add in, I just didn't have enough time to walk it back 

I'll probably leave it as-is for the jam page as I'll probably just do some minor fixes once voting is over, but if I decide in the future to continue the game there will definitely be an undo button

(+1)

if i were to make one again, I would probably save the state of the game after each input than save each input, that theoretically would have solved many of my problems. it may or may not help depending on the game, but hopefully this advice is helpful

(5 edits)

That would certainly work, but a transaction system would probably be a lot less memory. I'm actually saving the results rather than the inputs.  Something like a player moved 1 unit right and 3 units down and died, or a box moved one unit left

As you said it depends on the game so the full level state should be fine for a lot of cases