This is an example of how to use it
`/mi give ACCESSORY BOOK_OF_STAMPS MonzterSlayer 1 0 100 0 silent`
You need to specify the unidentify-chance, drop-chance, and soulbound-chance, to then add silent.
If you use "s" or "silent" where I did, the message of "You received ITEM NAME" will not be sent to the Player. This does not affect any previous usages of the command, but if you want to use it, just add the "silent" argument!
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
```
Crafting recipes being visually constrained by additive RNG even when multiplicative is selected.
A pair of variables from the config not being read but until the first `/mmoitems reload`.
Also removed that strange empty slot when crafting stations display ingredients of amount divisible by 64
Implemented suggestion of ticket #403, you may add and edit the following quantities to your config.yml:
```yml
stats-displaying:
# This will be a prefix to numeric stats,
# changing their color when they are undesirable.
color-positive: '&b'
color-negative: '&9'
range-dash: '§f§l⎓'
```
https://git.lumine.io/mythiccraft/mmoitems/-/issues/403
A stat called "Projectile Particles" has been added for this purpose.
```
You may use any particle provided by Spigot. A list of available particles can be found here: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Particle.html
In addition to being able to change the particle, you can also change the color of certain particles. REDSTONE, SPELL_MOB, SPELL_MOB_AMBIENT, and NOTE can all change colors.
REDSTONE, SPELL_MOB, and SPELL_MOB_AMBIENT can use any RGB color. If selecting one of these particles, you must also provide a color. For example:
SPELL_MOB 255 255 0
NOTE particles are unique and instead require a single value between 1 and 24 for their color. For example:
NOTE 16
```
This functionality may be extended to other weapons such as muskets and whips in the future.
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
