```yml
crafting:
shaped:
'1':
- m MATERIAL WEAPON_POWDER 1|m MATERIAL WEAPON_POWDER 1|m MATERIAL WEAPON_POWDER 1
- m MATERIAL WEAPON_POWDER 1|m SWORD PLATINUM_SWORD{level=2..5} 1|m MATERIAL WEAPON_POWDER 1
- m MATERIAL WEAPON_POWDER 1|m MATERIAL WEAPON_POWDER 1|m MATERIAL WEAPON_POWDER 1
```
Suppose the latest item has less gem slots / different colored gem slots, or you set keep-gems to FALSE. In all these scenarios, gems are 'lost' so that this config option (**true** by default!) gives them back to the player.
Enable in your config:
```
# Options for the Item Revision System
item-revision:
# If an item is updated, and the new version does not
# keep its gems, this will give the gems back to the
# player so that they don't get lost forever.
drop-extra-gems: true
```
You can now go to your config and add, under item-revision:
```yml
item-revision:
phat-loots:
display-name: true
lore: true
enchantments: true
soulbound: true
upgrades: true
gemstones: true
modifications: true
external-sh: true
```
Which will update your PhatLoot items to the latest format in `/mmoitems browse` as they are generated for players. Since this will regenerate items, the *Unstackable* ItemStat now works with PhatLoots also
***If this is not added to the config, ** the default is that all options are false, and the items are completely regenerated and RNG-rerolled.
**Update MythicLib**
Pro tip: Its not implemented in-game but you can write it in the config files directly:
```
crafting:
smithing:
'1':
input1: SWORD.HEARTSWORD
input2: SWORD.ORACLE_SWORD
# Makes extra gems drop instead of getting lost
drop-gems: true
# If both inputs have upgrades, how to treat them?
# upgrades: ADDITIVE # Sum them
upgrades: MAXIMUM # Largest of them (Default)
# upgrades: EVEN # Average
# upgrades: MINIMUM # Minimum of them
# upgrades: NONE # Actually just dont keep upgrades
```
+ Upgrade level of items may be kept, with its bonuses
+ Gem Stones are now perfectly kept, with all their stats
+ Enchantments may be kept (more details in-game)
+ Soulbound (was already working) may be kept.
+ Item Name may be kept (already kinda working)
+ Lore may be kept (more detail in-game)
Add to your config:
```yml
item-revision:
keep-data:
display-name: true
lore: true
enchantments: true
upgrades: true
gemstones: true
soulbound: true
```
*Requires MMOLib update*
- Automatically update old items by assigning different revision IDs for your templates. More about this feature on the wiki.
- config.yml version detection. This will help users update their config file when we change things!
You will now be notified if you use an outdated 'config.yml' file
Added an auto-soulbind stat which let's you automatically soulbind items when acquired.
Fixed ingredient displays showing up as "INVALID"
Fixed '/mi generate' not randomizing items
Fixed '/mi generate' not respecting '-id:'
Item Builder no longer throwing errors if tier doesn't have gen options
- Readded Durability in lore!
The format can be changed in 'dynamic-lore.yml'
You need to add - '%durability%' to lore-format.yml for it to work.
- Fixed ingredient name display
- Fixed NBTTag inputting & made it compatible with Double values
You can now use hex colors with most things!
The format is '<#xxxxxx>' and it works just like the old '&x' did.
The old format is still supported and sometimes they can even be mixed!
Requires MMOLib 1.2.3 or later
