Commands and Configuration - mess1re/axiomata GitHub Wiki

Give a blueprint

Permission level 2 is required.

/axiomata blueprint give <blueprint>
/axiomata blueprint give <blueprint> <quality>
/axiomata blueprint give <blueprint> <quality> <targets>

quality is clean, plain, hasty or sloppy. Omitting it gives a plain blueprint. Blueprint IDs and quality values have command suggestions.

Examples:

/axiomata blueprint give example:machine
/axiomata blueprint give example:machine clean @p

Server config

The per-world file is:

world/serverconfig/axiomata-server.toml

Section: [construction]

Key Default Range Meaning
hitsPerItem 1.0 0.05–20 Derived base hits per allocated item
minStageHits 3 1–1000 Minimum hits for any stage
maxStageHits 100 1–1000 Maximum hits for any stage
hitCooldownTicks 8 0–1200 Delay between accepted hits from one builder

Minecraft runs at 20 ticks per second. Restart the world or server after editing the file.

Config updates

Both server and client configs include configVersion = 1. It is the config layout version, not the mod version; leave it unchanged. Existing unversioned configs receive the field and any missing settings without resetting valid construction values. Updating does not require deleting the files. Changed defaults do not overwrite existing values.

The mod's built-in blueprint data comes from the new jar. Custom datapacks are not rewritten when Axiomata updates.

Client config and update notices

File: config/axiomata-client.toml

Under [updates], showNotice defaults to true. When a newer version is available, the client shows one clickable download link in chat per game launch. It does not download or install a jar.

Set showNotice = false to hide the message. The loader's global version-check setting controls the network check and standard Mods-screen indicator; this setting only controls the chat message.

⚠️ **GitHub.com Fallback** ⚠️