-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
- The definition must be under
data/<namespace>/blueprints/. - A matching outline must be under
data/<namespace>/blueprint_outlines/. - The definition and outline IDs must match exactly.
- All item and preview-entity IDs must exist.
- Water deployment must specify
preview_entity. -
index.jsonis ignored.
Check the server log for Skipping blueprint, Skipping outline or Failed to load, then run /reload.
Regenerate the texture and base64 mask from the same source drawing. Verify that the outline JSON points to the generated texture and that cells matches the number of set mask bits.
The pen travelled too far away from the guide. Insert another sheet and trace more closely. The ink remains in the table until a completed blueprint consumes it or it is removed before drawing.
- Put the blueprint in the off hand.
- Put the Axiomata construction hammer in the main hand.
- Verify that the blueprint's definition still exists after the last data-pack reload.
- Look at a block or water surface within interaction range.
- Clear the preview bounds of blocks, entities and other unfinished machines.
- For ground placement, use a sturdy target with enough support under the result footprint.
- For water placement, use a large enough continuous water surface.
- Right-click the unfinished entity; attacking does not build it.
- Do not sneak unless dismantling is intended.
- Aim at the highlighted current section.
- Carry the complete material kit requested for that stage.
- Wait for
hitCooldownTicksbetween accepted hits.
Drawing quality changes field-construction material totals. Also verify that all construction stage allocations add up to each key count. Allocation mismatches are warnings rather than load failures.
axiomata-server.toml is stored per world. Edit the copy under the active world's serverconfig directory and restart the server.