Stacked pushblocks can cause void issue

[lahm86]

If the game is saved when Lara is standing on top of a pushblock, which itself is on top of another pushblock, when that save is reloaded Lara voids. If an earlier save, where she is not standing on the block, is loaded, she can only get on top of the block after it is pushed/pulled. This isn't an issue with single blocks, only when they are stacked.

https://streamable.com/za1zsz

Found by LORDmeSH1NE during rando testing. The above is original level data and this has been checked with enhanced saves both on and off.

[lahm86]

This seems to be caused by the order of the items as they're defined in the level file. If I switch items 1 and 9 in the level file for Khamoon, the issue doesn't occur. So I think what happens in the original is the top block comes first in the item list, so when the game reloads the save it sets the floor height to 2048. The bottom block comes later in the list, and it adds another 1024 to the height. So when they're the other way around, they each add 1024 only to the floor height.

So it's easy to workaround the issue (for the randomizer/custom levels) - should Tomb1Main implement a "FixKhamoonBlocks" option that does this? Or is it feasible to scan over the blocks based on their y pos in the savegame load logic so the floor height is amended in order?

[rr-]

I'd say the latter is the more universal and desirable fix.

[walkawayy]

So this happened because the top of the block was near a room portal.