X-Factor Optimization 1.0.4

X-Factor Optimization 1.0.4 is a chunk-throughput, networking, and multiplayer stability update built on top of the rendering gains introduced in 1.0.3.

This release does not replace the existing optimization stack. Instead, it adds dedicated chunk-mesh threading and networking optimization, while also updating X-Factor's custom compatibility and session-safety components after extensive multiplayer/menu testing.

Highlights

Added Multicore Magic for dedicated client chunk-mesh worker threading
Added Krypton 0.3.1 for Minecraft networking-stack optimization
Updated Client State Guard 1.0.4 → 1.0.6
Updated Rendersnap Sodium Menu Compat 1.0.13 → 1.0.14
Changed Greedy Meshing's Aggressive Greedy option from ON to OFF
Kept Greedy Meshing itself enabled
No existing Modrinth-managed mods were removed
No other existing Modrinth-managed mod versions changed

Added: Multicore Magic

X-Factor 1.0.4 adds:

Multicore Magic

Multicore Magic gives client chunk mesh building its own dedicated thread pool instead of letting that work compete as heavily with world generation and other background jobs.

This fills an important gap in X-Factor's chunk pipeline.

The relevant stack now looks roughly like:

World-generation calculations
        ↓
Ferrite
        ↓
Lighting
        ↓
ScalableLux
        ↓
Chunk mesh building
        ↓
Multicore Magic
        ↓
Geometry reduction
        ↓
Greedy Meshing
        ↓
Rendering
        ↓
Sodium + Rendersnap + ImmediatelyFast

The goal is not simply to use more threads.

The goal is to separate chunk mesh work more cleanly so terrain can be prepared without unnecessarily competing with other background workloads.

This should be most noticeable during:

Fast exploration
Rapid chunk traversal
High render distances
Large terrain updates
Situations where chunks are loading faster than their meshes can be prepared

Added: Krypton

X-Factor 1.0.4 adds:

Krypton 0.3.1

Krypton targets Minecraft's networking stack.

Its optimizations focus on areas such as:

Netty packet handling
Packet serialization
Network memory overhead
Flush behavior
General networking efficiency

Krypton is included as an additional networking optimization layer alongside X-Factor's existing multiplayer components.

Because X-Factor also includes ViaFabricPlus and custom connection/session safety code, networking remains an area that should be tested carefully across different servers, proxies, and protocol versions.

If a networking regression appears, reports should include the full latest.log, the server being used, and whether ViaFabricPlus protocol translation was active.

Client State Guard 1.0.6

X-Factor 1.0.4 updates Client State Guard from:

1.0.4

to:

1.0.6

This is a major multiplayer stability update.

During testing, Minecraft could temporarily lose access to its ClientLevel while navigating through:

Pause
→ Options
→ Video Settings
→ back

If an entity metadata packet arrived during that short window, vanilla Minecraft could attempt to access the missing world and throw a null-pointer exception.

That packet-handler exception could then terminate the multiplayer session.

Client State Guard 1.0.6 now directly protects the affected entity handlers before vanilla can dereference a missing ClientLevel.

Protected paths include:

handleSetEntityData
handleEntityPositionSync
handleSetEntityMotion

When the current multiplayer listener temporarily has no world:

Entity packet arrives
        ↓
ClientLevel is unavailable
        ↓
unsafe entity update is skipped
        ↓
network connection is preserved

It does not treat a temporary null world/player as proof that the player intentionally disconnected.

Session isolation

Client State Guard also keeps the session-isolation improvements introduced during 1.0.5 development.

Once an old ClientPacketListener has genuinely been replaced, old-session traffic can be isolated so it does not contaminate the new server session.

This is designed to prevent stale data such as:

Chat
Tab-list updates
Player-list data
World/block updates
Entity updates
Disconnect-state packets

from an old listener affecting a replacement session.

The current active listener is protected from being closed merely because a menu transition briefly exposes incomplete client state.

Rendersnap Sodium Menu Compat 1.0.14

X-Factor 1.0.4 updates:

Rendersnap Sodium Menu Compat
1.0.13 → 1.0.14

This update focuses on safer Video Settings navigation.

Earlier compatibility logic could retain stateful menu objects across different screen opens. In unusual multiplayer transitions, that created the possibility of returning to the wrong parent screen.

Version 1.0.14 changes the menu bridge so that:

Rendersnap button widgets are recreated for each menu open
Stateful widget instances are no longer cached between screens
Video Settings prefers the current vanilla Options screen as its return parent
Broad reflective searching for arbitrary parent screens has been removed
A live multiplayer world is not intentionally routed from Video Settings directly to the title screen or world/server-selection menus
Sodium screen-construction and search-layout reflection metadata can still be cached for performance

The two Rendersnap controls remain integrated into Sodium's Video Settings layout.

Greedy Meshing: Safer Default

Greedy Meshing remains one of the central rendering optimizations in X-Factor 1.0.4.

However, one default has changed:

1.0.3:
aggressiveGreedy=true

1.0.4:
aggressiveGreedy=false

