Sable: FTB Skies 2: Aero config options

If Sable should attempt to authenticate with clients and send them sub-level movement data over UDP

If the entire Sable UDP Networking pipeline should be disabled. This can improve compatibility with certain mods like Replay mod and certain networking setups, but will have worse performance and latency for networking sub-levels.

If Sable should log when saving sub-levels for a dimension.

Whether sub-levels can split when parts are separated

Keeps sub-levels with intersecting players from unloading at all

If Sable should use verbose logging for its serialization system and the holding chunk-map. Not recommended- for debugging purposes only.

Prunes and deletes empty sub-level storage files. Experimental.

The cooldown in ticks between sub-level punches

The strength multiplier applied to the vertical component of downward sub-level punching impulses (to prevent jumping by punching the ground while standing on something light)

The strength multiplier applied to sub-level punching impulses

The maximum y coordinate sub-levels can exist at

The minimum y coordinate sub-levels can exist at

Sub-level splitting heatmap steps that take place per tick

The distance to network sub-levels to players at

The fraction of velocity that is retained when a sub-level is loaded in. A value of 0.0 will indicate that no velocity should be carried over, while a value of 1.0 would carry over 100% of velocity on load.

How many times the physics simulation is stepped in every second. Higher values will be significantly more performance intensive, but will have higher accuracy.