Test Inventory

<Player>

• The player whose inventory will be checked, and score changed.

• Supports a few vanilla selectors.

<Slot>

• The slot in the player's inventory that will be checked. To read on slots see Inventory Slots.

• Examples: mainhand, offhand, chest, feet, any, 0-8, ec*

{Filter}

• Specify what NBT the item must have by the use of a GooP Item Filter.

• Always three words long.

[Amount] ( GooP 1.8.6+ )

• A quick number range of the amounts of items that will allow the command to succeed.

• If this is specified, it will dominate whether the command succeeds (Say you use 0 as the amount, usually, finding no items makes the command fail, but this time it will succeed because you are searching for there to be 0 items).

• May be omitted entirely (preserves backwards compatibility to when this wasn't there).

[Objective]

• The name of the scoreboard objective that will store the results.

• You must specify a score for this to be understood as a 'scoreboard objective,' otherwise it will be thought of as a shulker box name filter.

[±][Score][%]

• The score that will be set if the item is found. Will be round to an integer number.

• Using the amount keyword instead of an integer number will set the score to the number of items that mach in the slot:

  • If the item in that slot doesnt match, the score will be set to 0, because zero items matched the filter.

  • If the item in that slot matches, the score will be set to how many items are in that slot.

  • If you are targetting multiple slots, all the items of all the slots will be counted.

• May be an operation prformed on the score the player already has. See PlusMinusPercent page.

[Comp]

• Usually, this command succeeds and ends when the first item that matches is found (unless you used the amount keyword for score), which is undesirable if you want to use slots of success on all items that match. comp fixes this by forcing the command to go to completion.

• The [amount] argument, if you are using it, wirte comp after it.

• The [±][Score][%] argument, if you are using it, wirte comp after it.

• The shulker box name filter, if you are using it, wirte comp before it.

• May be omitted entirely (preserves backwards compatibility to when this wasn't there).

[Shulker Box Name Filter]

• Allows to only match items within shulker boxes named this, color-code and case sensitive.

• Must use slots that search within shulker boxes, example for slot #5 of any shulker box in the enderchest: ec*.5

• You can use the amount keyword in place for a score. This will count the amount of items the player has. More detail on this in Args Breakdown section.

• The shulker-box-name-filter only applies to slots that target shulker boxes, normal slots won't be affected.

  • See last example, below.

• To detect that the player has no item in that slot, use the filter v AIR 0

  • When used targetting multiple slots, it will then detect if any of these is free.

  • And if used with the amount keyword for the scoreboard score, it will count how many of these slots are free.

• You can use a range of accepted amounts, in the vanilla format: 2..20 will allow the command to succeed if the total count of the items is between two and twenty (inclusive).

  • You must thus use 6.. for something like "at least six"

In case for MMOItems to execute Mythic Skills, you are required to create a dynamic mythicSkill-to-mmoitemAbility .yml file:

• You must reboot your server for these dynamics files to load.

You also need a MMOItem with the ability attached to it:

Finally, you want to link your textures to stone_sword. I'll use Custom Model Datas 68 (normal) and 69 (powered) for mine.

Below you can see the two different textres I'll be using.

This skill will only work with a sword of MMOItem Type LONG_SWORD and ID SOULSTORM; It is hard-coded that way.

• You could make it detect more swords by uncommenting the lines commented with #EX#; If any succeeds, player score will end up being 3 and the skill will proceed.

• GooP Test Inventory is used here to detect when the sword is powered based on it having FROST_WALKER V enchantment.

  • There are more ways, like using /goop nbt cModelData <target.name> mainhand +0 swordhold which will add 0 to the current CustomModelData value of the sword, and store the final result in that player's swordhold score (And then detecting if the score is 68 or 69 --- 69 being the powered state).

• It is also used to make sure the player is holding the sword in their mainhand, and not in their offhand or whatever.

  • That way players wont be holding the sword in their offhand and some boots in the mainhand and enchant it with Frost Walker.

    • Or change any other items' CustomModelData.

  • Also, MMOItems has a 0.5s delay of updating held equipment, so it would be possible to hold the sword, then quickly change to another item, and run the skill - enchanting it with frost walker 5 and changing its CustomModelData.