X-Factor Optimization 1.0.6

X-Factor Optimization 1.0.6 is a chunk rendering, compatibility, and settings integration update built on top of the stability and client-state work introduced in 1.0.5.

This release keeps the existing 26.2 optimization stack largely unchanged. The main changes are the addition of Multicore Magic, a proper RenderSnap integration inside Sodium's Video Settings menu, and new compatibility rules to make the two systems work together safely.

Highlights

• Added Multicore Magic 1.0.2
• Added a dedicated chunk mesh building thread pool
• Updated RenderSnap Sodium Menu Compat from 1.0.0 to 1.0.2
• Added a dedicated RenderSnap section to Sodium's Video Settings
• Added Performance and Visuals RenderSnap buttons
• RenderSnap now opens through Sodium instead of replacing the normal Video Settings screen
• Fixed a RenderSnap / Multicore Magic LevelRenderer Mixin conflict
• Added new RenderSnap compatibility patch rules
• Existing Sodium + Iris rendering combination remains unchanged
• Existing Client State Guard and compatibility patching systems remain in place

---

Multicore Magic 1.0.2

X-Factor 1.0.6 adds:

Multicore Magic 1.0.2

This is the main new performance component in X-Factor 1.0.6.

Minecraft normally performs chunk mesh building alongside other background work. During rapid movement, especially while generating or loading terrain, chunk rendering can therefore compete with other jobs for CPU time.

Multicore Magic gives chunk mesh building its own dedicated worker pool.

The intended path is now effectively:

Chunk mesh work arrives
        ↓
Multicore Magic
        ↓
Dedicated chunk-builder executor
        ↓
Chunk meshes are processed separately
        ↓
Less competition with unrelated background work

This does not attempt to make Minecraft's entire game loop magically multithreaded.

The optimization targets a specific workload: building the render meshes used to display chunks.

This makes it particularly relevant during workloads such as:

High-speed movement
Fresh terrain traversal
Rapid chunk loading
Large render distances
Frequent chunk rebuilds

---

RenderSnap and Multicore Magic Compatibility

Further testing revealed an important conflict between RenderSnap and Multicore Magic.

Both mods attempted to redirect the chunk-worker executor inside:

LevelRenderer

The conflicting paths were:

RenderSnap
world.ChunkWorkerLimitMixin

and:

Multicore Magic
LevelRendererMixin

Because both redirects targeted the same operation at the same priority, only one could successfully apply.

RenderSnap then failed its required Mixin injection check, causing Minecraft to stop during initialization.

X-Factor 1.0.6 resolves this by allowing Multicore Magic to own this optimization path and disabling RenderSnap's competing redirect.

The supplied compatibility rules now include:

Rendersnap-1.3.1-mc26.2.jar: =world.ChunkWorkerLimitMixin

The resulting path is:

Chunk rendering initializes
        ↓
Multicore Magic redirect applies
        ↓
RenderSnap competing redirect is disabled
        ↓
No duplicate executor redirect
        ↓
LevelRenderer initializes normally

This allows X-Factor to use Multicore Magic's dedicated chunk-building system without retaining two optimizations that attempt to control the same operation.

---

RenderSnap Sodium Menu Compat 1.0.2

X-Factor 1.0.6 updates:

RenderSnap Sodium Menu Compat
1.0.0 → 1.0.2

RenderSnap's configuration is now properly integrated into the Sodium Video Settings menu.

Instead of maintaining a separate replacement for the normal Video Settings screen, X-Factor now uses Sodium's configuration API.

A new:

RenderSnap

section appears inside Sodium.

It contains two entries:

Performance

Visuals

Performance

Opens RenderSnap's existing optimization configuration screen.

Visuals

Opens RenderSnap's existing effects / visual configuration screen.

The flow is now:

Options
        ↓
Video Settings
        ↓
Sodium
        ↓
RenderSnap
        ↓
Performance / Visuals
        ↓
RenderSnap's existing settings screens

The compatibility mod does not duplicate RenderSnap's configuration system.

It simply exposes RenderSnap's existing screens through Sodium's supported addon configuration API.

---

Sodium Remains the Main Video Settings Screen

RenderSnap normally includes a Mixin that changes the vanilla Video Settings button so that it opens RenderSnap's own menu first.

That behavior is no longer required in X-Factor.

The supplied compatibility rules therefore include:

