This was initially observed during a multiplayer session while testing a race map. That map is not attached here, because I found that this is very easy to replicate; a test level is attached instead. Known to affect 0.10.26; other versions untested.
To reproduce: simply place an object and shove it out of the level using the keyboard controls. Alternatively, resize the level so the objects are no longer in bounds. Save the level. These objects persist through saves and will persist through multiple resaves.
You CAN remove the objects by resizing the level so they're back inside and then manually deleting them, but it's probably easier to simply edit the .txt file manually.
Exits cause problems in multiplayer as players may be assigned the out of bounds exits. Entrances cause problems always because Lix spawned outside of bounds immediately die.
Expected behavior: Out of bounds objects should be discarded after saving. I do think it makes sense to hold onto them temporarily for resizing purposes, though.
When moving selected pieces it may be beneficial for the editor to disallow movements that would result in the selection being entirely out of bounds.
bugtest.txt
The test level features only 2 pieces inside the level, a hatch and a platform. 8 terrain, 8 steel, and 8 exits have been placed, one each of:
Out of bounds in -X only
Out of bounds in +X only
Out of bounds in -Y only
Out of bounds in +Y only
Out of bounds in -X, -Y
Out of bounds in -X, +Y
Out of bounds in +X, -Y
Out of bounds in +X, +Y
(I say intended because it's possible I undershot some of them as I didn't math out the coordinates to make sure they reached the intended areas, but I believe I should have sent them sufficiently far).
There is also one out of bounds hatch to demonstrate Lix immediately dying after spawning from it.
SimonN
commented
3 days ago
This was initially observed during a multiplayer session while testing a race map. That map is not attached here, because I found that this is very easy to replicate; a test level is attached instead. Known to affect 0.10.26; other versions untested.
To reproduce: simply place an object and shove it out of the level using the keyboard controls. Alternatively, resize the level so the objects are no longer in bounds. Save the level. These objects persist through saves and will persist through multiple resaves.
You CAN remove the objects by resizing the level so they're back inside and then manually deleting them, but it's probably easier to simply edit the .txt file manually.
Exits cause problems in multiplayer as players may be assigned the out of bounds exits. Entrances cause problems always because Lix spawned outside of bounds immediately die.
Expected behavior: Out of bounds objects should be discarded after saving. I do think it makes sense to hold onto them temporarily for resizing purposes, though.
When moving selected pieces it may be beneficial for the editor to disallow movements that would result in the selection being entirely out of bounds.
bugtest.txt The test level features only 2 pieces inside the level, a hatch and a platform. 8 terrain, 8 steel, and 8 exits have been placed, one each of:
Out of bounds in +X, +Y
(I say intended because it's possible I undershot some of them as I didn't math out the coordinates to make sure they reached the intended areas, but I believe I should have sent them sufficiently far).
There is also one out of bounds hatch to demonstrate Lix immediately dying after spawning from it.