v2.4.0

Changes

• Name infused gems after their rolled stat by @XxFran10xX in #45
  • A better name never means a weaker gem: rarity is still drawn as before (65/25/7/3), and d20 + Intelligence still picks the stat in the same range. The gem is then named after how that stat ranks among every result it could have rolled. Before, a Flawless Epic Agate (0.60) could beat a fumbled Legendary one (0.40).
  • Same name rates: each name goes to its rarity's share of results (Legendary to the best 3%, and so on), worked out at the new d20.infusion.name-reference-modifier (default 0, Intelligence 10–11). Players with more Intelligence get better names more often, because their gems really are better.
  • Ties go down: results that tie on one stat share a name, and a tie that would take a rarer name past its chance gets the lower name. Rarer names can fall slightly short of their chance (at most 3.1 points for the bundled gems) but never go over it.
  • The name, the Rarity: lore line, the stored rarity, the Legendary broadcast and the goldsmithing gem stat boost chance all follow the name, not the drawn rarity.
  • Each gem's cutoffs are logged when the config loads, e.g. Gem 'agate' names: legendary from 0.5558, epic from 0.4526, rare from 0.3347, common below.
  • Existing gems keep their names. Configs without the new key use the default, so no config change is needed.

Full Changelog: v2.3.3...v2.4.0

Downloads

• geminfusion-2.4.0.jar
• SHA256SUMS — SHA-256 checksums.
• build.json — Build metadata.