There's been a few issues with suggesting to persist state between restarts like:

• Tick freeze state
• Tick rate
• Edited mobcaps
• Loggers per player (currently there's only the defaultLoggers rule)
• Fake players maybe (currently there's keepalive.sc)
• /track state (although maybe we should move it forward with scarpet first)

A workaround for some of those right now is having a scarpet app to automatically run the command to set these, at least if you always want them to be the same at the start.

Opinions?
Should this be controllable per every part of state? Or all either save or not?
Implementation suggestions?

This would be highly appreciated.

I use tick freeze (technically superhot) to pause the server when nobody is online. This works great until the server crashes and then requires manual intervention. Persistent state would prevent this desync.

I'd also appreciate an explicit option for tick freeze style commands. /tick freeze on over /tick freeze. Again for the same reason, a datapack can't know if it's toggling it on or off.