ThreadTweak Guide: Settings, Thread Counts, and Safe Priority Changes

guide

ThreadTweak is a utility mod that lets you adjust how Minecraft distributes its worker threads and how much priority the game gives to different kinds of tasks. Everything it offers is controlled through its settings interface and hotkeys rather than through crafting or in-game items, so getting started means finding that interface and learning which values are safe to touch.

Where the Settings Live

ThreadTweak does not add blocks, items, or recipes. Its options are exposed through its own interface, which you open with the corresponding hotkey (set it in the controls menu). Once open, you will see a list of numeric and priority settings you can change directly. Because these values affect how the game schedules work, it is worth reading each one before you move a slider or type a number.

Thread Count Settings

Two settings control how many worker threads are available.

Bootstrap Worker Thread Count — This controls the threads used during the early startup phase. The interface warns that raising this value is known to decrease performance, so the safe approach is to leave it where it is unless you have a specific reason to change it.
Main Worker Thread Count — This controls the threads used for the bulk of the game's background work. The interface notes that this value greatly affects load times, and that it may also affect in-game performance. Because both loading and gameplay can shift when you change it, adjust it in small steps and test the result rather than making a large jump.

A practical way to work with these two is to change one at a time. If you raise the main worker count and loading gets faster but gameplay feels worse, you have learned something useful and can step back. If you lower it and nothing improves, return it to its previous value. The bootstrap count is the one to treat most conservatively, since the interface explicitly flags increases as harmful.

Priority Settings

Priority settings determine how much attention the operating system gives to each category of thread. ThreadTweak exposes five of them.

Game Thread Priority — the priority of the main game thread.
Bootstrap Worker Priority — the priority of the threads handling startup work.
Main Worker Priority — the priority of the threads handling the main background workload.
IO Worker Priority — the priority of the threads handling input and output work.
Integrated Server Thread Priority — the priority of the integrated server thread, which matters when you are running a single-player world with the internal server active.

Higher priority means a thread is scheduled more readily; lower priority means it yields to others. Raising everything at once defeats the purpose, because the threads then compete with each other in the same way they did before. A safer pattern is to decide which area is struggling and adjust only that one priority, then observe whether the situation improves.

Configuring Safely

Treat every value here as something to change deliberately and reversibly.

Change one setting per session so you can tell what caused any difference.
Keep notes on the original values so you can restore them.
Move priorities gradually instead of jumping to an extreme.
Be cautious with Bootstrap Worker Thread Count, since the interface states that increasing it reduces performance.
Remember that Main Worker Thread Count influences both load times and, potentially, in-game performance, so a change that helps one may not help the other.

If a change makes things worse, put the value back. ThreadTweak gives you direct control over thread counts and priorities, and the most reliable results come from small, tested adjustments rather than aggressive ones.