Full System Audit

This is a currency earn-rate bonus tied to rank. It directly accelerates economic progression. EULA is ambiguous here — Mojang's guidance says gameplay advantages are prohibited, but small economy bonuses on a non-PvP-affecting currency are generally accepted by the community and have not been acted on. Risk level: low-medium. The bonuses are small (max 10%) and Silver is not used in PvP contexts. Recommend retaining but monitoring Mojang guidance updates.

Flight within a claimed zone is a significant convenience perk and potentially an economic advantage (faster build speed, easier resource placement). It is restricted to Guild claims in the Nexus only — not in open world, Shard, or combat zones. This is the critical constraint that keeps it EULA-compliant. If /fly is ever extended outside the Nexus, it must be re-evaluated. Confirm implementation enforces the Nexus-only restriction before launch.

Cosmetic recognition perk. EULA compliant in principle. Codex Wall built — public page (codex_wall.html) live with staff-managed admin panel, Founders' Record section at top, Fractureborn wall below. Linked in public nav.

$12 for a single-use item is high for a casual player. This is deliberate — Keep Inventory should feel like a significant purchase, not something players spam. Review during economy balancing to ensure the price is not so high it never sells, but not so low it trivialises death in non-PvP zones.

$21 is a meaningful ask for a social feature, especially for players who have no intention of buying a rank. Consider whether this price is a barrier to Guild formation or an appropriate gate. If Guild density is important for the server's social health, a lower price ($15 = 50G) may be worth considering. Note: T4/T5 get it free, so this only affects lower-rank players.

Rules rule 5.1 states 70 Gold. Economy doc states 70 Gold. Consistent currently. If the price changes during balancing, both documents must be updated simultaneously. Add to the pre-launch consistency checklist.

Rules state PvP is enabled in designated conflict zones in the Infernal Realm, but no document defines which zones those are or how they are marked. This must be specified before the Infernal Realm opens to prevent disputes. Consider adding to the world design doc when it is built.

Rule 5.3 references a weekly Silver upkeep fee but does not state the amount. Economy doc mentions Guild upkeep as an anti-inflation sink but does not set a price. Set the upkeep fee before launch and add it to both documents.

Previously cross-referenced and cleared. No major IP conflicts found. Flagged here as a reminder: this was the rename from Malachar (which conflicted with existing properties). Zaveth is clear. Do not revert to Malachar.

"Veilsworn" appears in minor usage in tabletop RPG homebrew communities but has no major IP attachment. Low conflict risk. Recommend a final search before public launch to confirm no major release has used it in the interim.

Requires a cosmetics plugin (Cosmetix, GadgetsMenu, or similar) or custom implementation. Not natively in EssentialsX. Choose and configure a cosmetics plugin before launch. Custom cosmetic items (per-rank exclusive items) require custom resource pack or MythicMobs item definitions.

Animated chat name requires either a custom plugin or a plugin like TAB (scoreboard/tab plugin) that supports animated placeholders. Confirm your chat/tab plugin supports this before advertising it as a perk.

Custom per-player join messages require a plugin that hooks into login events and supports per-player message configuration. EssentialsX supports custom join messages but typically per-group, not per-player custom text. Clarify whether this is a fixed rank-themed message or player-customisable text. Player-customisable text is harder to implement.

WorldGuard region flag for flight, combined with a permission plugin that grants /fly only within a specific region type. Achievable with WorldGuard + CMI fly flag per region, but requires careful configuration. Test thoroughly before launch — a misconfigured /fly permission is a significant exploit risk.

Max health attribute modification via MythicMobs is achievable. Per-player variable tracking for 3 stacks with individual 30s timeouts requires a custom skill that reads and writes player variables. Non-trivial but within MythicMobs scripting capability. Build and test early — this mechanic appears in both dungeons.

Dash mechanic achievable. Spawning bleed zones at intervals along the charge path requires tick-based position sampling during the dash. Achievable with a custom movement skill but needs careful implementation to avoid zone placement lag. Test at scale — lag in zone placement during a fast charge will make the mechanic feel broken.

MythicMobs global variables can track dungeon-wide state. Incrementing on a timer is trivial. Incrementing on player death requires a Bukkit PlayerDeathEvent listener that checks if the death occurred in the dungeon instance and updates the variable. Custom plugin work — but this is the core mechanic of Dungeon 2 and must be built robustly.

