Network and hub settings
Batch limits, numeric caches, movement tiers, locator cadence, and combat priority.
Consider the client experience
Batching and distant tiers can reduce visible update frequency. Test movement, teleport, combat, tab lists, and packet plugins under real load. Native transport depends on OS/runtime support and Paper policy.
Option reference
All options below belong in nusa-global.yml and require a full restart. Missing keys use defaults. Ranges include both ends unless marked >.
| Complete key | Type / default | Range / unit | Purpose, effects, and when to change |
|---|---|---|---|
hub-networking.shared-cache-entries | integer8192 | 1..65536 entries | Short-lived numeric encode-cache capacity, not a world cache. More entries can use more memory.Applies when: feature-flags.shared-packet-encoding |
hub-networking.near-distance | number8 | >0..4096 blocks, finite | 3D near-tier distance. Changed nearby player positions/head rotation can update every tick; far delivery is less frequent.Applies when: feature-flags.tiered-entity-updates |
hub-networking.far-interval | integer4 | 1..20 tick | Far visible player position/head interval. Increasing it reduces visual smoothness, not simulation rate. Combat priority may bypass it.Applies when: feature-flags.tiered-entity-updates |
hub-networking.waypoint-far-interval | integer1 | 1..4 tick | Opt-in far-player locator cadence. One retains native refresh. Near, mounted, non-player, and direct API updates stay immediate.Applies when: feature-flags.tiered-entity-updates |
hub-networking.snapshot-interval | integer4 | 1..20 tick | Tier-distance snapshot interval. Stale hints fall back to current distance on main through the tracking pool.Applies when: feature-flags.tiered-entity-updates |
hub-networking.max-snapshot-players | integer1024 | 2..2048 players | Optimization snapshot bound. Overflow falls back; it does not set max-players or hide players.Applies when: feature-flags.tiered-entity-updates |
hub-networking.tab-window-millis | integer200 | 1..1000 ms | Numeric tab batching window. Main networking ticks perform flushes, so tick lag can extend actual delay.Applies when: feature-flags.batch-tab-list |
hub-networking.max-tab-entries | integer4096 | 1..16384 entries | Entry cap before a tab batch flush. Ordering barriers can flush earlier; not all updates are batched.Applies when: feature-flags.batch-tab-list |
combat-priority-override.enabled | booleantrue | true / false | Recent damage pairs bypass far movement throttling and receive every-tick position/rotation updates for the configured window.Applies when: independent override; affects eligible far-throttled damage pairs |
combat-priority-override.window-ticks | integer80 | 1..1200 tick | Priority duration since recent damage; 80 ticks is about four seconds at 20 TPS. Pairs then return to distance tiers.Applies when: independent override; affects eligible far-throttled damage pairs |
networking.flush-consolidation | booleantrue | true / false | Consolidate PLAY flushes. False disables the Nusa tuning handler; login/configuration ordering stays native.Applies when: feature-flags.netty-tuning |
networking.ip-tos | integer24 | 0..255 | Advisory traffic-class hint. Zero keeps OS policy. OS/network equipment can ignore it; priority is not guaranteed.Applies when: feature-flags.netty-tuning |
networking.tcp-fastopen | booleantrue | true / false | Try Fast Open when native listener, kernel policy, and client support it. Does not enable kernel policy itself.Applies when: feature-flags.netty-tuning |
networking.tcp-fastopen-backlog | integer256 | 1..65535 connections | Listener Fast Open backlog hint. Change only with an understanding of platform policy.Applies when: networking.tcp-fastopen with a supported native transport |
networking.chunk-batch-max-packets | integer32 | 1..1024 packets | Serialized packets per connection cohort. Larger values can retain more bytes and increase chunk delivery delay.Applies when: feature-flags.chunk-compression-batching |
networking.chunk-batch-max-bytes | integer2097152 | 1024..8388608 byte | Cohort byte cap. Oversized packets bypass batching; not a cap on all outbound memory.Applies when: feature-flags.chunk-compression-batching |
networking.chunk-batch-delay-millis | integer1 | 0..10 ms | Drain timer target. Zero means the next event-loop opportunity, not immediate delivery.Applies when: feature-flags.chunk-compression-batching |
Legacy aliases and limits
The primary group is combat-priority-override. Legacy hub-networking.combat-priority-override.enabled and .window-ticks remain accepted with the same bounds/defaults. If both forms are explicit, their values must agree. Prefer primary keys for new edits.
Player density and network pressure determine fan-out cost. Cache/pooling flags do not prove acceleration and IP_TOS is not network protection. Read the hub guide before reducing visual update cadence.