🧪 DivinityEconomy 4.0.0-arclight (26.2) – Experimental 🧪

This is an experimental build for hybrid servers (Arclight and similar). It is the 4.0.0 release plus modded item support, published as a separate jar so it can be tested without affecting the main release. It is not a replacement for DivinityEconomy-4.0.0.jar until it has been proven on a real hybrid server.

📦 Build Details

• Jar: DivinityEconomy-4.0.0-arclight.jar
• Plugin version (plugin.yml / Maven): 4.0.0-arclight. This is the version shown by /plugins, in the startup banner, via PlaceholderAPI and on bStats.
• Plugin name: still DivinityEconomy, so the data folder, permissions, placeholders and depend entries of other plugins are unchanged. Do not run this jar alongside the normal one; they are the same plugin.
• Config version (Main.Version in config.yml): still 4.0.0. This is the config schema version used by the migration system, which only understands numeric versions, so it must not carry the label.
• Based on: 4.0.0 (Minecraft 26.2, Java 25 required).
• Source: branch experiment/arclight-modded, built on YouniorPL's "Arclight Patch" (#79).

⚠️ Upgrade Notes ⚠️

• Back up your plugin folder first. The plugin will add entries to materials.yml and materialAliases.yml and a Commands.Admin.Modded setting to config.yml.
• You can go back to the normal jar. Imported modded entries are left in materials.yml and are harmless on a server that doesn't have those materials (they are skipped).
• On servers that do not expose modded materials to Bukkit (plain Paper/Spigot) this build behaves like 4.0.0; the scan finds nothing.

➕ What's New ➕

• Modded Item Import

  About 10 seconds after startup (hybrid servers register mod items late), and whenever an admin runs /modded, the plugin scans for materials outside the minecraft namespace and adds new ones to materials.yml.

  • New items are imported banned (ALLOWED: false) with QUANTITY: 0. Nothing is tradable until you set it up, e.g. /banitem <item> false plus /setstock and /setvalue.
  • A short alias is created automatically (cobblemon:mago_berry becomes mago_berry). Aliases never replace an existing alias or item.
  • Entries already in materials.yml whose mod wasn't loaded yet are skipped, then picked up by the next scan with their settings intact.
  • Unresolved materials are never in the market, so they can't be bought or sold.
  • Only blocks/items are supported. Modded potions, entities and enchants are not.

• /modded Command

  Rescans for modded items on demand. Setting: Commands.Admin.Modded. Permission: de.admin.modded (operators by default, included in de.admin).

• Localisation

  All modded-item messages are available in all 20 languages. The translations are machine-generated and should be reviewed by native speakers.

🛠️ Changes From The Original Patch 🛠️

• Strict item validation: no stone placeholder for unresolved modded items.
• Only the block/item manager imports modded items; the potion and entity managers no longer run the scan.
• Dotted IDs such as mod:item.v2 are stored as mod:item_v2 (the real ID is kept in MATERIAL_ID) so Bukkit doesn't split them into nested sections. Colliding keys are skipped and logged.
• Imported items and aliases are preserved across reloads and restarts. ConfigUpdater removes any key that isn't in the bundled files on every load, which would otherwise wipe them.
• Alias saving is serialised and goes through the Bukkit scheduler instead of a raw thread.
• The ConfigUpdater dependency is kept, and the original patch's version bump and committed IDE files are dropped.

🧪 Testing Status 🧪

• Automated: the full suite (178 tests) passes. A simulated hybrid server (a fake modded-material provider) covers import, aliases, dotted IDs, collisions, late-loading mods, /banitem, potion/entity isolation and reload survival.
• Not yet verified on a real Arclight server. The simulation checks this plugin's logic, not how Arclight populates Bukkit's material registry.

Please test

1. Start with a few mods installed. About 10 seconds after startup, check the console for "Importing modded material" lines.
2. Confirm materials.yml and materialAliases.yml contain the new entries (banned, quantity 0).
3. Enable one with /banitem <alias> false, set stock and price, then buy and sell it.
4. Restart and confirm the entries, settings and aliases are still there.
5. Add another mod, run /modded, and confirm only the new items are imported.

⚠️ Known Limitations ⚠️

• Imported items have no stock or price until an admin sets them (the Static pricing model also needs PRICE). They use the default ELASTICITY of 0.7.
• The server software must expose modded items through Bukkit's Material.

See Documents/modded-items.md for the developer guide and the README's "Modded Items" section for the admin guide.