Tensura: Xaero Maps

Tensura × Xaero Integration

See the magicule in the air where you have already been. This addon tints mapped chunks on Xaero's Minimap and Xaero's World Map according to how magicule-rich the ambient air is in that chunk, and tells you the exact number when you point at a chunk on the world map.

Install it on the client, and on the server if you play multiplayer. With Tensura and at least one Xaero map present, the overlay appears on explored chunks, with no commands, items or world setup. Each map works on its own, so the minimap alone or the world map alone is enough.

What it does

• A translucent overlay on both maps. Chunks whose ambient concentration is above the normal baseline are tinted, and the tint grows stronger the further above baseline they are. Normal chunks are left untouched.
• Live values. Tensura's concentration moves as magicule regenerates and as blocks and entities use or emit it. The tint and the number follow, without you having to reopen the map.
• Point at a chunk on the world map and the tooltip shows its concentration and how that compares to normal, for example Magicule Concentration: 1450 — Moderately Elevated.
• Chunks you have not mapped are never shown, sent or stored.
• Optionally, a sensing skill. A server can require players to hold a skill such as Magic Sense before they are sent any concentration. Without it your maps stay uncoloured: the server sends you nothing, and your own overlay and hover hide until you qualify.
• Nothing is simulated. The values are Tensura's own. This addon only reads and draws them; it never recalculates, guesses or changes concentration.

What your map remembers

Tensura only holds a concentration value for chunks the server currently has loaded. This addon remembers the last value it saw for every chunk you have mapped. When a chunk unloads or you travel away, its overlay stays but fades, and hovering says (last known) instead of passing an old number off as a current one. Walk back and it brightens again as soon as the server can answer for it.

That history is stored in your own game folder, one file per world, and it only ever contains chunks your maps had already explored. You can delete it; the maps go blank outside the loaded area again.

Configuration

Two config files, both optional to touch:

• Client: which overlays and hover are on, colours and opacity (which can override the pack's), how bright last-known values are, how much history to remember, and how far around you data is requested.
• Server: a master switch for sending concentration at all, an optional skill gate (Magic Sense by default), per-player caps, the distance limit, and how much work reconciliation may spend per cycle.

Per-dimension tiers

Dimensions do not share a magicule scale. The nether and the end are hotter than overworld air, and the hell dimension is orders of magnitude hotter still. So "elevated" is judged per dimension: a chunk is compared with what normal looks like where you are, not with one global number. The server decides the tier and sends it with the value, so every player on a server sees the same thing.

Those tiers ship as datapack entries and are the intended knob for pack authors: data/<pack>/magicule_tiers/*.json sets a dimension's normal and, if needed, its own band boundaries, given as percentage increases over that normal. See docs/CONFIGURATION.md.

Defaults are chosen to look good and stay cheap. Every key, default and effect is documented in docs/CONFIGURATION.md.

Dependencies

Known limitations

• Only the area the server still has loaded has live values; everything else shows what was last observed there (see above).
• The bands (Slightly / Moderately / Highly / Exceptionally Elevated) are display bands relative to Tensura's baseline. Tensura itself has no named tiers, so these are a reading aid, not a game rule.
• The integration is pinned to the Xaero and Tensura versions listed above. Later versions may move the map hooks it needs; see docs/COMPATIBILITY.md.
• Multiplayer values are server-authoritative, and a server can switch the whole feature off.

Building from source

Java 21 and the committed Gradle wrapper are all that is needed; every dependency resolves from CurseMaven, including Tensura's own library closure.

./gradlew build                # compiles, runs the JUnit suite, produces the jar
./gradlew runGameTestServer    # headless GameTests against the real Tensura jar

Deeper detail: docs/ARCHITECTURE.md, docs/CONFIGURATION.md, docs/COMPATIBILITY.md, docs/TESTING.md, docs/RECONNAISSANCE.md and CHANGELOG.md.

Credits

• Tensura: Reincarnated by ManasMods — every concentration value shown here comes from its API.
• Xaero's Minimap and Xaero's World Map by Xaero96 — the maps this addon draws on.
• NeoForge — the mod loader.

License

GNU Lesser General Public License v2.1 — see LICENSE. Copyright (c) 2026 Bitwise Madness.

No third-party mod binary is bundled, redistributed or committed by this project.

AI disclosure

Parts of this project were written with the assistance of AI coding tools. AI-assisted code, data and documentation ship only after human review by the maintainers.

In-game config editing

Mods built with this template can be edited in-game with Configured - install it like any other mod; it adds no code to this one. Open the mod list, select a mod, press Config, and change values directly: Configured writes through NeoForge's config system, so a reload applies the new values without restarting the game.

This template pre-wires the config-screen background in src/main/templates/META-INF/neoforge.mods.toml ([modproperties.${mod_id}] configuredBackground) - point it at any texture you like. Note Configured only shows a menu for mods that actually register a config: a template-derived mod with no registered settings has nothing to show.