You may edit this behaviour directly onto the yml file for now.
```
crafting:
smithing:
'1':
input1: SWORD.HEARTSWORD
input2: SWORD.ORACLE_SWORD
drop-gems: true
upgrades: MAXIMUM
enchantments: MAXIMUM
```
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
```
**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
```
Under the new RNG parameters, is the chance of getting this same RNG roll less than 1 in 3,000?
If the answer is *yes*, the stat is Rerolled with the new parameters. Otherwise it remains the same :)
Or then again, you can always enable in the config, if you wanted them to roll
```yml
item-revision:
reroll-when-updated: true
```
(RPG Provider is, which plugin tells MMOItems what class / level players are, like MCMMO power level or MMOCore or whichever).
Add to your config:
```
preferred-rpg-provider: <plugin>
```
If you misspell the name, you'll get this list telling you all RPG Providers supported:
```cs
[MMOItems RPG Provider] These are the supported ones:
[MMOItems RPG Provider] + MMOCore
[MMOItems RPG Provider] + Heroes
[MMOItems RPG Provider] + SkillAPI
[MMOItems RPG Provider] + RPGPlayerLeveling
[MMOItems RPG Provider] + RacesAndClasses
[MMOItems RPG Provider] + BattleLevels
[MMOItems RPG Provider] + mcMMO
[MMOItems RPG Provider] + McRPG
[MMOItems RPG Provider] + Skills
[MMOItems RPG Provider] + SkillsPro
```
Sorry about that I just really like the Mango so I based the entire system on top of a 'temporal' test that shuts everything down if the mango was missing....
Also, Updating items with RevID should no longer reroll RNG stats if you have the following in your config:
```
item-revision:
reroll-when-updated: false
```
Also the spread formula for DoubleData is kind of strange so an alternative has been added, add this to your config to use:
```
additive-spread-formula: true
```
Recipes now work even if the Mango Consumable was deleted.
Sorry about that I just really like the Mango so I based the entire system on top of a 'temporal' test that shuts everything down if the mango was missing....
Also, Updating items with RevID should no longer reroll RNG stats if you have the following in your config:
```
item-revision:
reroll-when-updated: false
```
Also the spread formula for DoubleData is kind of strange so an alternative has been added, add this to your config to use:
```
additive-spread-formula: true
```
Fixed bug where Updating an item would cause the template to become leveled up (this was absolutely ridiculous and hilarious btw), fixes Ticket #mmoitems-1283
Changes:
Unbreakable now will restrict items from losing all types of durability (custom and vanilla).
New Durability Bar boolean stat. This determines whether or not the vanilla durability bar will be shown when using custom durability. Note: This will be scaled according to the custom durability.
**You know what? Dont use vanilla color codes, just go to https://htmlcolorcodes.com/color-picker/ and pick a color for it**
```
name-suffix: ' <#CEEE70>+#lvl#'
```
