These are all of the placeholders and special characters you can use in skills and mechanics that use strings. There are some examples of usage at the bottom to get you started.

Note: Usage of many variables in skills are locked to the premium versions, excluding MMOCore, special characters, color codes, and setvariable.

Special Characters

Color Codes

These color codes work anywhere in mob- and skill-files. They will even properly format tellraw-commands used in command skills!

Legacy color codes:

It's recommended that you use MiniMessage tags for text styling and text decorations. Here's an example using MiniMessage tags:

MessageSkill:
  Skills:
    - message{m=<rainbow>This text is a rainbow</rainbow> but <red>this is red</red>!} @target
    - message{m=<#bae5f4>This is a cool color that I picked from</#bae5f4> <red><click:open_url:https://www.color-hex.com/color/bae5f4>color-hex site</click></red>} @target

MiniMessage also has a web viewer to see what your text will look like in game.

Additional Placeholders

Links to placeholders added by addon plugins. Any placeholders from these links will not work without that plugin installed.

• Mythic Crucible
• MCPets

Placeholders

Scoped Placeholders

Most placeholders that fetches data "from the environment" have a scope prepended to them. You can see the scope as "telling the placeholder" which entity or location to fetch the data from.

::include{file=/Skills/Placeholders/Scoped-Placeholder-Table.md}

So, for instance, the <caster.name> placeholder will be retuning the name of the mechanic's caster, while <target.name> will also be returning a name, but this time it will be that of the mechanic's target

  Skills:
  - message{m=Hello <target.name>, i am <caster.name>} @NearestPlayer

Misc Placeholders

Item Placeholders

Score Placeholders

Text Placeholders

Variable Placeholders

These placeholders will return whatever variable has been called. For instance <caster.var.[name]> will return the value of the caster's [name] variable.
Some of these variables are only generated and available under some special circumstances, such as some specific trigger/attribute/metamechanic being used previously in the skilltree.

  Skills:
  - setvariable{var=caster.test1;val=1} @self
  - setvariable{var=target.test2;val=2} @self
  - message{m=<caster.var.test1> <caster.var.test2> <target.var.test1> <target.var.test2>} @self

If you execute this metaskill yourself, this will send you a message saying 1 2 1 2 because the target of every mechanic is the caster, so the affected registry is always the caster's even if a "target" scope is used

Meta Placeholders

You may now be wondering "Ok, but what is that Return Type listen after the placeholder's explanation?"
That value determines

• What data the placeholder is returning and, subsequently
• What Meta Placeholders you can use to mutate it!

For instance... do you want to uppercase a string? Why not use

<caster.name.uppercase>

Do you want to remove possible whitespace characters from the edges? then you can also

<caster.name.uppercase.trim>

See the full documentation HERE

Placeholder Attributes

Some placeholders can use a set of attributes to further define the output they will give

All placeholders

Double Return Type Placeholders

  Skills:
  - message{m="<target.hp{round=2}>"} @self

PlaceholderAPI Integration

Other than being able to use PlaceholderAPI placeholders anywhere placeholder support is in place, MythicMobs introduces some new PAPI placeholders that can be used by third parties to fetch MythicMobs-related values.

PlaceholderAPI Parsing

When using placeholders via PlaceholderAPI, it is important to remember that some of them are meant to be parsed against a player, and if parsed against a mob they may behave unexpectedly.
More concretely, this means that:

• If used inside a mechanic, the target must be a player
• If used inside a condition, the checked entity must be a player (caster for conditions, inherited targets for targetconditions, trigger for triggerconditions)

...and so on

Custom Placeholders

It's possible to create custom placeholders in any Pack by creating a file named placeholders.yml in the pack directory. These can be static or you can define conditional placeholders - the first one that evaluates true will be chosen, or the Default if they're all false.

Custom placeholders can be used via <placeholder.[CustomPlaceholder]>, with [CustomPlaceholder] being the name of your custom placeholder.

TestPlaceholder: 'some value'

TestConditionalPlaceholder:
  Day:
    Conditions:
    - day
    Value: day
  Night:
    Conditions:
    - night
    Value: night
  Default: idk

TestRandomPlaceholder:
- red
- green
- blue

A value of "null" is not accepted

Static Placeholders

Placeholders are considered "Static" when their parsing can only ever result in a single, defined output.

As of now, this is only the case for Custom Placeholders that have a single possible value

TestPlaceholder: 'a single value'
AnotherTestPlaceholder: 'another single value'

Load-Time Static Placeholder Parsing

Static Placeholders not parsed when the configuration line is executed at runtime, but are parsed and replaced as soon as the configuration is loaded in, only once per reload, and before any other parsing is done.

This has numerous advantages!
The most obvious one is that of performance: If placeholders are replaced at load time, at runtime they will appear as normal strings, not needing to be parsed again and saving on resources.

There is also quite an interesting application to this: since static placeholders are parsed and replaced before anything else is, they can be used anywhere in the configuration files, even in places where normal placeholders would not make sense, such as internal names, mechanic names or anything else!

# placeholders.yml
test: "message=1;"
debug: "#log"

testPreparsedPlaceholders:
  Skills:
  - message{<placeholder.test>} @self
  - <placeholder.debug>{message="hello world"}

Examples

This will make a mob send a teal message to all players in a radius of 20 blocks around in itself, stating what entity killed it in green.

    Skills:
    - message{m="<&b><caster.name><&r> was slain by <&a><trigger.name><&r>."} @PIR{r=20} ~onDeath

This skill will make an announcement when the mob spawns that looks like this:

  Skills:
  - Skill{s=SaveBossLocation} @self ~onSpawn
  - message{m="&eA &BGiant Zombie&e (Level &4<caster.level>&e) &ehas spawned at <caster.var.SpawnLoc>"} ~onSpawn @PlayersInWorld
  - message{m="&eThe &BGiant Zombie&e (Level &4<caster.level>&e) &espawned at <caster.var.SpawnLoc>&e has been slain."} ~onDeath @PlayersInWorld

Be sure to place this skill somewhere in the skills file

SaveBossLocation:
  Skills:
  - setvariable{var=SpawnLoc;type=STRING;value="&b<caster.l.x>&e, &b<caster.l.y>&e, &b<caster.l.z>";scope=CASTER} @self

You can also use color tags and formatting tags to make the mobs have pretty names:

ZOMBIE:
  Display: 'ZOMBIE &F- &A<caster.hp>/<caster.mhp>HP &F- &ELv.<caster.level>'