The rest of the main Greedy Meshing configuration remains unchanged:

enabled=true
greedyWater=false
mergeOrientedBlocks=true
debugWireframe=false
debugComparison=false

Normal Greedy Meshing is still enabled and continues to merge compatible terrain geometry.

The Aggressive Greedy mode is now disabled to use the more conservative meshing path and reduce the visual/lighting trade-offs associated with merging across additional ambient-occlusion boundaries.

This means X-Factor keeps the core geometry-reduction benefit without forcing the most aggressive available mode.

About the previous 900+ FPS result

X-Factor 1.0.3 development testing showed an observed FPS increase exceeding 900 FPS in both singleplayer and multiplayer scenarios after Greedy Meshing was introduced.

That measurement was made with the previous 1.0.3 configuration, where Aggressive Greedy was enabled.

Because 1.0.4 now uses the safer non-aggressive setting, the old +900 FPS result should be treated as a 1.0.3 test result, not a guaranteed 1.0.4 benchmark.

Performance will continue to vary heavily by hardware, world geometry, resolution, render distance, shaders, and server conditions.

Compared With X-Factor 1.0.3

Added

Krypton 0.3.1
Multicore Magic

Updated

Client State Guard
1.0.4 → 1.0.6

Rendersnap Sodium Menu Compat
1.0.13 → 1.0.14

Configuration Changes

Greedy Meshing:
aggressiveGreedy=true
→
aggressiveGreedy=false

Removed

No mods removed

Unchanged

All other Modrinth-managed mods from X-Factor 1.0.3 remain on the same versions in 1.0.4.

Existing Optimization Stack Retained

X-Factor 1.0.4 continues to include the existing performance stack, including:

Sodium
Lithium
Rendersnap
ImmediatelyFast
Greedy Meshing
More Culling
Ferrite
FerriteCore
ScalableLux
Async
Modernica
Optimized Block Entities
Particle Core
BadOptimizations
Signs Faster
Gnetum
PAPI
Tick Sync
Eslium
Iris
Oxidizium Panama
Quantified API

X-Factor's custom compatibility components also remain:

Client State Guard
Rendersnap Sodium Menu Compat
X-Factor Compatibility Patcher
xfactor-compatibility-patches.txt

What 1.0.4 Is Trying to Improve

X-Factor 1.0.3 was primarily about reducing visible terrain geometry.

X-Factor 1.0.4 expands beyond that.

The optimization pipeline now covers more of the work surrounding the rendered frame:

Worldgen calculations
        ↓
Lighting
        ↓
Chunk mesh scheduling
        ↓
Geometry reduction
        ↓
Rendering
        ↓
Networking
        ↓
Session/menu safety

The focus is therefore not only on maximum FPS.

The goals of 1.0.4 are:

Keep chunk rendering responsive during movement
Better use available CPU resources for chunk mesh preparation
Reduce networking overhead where possible
Prevent menu transitions from destroying otherwise valid multiplayer sessions
Prevent stale sessions from contaminating later connections
Keep Greedy Meshing's benefits with a more conservative visual default

Recommended Testing

For performance comparisons between 1.0.3 and 1.0.4:

Use the same world/server.
Use the same render and simulation distances.
Keep resolution and shader state identical.
Disable VSync for maximum-throughput testing.
Use the same FPS cap.
Test rapid traversal through already-generated and fresh terrain.
Test a busy multiplayer lobby.
Repeat each workload more than once.

For the multiplayer stability changes, test:

Join server
→ Pause
→ Options
→ Video Settings
→ back
→ resume gameplay

Repeat the sequence several times.

Also test:

Server A
→ disconnect normally
→ Server B

and confirm that chat, tab-list decorations, boss bars, player-list state, and other server-specific data do not leak between sessions.

Updating From X-Factor 1.0.3

A clean launcher update is recommended.

If updating an existing instance:

Back up worlds, screenshots, and personal configuration changes.
Update the pack through the launcher.
Remove duplicate older mod versions if the launcher leaves them behind.
Make sure only the supplied Client State Guard and Rendersnap Sodium Menu Compat versions remain.
Launch the pack.
Review the X-Factor Compatibility Patcher wizard if it appears.
Restart after an approved compatibility patch if requested.

Do not use a launcher-wide Update All Mods action on X-Factor.

The pack contains compatibility-sensitive rendering, networking, and Mixin combinations that are tested together.

Compatibility

Minecraft: 26.2
Mod loader: Fabric
Environment: Client-focused
Rendering: Sodium-based
Shaders: Iris included
Server installation: Not normally required

Reporting Problems

When reporting an issue, include:

X-Factor version
Minecraft version
Fabric Loader version
Java version
CPU and GPU
Full latest.log
Exact reproduction steps
Singleplayer or multiplayer
Server address/name when relevant
ViaFabricPlus target protocol when relevant

For performance reports, also include:

Render distance
Simulation distance
Resolution
FPS cap
VSync state
Shader state
Spark profile link when available

For menu/session problems, include the exact screen sequence used before the issue.

Join the X-Factor Discord

X-Factor Optimization