[SUGGESTION] [EDITOR] No overwrite objects default on/off

[Wafflem]

Recent updates have made it so all objects are always set to no overwrite.

I've tolerated this in the past, but the more I add objects, the more frustrating it gets. Sure, objects such as exits have to be set to no overwrite so e.g. builders' bridges won't be hidden behind the exit.

When I add a trapdoor or pickup skill or unlock button, it ends up behind terrain. This is very inconvenient for me. Please consider adding an option, that sets the default on whether an object I add is always set to no overwrite or not.

[namida]

We already have such an option for the One-Way setting on terrain, so it shouldn't be too hard to add one for this too. I'll see what I can do next time I'm working on the editor (I've been meaning to do some work on it for a few days now, but haven't got around to it yet; at this point I'm guessing most likely after the weekend I'll be able to).

I would advise against not using No Overwrite on entrances though; those too can interfere with the visibility of builder bricks (technically, all objects can, but entrances are more likely to do so than a small pickup skill for example).

[Simon]

DynaLem: What are you desigining? Buried buttons and pickups in the midst of terrain?

My hunch is that yes-overwrite is bad, so I want to learn about counterexamples.

-- Simon

[namida]

Re: Buttons, see here: http://www.neolemmix.com/old/levelimg/lpiii/0308.png
Most graphics for them are like this; designed to be in front of terrain.

I'm not so sure with pickup skills. Perhaps the intention is to place them in a fairly narrow corridor?

[IchoTolot]

I really like the new no-overwrite standard, as most of my objects tend to have it.
Also this way, I never forget to make the exit/entrance no-overwrite aswell:)

[namida]

Added an option for the next update.

Default is yes to setting No Overwrite by default, but as always, the default probably won't set correctly for people updating existing installations so if you want this setting on and you're upgrading from an older version, be sure to check it's configured.