Quick start
Solve your first research puzzle in minutes.Prepare the game
Install and activate the resource pack
Make sure the custom resource pack is installed and active in your Minecraft settings.
Set up the research table
- Open a Research Table in-game
- Place an unsolved Research Notes item in the table
- Make sure only the initially given aspects are on the board
The puzzle board should be clean - no aspects placed except the starting ones provided by the research notes.
Run the bot
Open a terminal
Navigate to the project folder and open a terminal:
You can use Windows Terminal, PowerShell, or Command Prompt.
Start the bot
Run the main command:The bot will automatically:
- Bring the game window to the foreground
- Take a screenshot
- Parse the puzzle board
- Generate an optimal solution
- Place aspects using mouse control
Emergency stop
Process next board
After the bot finishes placing aspects:Using test mode
Test the bot without performing any mouse actions:- Reads from
debug_input.pnginstead of taking a screenshot - Parses and solves the puzzle
- Skips all mouse clicks and window actions
- Saves the solution render to
debug_render.png
Test mode is useful for verifying puzzle recognition and solver performance without affecting your game.
Configuration
Create aconfig.toml file in the project root to customize behavior:
The config file is automatically created with defaults on first run if it doesn’t exist.
Understanding aspect costs
The solver minimizes total aspect cost when generating solutions:- Primal aspects (aer, aqua, terra, ignis, ordo, perditio) cost 1 by default
- Compound aspects cost the sum of their components
victus= aqua + terra = 2herba= terra + victus = 3instrumentum= humanus + ordo = higher cost
config.toml to reflect your actual inventory:
Advanced: Test all mode
Benchmark the solver on multiple puzzles:test_inputs/ folder and reports:
- Parse time
- Solve time
- Solution cost
Troubleshooting
Bot can't find the game window
Bot can't find the game window
Update the
game-window-title in config.toml to match your actual window title.Puzzle recognition fails
Puzzle recognition fails
- Verify the custom resource pack is active
- Ensure the game window is fully visible on the main screen
- Check that no tooltips are covering the puzzle board
- Make sure the window is large enough
Solver takes too long
Solver takes too long
Large boards with 7+ starting aspects can take longer. Consider:
- Using test mode to pre-validate the puzzle
- Waiting patiently (it will complete)
- Checking if there are any disabled aspects that could simplify the solution
Mouse control is too fast/slow
Mouse control is too fast/slow
Currently there’s no built-in speed control. The default speed is tested to work consistently on most systems.
Next steps
You’re ready to automate all your Thaumcraft research! The bot will:- Save screenshots of each puzzle to
test_inputs/for debugging - Generate debug renders showing the solution path
- Remember you can press
rto retry or Enter to continue
Report issues
Found a bug? Include the generated
debug_input.png when reporting issues on GitHub.