ID:2833735
 
Not a bug
BYOND Version:515.1594
Operating System:Windows 10 Home 64-bit
Web Browser:Firefox 106.0
Applies to:Dream Maker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary: When using the map editor’s palette, the Edit Instance... command acts like the New Instance... command, resulting in a new instance being created (with a new instance ID number) and existing instances located on the map remaining unchanged.

Numbered Steps to Reproduce Problem:
1) Create a new map and place some turfs
2) Use the Edit instance... command from the palette on the instance of the turfs placed in step 1.
3) Change a variable (such as density)
4) On the map, select a turf placed in step 1 as the active object.
5) Observe from the right-hand individual instance editor that the variable edited in step 3 has not been changed. This result can also be verified in game.

Expected Results: For Edit Instance... to result in changes being made to all copies of that instance on the map.

Actual Results: Edit Instance... appears to act similarly to New Instance...

Does the problem occur:
Every time? Or how often? Everytime.
In other user accounts? Untested.
On other computers? Untested.

When does the problem NOT occur? Unknown.

Workarounds: Use Find/Replace to replace unedited instances with the newly edited instance.
Lummox JR resolved issue (Not a bug)
This is intentional behavior. The palette now behaves like an actual palette.

The old approach of having everything on the map hot-linked to the palette entry was extremely unwieldy, and it also created weird situations where related instances (e.g. one with another additional var changed) didn't change on edit.

Instead, Edit Instance now edits the palette entry but not what's on the map. The original "pop" will still exist if it exists on the map.