This is purely a personal preference sort of recommendation/post but there are certain defaults on some devices that should be left for unique edge cases rather than automatically applied. They are here in the order I raged at them when I forgot to uncheck their box/change the drop down:
Verse Creative Device defaults to “Visible In Game” - Give me a single good reason why someone wants to see the computer in game.
Item Granter’s “On Grant Action” defaults to “Clear Inventory” - The most intrusive option should not be the default.
Accolades device’s “Triggering Player Only” unchecked by default - 99% of accolades are used for individual player achievements
Hud Messages’s defaults to “Queue Message for Join In Progress Players” - I have never once used this due to the buggy nature of any device that checks “join in progress” players
Mutator Zones does not Allow Weapon Fire as default - I would greatly prefer the mutator zone to do practically nothing when first placed, then the individual settings be added by me. (See also the mutator vfx default off)
-Barrier device to have an invisible material when placed as a default.
-Creature Spawner to not be visible, or break and have its spawn radius set to random rather than max distance because that collides with the spawner and causes creatures not to spawn (and being the default, it doesn’t work by default)
-No device should have its device base visible by default, except if its a trap
-(for Creative too) Island settings:
Time limit: None
Autostart: 30 seconds
Game Start Countdown: Off (personal preference)
Vehicle Trick Score Multiplier: 0 (messes up score otherwise)
Time of Day: 3PM (so you can see while building)
Allow Building: None (most maps do not have building)
Environmental Damage: Off
Jump fatigue: Off
Glider redeploy: Off
Timer Direction: Count Up (only 1-round games need count down)
and please for the love of what is holy, let me turn the message log Off in UEFN, I never care what it has to say, except for UEFN validation blockers (not all errors, only the blockers). Everytime I import something, it bumps in front as if I care about the smoothing groups.
Not connected devices should be expressed as MyDevice: ?my_device = false in verse rather than MyDevice: my_device = my_device {}. Everyone should properly unwrap the option type to either get the device that was set through the editor or find out that it wasn’t set yet. It is incorrect to assume the value is set because it has a non-functional default value.
An empty array is correctly empty in the editor. A value that is set to none in the editor should be reflected as an optional value in code with the value of false.
+1,000,000 on the turn message log off. I come close to raging every time I see that thing appear on my screen at this point… just blocking validation errors thanks.
I agree with every point, but it seems we are asking for more bugs here. Changing current defaults might be risky. Little gain while greater risks.
And there are things obviously more broken than the default values. I suspect when the device market place is introduced, we probably won’t use built-in devices a lot.
OMG i cant tell you how many times ive had random beeping sounds every second on my maps only to find out it was a random timer that is set to have audio alerts by default. who the hell places a timer and wants to hear a beep every second? thats a very specific need for a bomb or something. audio disabled should be default.
True, but the upgraded speed boost trap should not have had an upwards boost to begin with given the original speed boost trap had no upwards boost.
Sure making the movement modulator set to speed boost mode have no upwards boost by default will break some maps, but the fact that it has an upwards boost broke other maps.
