Using relative FLOAT_PLANE breaks the map editor
Numbered Steps to Reproduce Problem:
1. Make turfs have plane FLOAT_PLANE - 2
2. Make non-turfs have plane FLOAT_PLANE - 1
Code Snippet (if applicable) to Reproduce Problem:
/turf
plane = FLOAT_PLANE - 2
/obj
plane = FLOAT_PLANE - 1
Expected Results:
the FLOAT_PLANE-1 shows up in front of FLOAT_PLANE-2
Actual Results:
the FLOAT_PLANE-2 shows up in front of FLOAT_PLANE-1
Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?
When does the problem NOT occur?
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Workarounds:
set the FLOAT_PLANE shizz at runtime I guess