Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 136
    • Issues 136
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Wiki
    • Skills
    • Mechanics
  • Terminable

Terminable · Changes

Page history
Update Terminable authored Feb 16, 2024 by Lxlp's avatar Lxlp
Hide whitespace changes
Inline Side-by-side
Showing with 19 additions and 2 deletions
+19 -2
  • skills/mechanics/Terminable.md skills/mechanics/Terminable.md +19 -2
  • No files found.
skills/mechanics/Terminable.md 0 → 100644
View page @ 4c23b904
## Description
Creates an [aura] that, after each mechanic of its onStart [metaskill], checks if a set of conditions is met: If so, the execution of the onStart skill is immediately cancelled. This effectively adds a conditional cancel mechanic after each line of the cascading meta skill.
## Attributes
| Attribute | Aliases | Description | Default |
|-----------|-----------|----------------------------------------------------------------------|---------|
| terminateconditions | conditions, cond, c | The conditions to check against | null |
| deep | | Whether the terminable aura, once its conditions have been met, should also stop the execution of the [metaskill] it has been called from | false |
| onterminate | ox | The [metaskill] to execute once the onStart is terminated | |
> This mechanic inherits every attribute of the [aura] mechanic
### Deep Attribute
The deep attribute is quite peculiar: when enabled, other than the onStart metaskill, it makes the terminate aura also affect the metaskill it was originally called from. So, if we had a situation like the following
```yaml
ExampleSkill:
Skills:
- terminable{deep=true;...}
- skill:test1
- delay 100
- mechanic2
SecondarySkill:
Skills:
- mechanic1
- delay 200
- mechanic3
```
Then the `ExampleSkill` and the subsequently called `SecondarySkill` metaskill would be stopped if the terminable aura had its conditions met: so, for example, if the terminable aura stopped the execution after 10 ticks, neither `mechanic2` or `mechanic3` could be triggered
## Examples
```yaml
Skills:
- terminable{
auraName=exampleAura;
d=2000;
conditions=[
- health{h=<50} true
];
onStart=[
- state{s=charged_attack}
- delay 20
- skill{s=ChargedAttackDamage}
];
onTerminate=[
- state{s=charged_attack;remove=true}
- state{s=stunned}
]} @self
```
## Aliases
- [x] stoppable
- [x] cancelable
- [x] exit
<!-- LINKS -->
[aura]: Skills/Mechanics/aura
[metaskill]: Skills/Metaskills
\ No newline at end of file
Clone repository
Home
Changelogs
Premium Features
Commands and Permissions
FAQ / Common Issues
Mythic Add-ons
Compatible Plugins
API Information
Packs
  • Pins
Mobs
  • Mob Options
    • Display Options
  • Mob Levels
  • Mob Factions
  • Power Scaling
  • Damage Modifiers
  • Equipment
  • BossBar
  • Custom AI
  • Custom Kill Messages
  • Threat Tables
  • Immunity Tables
  • Templates
  • Vanilla Overrides
  • Extra: Disguises
  • Extra: ModelEngine
Skills
  • Mechanics
  • Effects
  • Targeters
    • Filters
  • Triggers
  • Conditions
    • In-line conditions
  • Metaskills
  • Placeholders
  • Variables
  • Math
Items
  • Options
  • Attributes
  • Enchantments
  • Potions
  • Banner Layers
  • Firework
Drops & DropTables
  • Drops
  • DropTables
  • FancyDrops
Spawning
  • Spawners
  • Random Spawns
Stats
  • Custom Stat Options
  • Modifiers
  • Built in Stats
Examples
Useful Tips