Rendersnap-1.3.1-mc26.2.jar: =ui.OptsBtn

This leaves Sodium as the primary Video Settings interface.

RenderSnap then becomes an integrated part of Sodium instead of replacing the menu containing it.

The intended distinction is:

Sodium = primary video settings interface

RenderSnap = additional performance and visual settings

This produces a cleaner configuration path and avoids competing Video Settings replacements.

---

RenderSnap Compatibility Rules

X-Factor 1.0.6 continues to use the X-Factor Compatibility Patcher for targeted Mixin compatibility changes.

The supplied RenderSnap rules are:

Rendersnap-1.3.1-mc26.2.jar: =world.ChunkGraph
Rendersnap-1.3.1-mc26.2.jar: =client.GraphicsPresetGuardMixin
Rendersnap-1.3.1-mc26.2.jar: =ui.OptsBtn
Rendersnap-1.3.1-mc26.2.jar: =world.ChunkWorkerLimitMixin

The two important 1.0.6 integration rules are:

=ui.OptsBtn
=world.ChunkWorkerLimitMixin

They serve different purposes.

ui.OptsBtn

prevents RenderSnap from taking over the Video Settings button.

world.ChunkWorkerLimitMixin

prevents RenderSnap from conflicting with Multicore Magic's chunk-builder executor.

The goal is not to broadly disable RenderSnap.

Only the specific pieces that overlap with X-Factor's selected configuration are removed.

---

Existing Modernica Compatibility Rules Retained

The existing Modernica compatibility rules remain part of the supplied X-Factor patch set.

These continue to target overlapping optimization paths including:

model_optimizations
blockstate_propertyaccess
perf.remove_biome_temperature_cache.BiomeMixin

X-Factor continues to prefer targeted compatibility changes over removing an entire optimization mod when only a small number of Mixins conflict.

---

Client State Guard 1.0.11 Retained

The Client State Guard work from X-Factor 1.0.5 remains in 1.0.6.

X-Factor continues to include:

Client State Guard 1.0.11

There are no major Client State Guard behavior changes in this release.

1.0.6 instead builds on the stability foundation introduced in 1.0.5 while focusing on the rendering and configuration side of the pack.

---

X-Factor Compatibility Patcher 1.1.0

X-Factor 1.0.6 retains:

X-Factor Compatibility Patcher 1.1.0

The patcher remains responsible for applying X-Factor's compatibility rules before conflicting Mixins can reach normal game initialization.

Its role in 1.0.6 is particularly important because the RenderSnap / Multicore Magic conflict happens while Minecraft's rendering classes are being transformed.

Without the compatibility rule, the conflicting Mixins can prevent the game from reaching the main menu.

With the supplied patch set:

Launcher starts
        ↓
Compatibility rules are applied
        ↓
Conflicting RenderSnap Mixins are disabled
        ↓
Fabric/Mixin initialization continues
        ↓
Multicore Magic initializes its chunk-builder path
        ↓
Minecraft starts normally

---

Compared With X-Factor 1.0.5

Added

Multicore Magic 1.0.2

Dedicated chunk mesh building executor

RenderSnap → Sodium menu integration

RenderSnap Performance button

RenderSnap Visuals button

Updated

RenderSnap Sodium Menu Compat
1.0.0 → 1.0.2

Version 1.0.2 also includes the corrected Minecraft 26.2 screen-opening implementation, shorter menu labels, and a proper mod icon.

Configuration Changes

New RenderSnap compatibility behavior includes:

Rendersnap-1.3.1-mc26.2.jar: =ui.OptsBtn

Rendersnap-1.3.1-mc26.2.jar: =world.ChunkWorkerLimitMixin

These respectively:

Keep Sodium as the main Video Settings screen

Prevent the RenderSnap / Multicore Magic executor conflict

Removed

No mods removed

Unchanged

The major 1.0.5 components remain in place, including:

Client State Guard 1.0.11
X-Factor Compatibility Patcher 1.1.0
RenderSnap 1.3.1
Modernica 26.07.1
Quantified API 2.2.0

The tested rendering combination remains:

Sodium 0.9.1+mc26.2
Iris 1.11.2+mc26.2

---

Existing Optimization Stack Retained

X-Factor 1.0.6 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
• Krypton
• Multicore Magic

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.6 Is Trying to Improve

X-Factor 1.0.5 focused heavily on stability and protecting client state during problematic transitions.

