i30817

I think this comes from restoring save games after starting a new game. I think the game is storing 'stuff' in savegames and reacts badly in some conditions: https://github.com/onitake/ags/pull/2/files#diff-5a305e749373fc1ae503198497ac396cL505 Maybe...

I found something interesting now on the current version of AGS 3.5 with a tentative fix for https://github.com/adventuregamestudio/ags/issues/799. If you run the game once (with the right libagsspritefont.so) you'll start...

Yeah, that was what i was thinking (first for the zip because of the code for it in this pull request above has something to add 'extras' to saves). But...

Ahah, the copy is very different from the original ``` [graphics] render_at_screenres=0 windowed=0 [language] translation= [mouse] control_enabled=1 speed=2,000000 ``` edit: apparently it's kind of normal, at least according to Heroine's...

It's like this game in particular can't abide the partial file... I'll try to reintroduce the modifications and copy the complete acsetup.cfg file to the save dir after the first...

Weird. Deleting the game save dir (and any saves inside the game dir), making the game directory read only an making the acsetup include: ``` [misc] shared_data_dir=. user_data_dir=. ``` Makes...

I had expected that `user_data_dir=.` would nuke my chances of having working saves (it + the readonly squashfs dir is my hack for the weird crash with using the gamedir...

I found which property the game is trying to read on the `acsetup.cfg` on the save dir and crashes by process of elimination. ``` [sound] ``` If you add this...

FYI, i found this bug can be worked around (if the path to writable files when the game dir is readonly in linux is fixed on upstream ags, which is...

~~Also this goddamn game original acsetup.cfg has a property named 'firstboot' which is probably the reason of this weirdness. Damn engine forks.~~