Mortals & Gods - Build Your Own Pantheon 1.1.0 Minecraft 1.21.1 | NeoForge

This release answers three field reports: a1remag1c and druidicmage, who both found the altar impossible to arm, and Priesttech, who sent a detailed list of bugs and suggestions after building a pantheon on top of the mod. Thank you all.

===================================================================== THE ALTAR: A BLOCK OF OUR OWN

NEW BLOCK: the Altar Lectern. Craft it from a Lectern + Book + Gold Ingot (shapeless). Right-click it to worship.

Why this exists: the altar used to arm on a vanilla enchanting table, matched by exact block identity. Any mod that replaced that block (Easy Magic and many others) silently disabled this entire mod, with no message and nothing in the log. a1remag1c spent a week diagnosing that. The mod now owns its altar block, so no other mod can take it away.

• Enchanting tables STILL WORK by default, so altars you have already built keep standing. Set acceptEnchantingTable = false in the config to require the Lectern instead.
• What arms an altar is now the block tag #mortalsgods:altar_blocks. Datapacks can add anything they like to it.
• Which blocks adorn a temple, and what each is worth, is now the templeBlockValues config list. Add modded storage blocks freely, for example "create:zinc_block=3".
• The Sanctum size limit is now configurable (sanctumMaxVolume, default 5000) instead of a hidden constant, so cathedrals are possible.

NEW COMMAND: /mortalsgods altar check, open to every player, no op needed. Stand at your altar and run it. Four separate conditions used to collapse into one message ("No active Altar is near."), so nobody could tell which had failed. It now walks all four in order and names the one that broke, including where the room leaks if it is not sealed, and the temple value and tier if it is fine. Right-clicking an unarmed Altar Lectern runs the same check automatically.

===================================================================== FIXED

• BOONS NO LONGER OUTLIVE THEIR GATE. If a player stopped passing a "require" gate (you removed the tag, their score dropped), the god vanished from their worship screen and they could not re-pledge, but its boons went on applying every second, forever, with no way for anyone to remove them. Gated gods are now SUSPENDED: attribute bonuses, potion effects, scoreboard writes, auto-revive charges, crafting durability and favor theft all stop, and the player is told once in chat. Their pledge and devotion are kept, so restoring the tag restores the god at full standing. (Reported by Priesttech.)

• RENOUNCE REACHES FURTHER. /mortalsgods renounce only ever touched tabs marked "exclusive", so on a pantheon without one it was a permanent no-op and there was no way to stop worshipping at all. Added: /mortalsgods renounce all turn from every god, everywhere /mortalsgods renounce tab <id> turn from one named tab Both are open to any player. Operators can run them on someone else, which is the tidy way to pair a gate with its cleanup. The bare command is unchanged. (Reported by Priesttech.)

• LONG LORE IS NO LONGER CUT OFF. A god's description was hard-capped at eight lines and ended in an ellipsis, and a god with many boons overflowed the panel entirely. The whole info panel now scrolls with the mouse wheel and nothing is truncated. (Reported by Priesttech.)

• THE CAMERA KEY RESPECTS YOUR KEYBINDS. The worship screen hard-coded F5 and swallowed it, so rebinding the perspective key did nothing there. It now matches your actual binding. (Reported by Priesttech.)

• TIME IS HONEST NOW. worshipCooldownDays, favorGraceDays and favorDecayPerDay were never world days: they were multiplied by 24000 ticks of server uptime. They are renamed worshipCooldownTicks, favorGraceTicks, favorDecayPerPeriod and favorDecayPeriodTicks, and the config now explains exactly what they measure. The old keys still work for one release and log what to rename. (Reported by Priesttech.)

• OFFERINGS SEE YOUR OFF HAND. Holding the offering in your off hand reported that you could not afford it. Worn armour is still never taken.

• RENOUNCING NO LONGER RESETS YOUR KILLS. Devotion and the cooldown are cleared, but who you have already killed is not, so renouncing and re-pledging cannot make old victims worth credit twice.

• THE JAR REPORTS ITS REAL VERSION. Every build since 1.0.0 announced itself in-game as "1.0.0" because the version was hard-coded in a second place.

===================================================================== PANTHEON SCHEMA (all optional, all backwards compatible)

• ITEM TAGS: "item": "#c:ingots/gold" accepts a whole family of items instead of one exact id.

• MOB HUNTS: a kill currency can name creatures instead of players: { "type": "kill", "entity": "#minecraft:undead" } { "type": "kill", "entity": "minecraft:zombie" }

• REAL PLAYER TARGETS: the "target" field on a kill currency was parsed, stored, and read by nothing but the UI caption; the behaviour was always "the victim follows the opposing god". It now means something: rival_followers (default) non_believers any_player tab:<id> group:<id> god:<id> Any other string keeps its old behaviour and logs a note, so nothing you have already written changes meaning.

• MULTIPLE CURRENCIES: "currency" may be an array, with "currencyMode": "all" (pay everything) or "any" (pay whichever you can afford).

• FAVOR MULTIPLIER: any currency may carry "favorMultiplier" to scale the devotion it grants. 1.0 unchanged, 1.3 is +30%, 0.5 is half.

• PER-GOD CADENCE: a god may override the global timing with "cooldownTicks", "graceTicks" and "decayPerPeriod". A jealous war god can demand attention every few minutes while a patient harvest god forgives a week.

• BOON TYPES TIDIED: max_health, reach and mana were three names for one code path. They are now aliases of the general "attribute" boon and still work exactly as before, with nothing to rewrite.

• REMOVED: the pehkui_scale boon type. It parsed, printed text in the worship screen, and never had any effect whatsoever. A god carrying one is reported in the log and skipped, so delete it. The Emperor's scaling is, and always was, driven by the emperor*ScaleCap values in the config.