WorldGuard exit region lock triggered by a custom item pickup event. Requires a Bukkit PlayerInteractEvent or InventoryClickEvent listener to detect the specific item being picked up and trigger the lock. Achievable but needs clean implementation — false triggers on item pickup would be a bad player experience.

AoE drain is achievable. Proportionally healing nearby mobs by the amount drained requires reading the damage dealt in the same tick and distributing it as healing — custom skill logic. Simplified version (drain players, separately tick-heal nearby mobs at a fixed rate) is significantly easier and achieves the same gameplay feel. Recommend the simplified approach.

Most standard economy plugins support only one currency. A second currency requires either a plugin with multi-currency support (GemsEconomy, PlayerPoints) or a custom implementation. Choose and commit to a Gold currency plugin early — this is a foundational infrastructure decision that affects the Gold shop, rank grants, and trading.

A safe /trade GUI (shows both players' offers before confirmation) requires a dedicated trading plugin. Not natively available. Several good options exist (TradeSystem, PlayerTrade) — choose one and configure it before launch.

Chest shops (sign-based or GUI-based) are well-supported (ChestShop, QuickShop Hikari). The implementation needs to enforce that shops only work within Guild Nexus claims — a WorldGuard flag check on shop creation. This is achievable but needs explicit configuration.

Quest chains with unlock conditions (complete M5 to unlock Chain A, complete A1-A4 to unlock M7) are supported by BetonQuest conditions and Quests plugin prerequisites. BetonQuest is strongly recommended over standard Quests plugin for this level of conditional complexity — its scripting model handles multi-chain dependencies cleanly.

Tracking aggregate quest completion across all players and triggering a server-wide event requires a custom plugin that maintains a global counter. BetonQuest alone does not handle server-wide aggregate conditions. This is the most complex quest mechanic in Chapter 1 and requires dedicated custom development.

Per-player time-gating between quest stages requires storing a timestamp per player per quest and checking it on next interaction. BetonQuest supports time conditions. Achievable but needs explicit implementation — do not rely on the default quest cooldown system which typically works differently.

Triggering a secondary lightning effect on a nearby entity on melee hit requires a custom Bukkit EntityDamageByEntityEvent listener. The secondary target selection (nearest within 4 blocks) and damage application are straightforward once the listener exists. Achievable, non-trivial.

Requires the Seam Pulse event system to expose a server-wide event flag that Storm Call can listen for. If Seam Pulse fires a custom Bukkit event, Storm Call becomes a standard "on event, if player is attacking, summon lightning." Dependency: Seam Pulse system must be built first.

Detecting any Void-type enchant on any equipped item slot requires an InventoryClickEvent and PlayerArmorChangeEvent listener checking all slots on every equip/unequip. Silently toggling all Severance enchant effects on/off requires the enchant plugin to support conditional enchant activation — most custom enchant plugins support this via conditions, but the player-wide check needs custom integration. Achievable but requires careful plugin architecture.

Permanently lowering an item's maximum durability (not current durability) on repair events requires storing per-item metadata tracking the degradation state. Standard item NBT tag storage achievable with PersistentDataContainer. The UI challenge: Minecraft does not natively display "max durability" separately — players will need to infer it from the bar. Consider a lore line on the item showing current durability floor.

Bypassing a percentage of armour requires intercepting EntityDamageEvent, reading the attacker's armour value, and applying a modified damage calculation that ignores the armour reduction for the Fracture Edge percentage. Requires a custom damage listener. Standard pattern for custom enchant plugins that support damage formula hooks.

Minecraft's native item rarity system only supports 4 tiers (COMMON, UNCOMMON, RARE, EPIC). Custom rarities require item lore lines with colour codes and NBT tags. EcoItems or ItemsAdder handle this cleanly. Without a custom item plugin, every item must be manually constructed. Recommend choosing an item management plugin early — this affects all 63+ custom items.

The glow/shimmer effect for Mythic and Artefact tiers requires a resource pack override or a client-side rendering plugin. Not achievable with lore lines alone. Low priority for Chapter 1 (neither tier appears in Ch.1 drop tables) — revisit before Chapter 2.

Quest items must be bound to the player's session and removed automatically when the quest resolves. BetonQuest supports take-item reward/condition cleanly. The non-tradeable flag requires a custom PlayerDropItemEvent and InventoryClickEvent listener to intercept attempts to move quest items out of inventory. Standard pattern.

Decided — canonical void buff list: (1) Active Void enchant effects: Wither, Poison, Darkness, Void Draw pull, life drain tick. (2) Void-Touched status, regardless of source. Not included: Void scroll debuffs, mob corruption passives/resistances. These are anti-void-enchant tools only — not general debuff cleansers. Implementation: track as a named PotionEffect or MythicMobs aura tag; Null-Strike iterates the list and removes the first matching entry.

Decided: Saturation Burst is a self-contained AoE ability on the item. It has no dependency on the dungeon mechanic — the two are fully decoupled. The dungeon convergence point mechanic is built independently by the dungeon plugin. No cross-plugin interface required.

"Void ability cooldown" is not a native Minecraft concept — it refers to MythicMobs skill cooldowns triggered by void enchants. Reducing those cooldowns by 8% requires the enchant cooldown system to support a multiplier applied from item NBT. Design the enchant CD system with this extension point in mind from the start.

Requires intercepting PlayerItemDamageEvent at 0 durability, cancelling the vanilla item break, setting an NBT tag (e.g. smc:broken=true), and triggering a tooltip/display update. The item must then be blocked from use (PlayerInteractEvent, EntityDamageByEntityEvent) while broken. Achievable with a custom listener — the tooltip cracked-icon display requires a resource pack override for the item texture. This is a core gameplay system and should be built and tested early.

A Citizens NPC with a custom GUI (ChestGUI or similar) that reads the held item's rarity NBT tag, calculates Silver cost based on durability deficit, and charges the player. The rarity-to-cost lookup table must be defined and stored — recommend a config file rather than hardcoded values so costs can be tuned post-launch without a plugin rebuild.

Intercepting PlayerDeathEvent, checking equipped/inventory items for Soul Bound NBT, adding those items to a "keep" list, then removing the Soul Bound enchant from the item before returning it to the player's inventory on respawn. Requires a custom death event listener — the "remove enchant on use" part needs PersistentDataContainer manipulation. Achievable but needs careful ordering with other death event listeners (e.g. Erasure). Test thoroughly — death event ordering can produce edge cases.

Focused: custom projectile entity, hits nearest mob in path. Splash: radius entity check on impact, positive effects to allies only, negative to enemies. Lingering: persistent entity with 3s tick. Recommend a generic delivery system — each scroll registers effect logic + delivery type separately to avoid duplication across 41 scrolls.

Custom crop blocks via ItemsAdder. BlockGrowEvent listener validates Farmer proficiency before allowing growth. Voidbloom's "any zone" ability at Farmer 100 requires overriding soil-type check for that player specifically — store a flag in player data on reaching Farmer 100, check it on BlockGrowEvent.

No off-the-shelf plugin handles: proficiency + point trees + faction gating + 2-slot active system + Severance deactivation + death event coordination. Build as part of the custom economy plugin's player data layer. Shared data layer avoids two plugins reading the same player state.

Decided: Slots 8 and 9 are dedicated skill slots. Right-click to activate. Skill plugin places a custom ItemsAdder item in each slot representing the equipped skill — name, lore, and cooldown state driven through item metadata. Cooldown feedback via item name update (e.g. "Verdict — 12s"). Bedrock compatible. No packet interception required.

Nine XP pools stored per player in the database. Each action type maps to one pool (BlockBreakEvent type-check for Excavator/Miner/Forester, CraftItemEvent for Artificer, PlayerFishEvent for Pathfinder, harvest event for Farmer, trade events for Merchant, weapon craft for Weaponsmith/Armorsmith). Breadth is the complexity — each listener is simple, but 9 of them need careful event filtering to avoid cross-crediting.

GemsEconomy or PlayerPoints recommended. Foundational — affects Gold shop, rank grants, and trading implementation.

BetonQuest supports the conditional complexity of Chapter 1's chain structure. Standard Quests plugin will struggle with multi-chain prerequisites and the M9 server-wide trigger.

Required for trail particles, cosmetic hat/armour, and animated rank name. Evaluate Cosmetix, GadgetsMenu, or custom implementation.

Decided: Custom trade plugin. Full dual-currency support (Ancient Silver + Ancient Gold in the same transaction window) is the priority — no existing plugin handles this without significant rework. Routes all transactions through the economy plugin API to keep the audit log clean. Built alongside the economy plugin once the economy API is finalised.