ID:2828885
 
Resolved
Map files were being read with underlay turfs displaying in the reverse order, and saving also reversed the order of underlay turfs.
BYOND Version:515.1590
Operating System:Windows 10 Home
Web Browser:Chrome 106.0.0.0
Applies to:Dream Maker
Status: Resolved (515.1591)

This issue has been resolved.
Descriptive Problem Summary:

BYOND Beta Version 515.1590 is causing certain turfs to be invisible after compile. However, running the world causes the certain turfs to appear but not unless you overlay the turfs together to only have them disappear if compile.

Example: https://imgur.com/k4l7SIi

Zip File: https://www.dropbox.com/s/yzs6t2jb9md6kkt/ map_layering_src.zip?dl=0

Numbered Steps to Reproduce Problem:

1. Open Dream Maker to the project.
2. Go to map editor file.
3. Place the turfs in the following order (1) X, 2) Y, 3) Z) together.
4. Go to Build to Compile/Clean Compile.

Code Snippet (if applicable) to Reproduce Problem:
/*
These are simple defaults for your project.
*/


world
fps = 25 // 25 frames per second
icon_size = 32 // 32x32 icon size by default

view = 6 // show up to 6 tiles outward from center (13x13 view)


// Make objects move 8 pixels per tick when walking

mob
step_size = 8

obj
step_size = 8

turf
icon='turf.dmi'
icon_state="1"

X
icon_state = "2"
Y
icon_state = "3"
Z
icon_state = "4"


Expected Results:

All of the turfs are visible after compile.

Actual Results:

Two of the 3 (X,Y,Z) are invisible but still remains if you right click the turf.

Does the problem occur:
Every time? Or how often? Only in this situation
In other games? N/A
In other user accounts? N/A
On other computers? N/A

When does the problem NOT occur?

During stable version 514.

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.)

This problem did not exist in the stable version.

Workarounds:
N/A.
Confirmed. The file is correct and it shows up correctly in Dream Seeker; it just seems to be that the map is re-loading them in the wrong order in the editor. This also means that re-compiling will reverse the order of the layers so they appear in the map editor correctly, but are now wrong in the file and in the .dmb.
Lummox JR resolved issue with message:
Map files were being read with underlay turfs displaying in the reverse order, and saving also reversed the order of underlay turfs.