-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ en
简体中文: FAQ · English
A: Yes. With storage.enabled = true, chunk payloads are written as ZSTD type 126 inside the unchanged .mca shell. Back up worlds before first enabling.
A: Saves remain type 126 and require reinstalling a matching MC version of Hassium. If you want to decouple: set storage.enabled = false (keeps network benefits until chunks are overwritten with vanilla Zlib) before uninstalling.
A: Reinstall a Hassium version compatible with that save. Compression resources are bundled with Hassium; users do not install or configure them separately.
A: From 1.21.5 onward, the client cache is not guaranteed to be cross-MC-version compatible. Old chunks are lazily overwritten (MISS → refetch → persist); there is no full invalidate on start, but the first session may see more misses. See Compatibility.
A: Yes by default. With compat.requireClientMod = false (default), vanilla clients connect via the vanilla protocol and benefit from server-side compression. Client cache, negotiated compression, and other advanced features require the mod on both sides.
A: No — it conflicts with network.globalPacketCompression. Escape hatches: network.globalPacketCompression = false or network.enabled = false (client cache only).
A: Escape via (1) network.enablePacketAggregation = false, or (2) add the packet ID to network.compressionBlacklist.
A: Pick one. Hassium is incompatible with Bobby. Remove Bobby from the client before enabling Hassium's beyond-view render.
A: No. It is multiplayer-only; singleplayer has no server-side view-distance limit.
A: Known limitation. The Fog Mixin is not implemented across the nine version segments; with RD > 32 the fog distance follows getEffectiveRenderDistance and far chunks may pop in. Recommended to keep RD ≤ 32.
A: Ring size depends on the gap between client RD and server view distance. Lower clientCache.maxRenderDistance, or disable clientCache.viewDistanceExtensionEnabled, to limit resource use. Beyond-view rendering reuses the existing cache eviction mechanism and adds no dedicated memory pool.
A: Off by default (network.dataPlane.enabled = false). Both features (control failover, weighted routing) are disabled by default; opt in by enabling and configuring reachable endpoints, then verify the six self-check markers in order. See Data-Plane-and-Failover.
A: When the stall exceeds controlStallMs (default 6s) and the UDP data plane is healthy, the server issues a FailoverPermit. The client does not proactively drop the current master; it switches to the next candidate under the permit. Finalize happens only when candidates are exhausted.
A: Yes. /hassiumc export produces a vanilla Anvil save (type 2 Zlib) that appears in the singleplayer menu and can be entered directly.
A: No. The cache holds only block states and block-entity NBT; no inventory, advancements, or world entities. See World-Export for full caveats.
A: This only appears in dev environments (Loom runtime) and is safe to ignore. Released client/server jars bundle the refmap and resolve targets normally.
A: The hot path is quiet by default. Toggle debug.* as needed: debug.metadataLogging / debug.networkLogging / debug.cacheLogging / debug.chunkApplyLogging etc. See Troubleshooting.
Hassium · GitHub · CurseForge · GPL-3.0-or-later