Default Laser State

[Electronus]

Is your feature request related to a problem? Please describe.

I am always toggling my lasers off, either on spawn or after using dev tools. While this wouldn't help with the second part would be nice for when im just going into a world to relax.

Describe the solution you'd like

A setting to set the default laser state to on or off.

Describe alternatives you've considered

Toggling the laser manually.

Additional Context

No response

Requesters

Electronus

[shiftyscales]

Considering lasers remain active in userspace regardless to how it is set in worldspace, I could see this being a potentially useful addition.

That raises a question for me though- I wonder if the laser state would make more sense as a persistent value across worlds?

You raised the point of having to always toggle them off, but I think it might be more intuitive if their state persisted across all sessions you are in. E.g. if you already had them off they would stay off in new worlds you join.

Prior to the settings rework, user locomotions tried to behave in a similar way where it would try to place you in whatever locomotion you were previously in at the time of joining the new world/session. (Now it instead just has a priority list it uses instead.)

Seeking input from @Frooxius.

[TisFoolish]

Wouldn't that be a separate feature request? I think having a setting for default laser state would still be good. While I'd like to have my lasers on all the time, I can definitely see users wanting to not have them on by default when starting res.

[Electronus]

Hmmm persisting is a good idea, so to add to it: perhaps a default laser state setting with three options, off , on, and persist?

I do have to admit that would probably be a decent chunk of work for what would be a minor QOL change at most but hey.

[shiftyscales]

I raise it because I'm getting to the underlying issue of the situation, @TisFoolish - the concern raised was at needing to continually change the state of it.

One possible solution is setting a default state by a setting, but if that still set the default state for each new world the user joined- the user would need to continually turn on their lasers instead of turning them off.

I see them as solving different, but related problems.

E.g. having a setting to set them on, off, or remember their last state (similar to the mute persistence setting that was recently added), and separately to that- having the state persist between sessions so there is never any confusion around when lasers are/aren't on.