X-Factor 1.0.6 focuses on chunk rendering coordination and cleaner configuration integration.

The rendering path now looks roughly like:

Minecraft requests chunk mesh work
        ↓
Multicore Magic receives the work
        ↓
Dedicated chunk-builder pool handles it
        ↓
RenderSnap's competing executor redirect remains disabled
        ↓
Existing rendering optimization stack continues

The settings path now looks like:

Minecraft Options
        ↓
Sodium Video Settings
        ↓
RenderSnap category
        ↓
Performance / Visuals
        ↓
Existing RenderSnap screens

The focus of 1.0.6 is therefore not adding as many new optimization mods as possible.

The goals are:

• Reduce overlapping optimization systems
• Give chunk mesh building a dedicated execution path
• Avoid duplicate LevelRenderer redirects
• Keep Sodium as the central graphics configuration interface
• Make RenderSnap settings easier to access
• Preserve the existing optimization stack
• Retain the stability improvements from 1.0.5
• Keep compatibility changes targeted and reversible

---

Recommended Testing

For general performance comparisons between 1.0.5 and 1.0.6:

1. Use the same world or server.
2. Use the same render and simulation distances.
3. Keep resolution and shader state identical.
4. Disable VSync for maximum-throughput testing.
5. Use the same FPS cap.
6. Test rapid traversal through already-generated terrain.
7. Test rapid traversal through fresh terrain.
8. Repeat each workload more than once.

Because 1.0.6 changes the chunk mesh execution path, the most useful workloads involve rapid chunk loading and rebuilding.

Examples:

Join world
→ fly quickly through generated terrain
→ enter fresh terrain
→ turn rapidly while chunks load
→ return to previously loaded terrain

Watch for:

• Chunk loading consistency
• Frame-time spikes
• Visible chunk rebuild delays
• Stuttering during rapid movement
• Unexpected rendering failures

RenderSnap menu testing

Also test:

Options
→ Video Settings
→ RenderSnap
→ Performance

and:

Options
→ Video Settings
→ RenderSnap
→ Visuals

Confirm that:

• Sodium remains the normal Video Settings screen
• The RenderSnap category appears
• Performance opens the correct RenderSnap screen
• Visuals opens the correct RenderSnap screen
• Returning from RenderSnap returns to Sodium normally
• No crash occurs when either button is pressed

Compatibility testing

The game should also reach the main menu without errors involving:

world.ChunkWorkerLimitMixin

or:

multicoremagic$useChunkBuilderExecutor

A startup Mixin conflict involving both names usually indicates that the supplied compatibility patch has not been applied.

---

Updating From X-Factor 1.0.5

A clean launcher update is recommended.

If updating an existing instance:

1. Back up worlds, screenshots, and personal configuration changes.
2. Update the pack through the launcher.
3. Remove duplicate older mod versions if the launcher leaves them behind.
4. Make sure only RenderSnap Sodium Menu Compat 1.0.2 remains.
5. Remove an older 1.0.0 or 1.0.1 copy if one remains.
6. Keep the supplied X-Factor Compatibility Patcher 1.1.0.
7. Keep the supplied xfactor-compatibility-patches.txt.
8. Launch the pack.
9. Review the Compatibility Patcher wizard if it appears.
10. 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 and Mixin combinations that are tested together.

In particular, X-Factor 1.0.6 uses:

Sodium 0.9.1+mc26.2
Iris 1.11.2+mc26.2
RenderSnap 1.3.1
Multicore Magic 1.0.2

Changing one part of that combination independently may reintroduce compatibility problems that the supplied patch set is specifically designed around.

---

Compatibility

• Minecraft: 26.2
• Mod loader: Fabric
• Fabric Loader: 0.19.3
• Environment: Client-focused
• Java: 25
• 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 when available

For RenderSnap menu problems, include the exact sequence used before the issue.

For 1.0.6 startup problems, also mention whether the log contains messages similar to:

@Redirect conflict

or:

world.ChunkWorkerLimitMixin

These messages help distinguish a RenderSnap / Multicore Magic compatibility problem from an unrelated rendering crash.

For RenderSnap menu problems, check for errors mentioning:

RenderSnapSodiumConfig

and include the surrounding stack trace.

X-Factor 1.0.6 keeps the 1.0.5 stability foundation while extending the pack's optimization stack with a dedicated chunk-building path and a cleaner Sodium-centered graphics configuration experience.