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 132
    • Issues 132
    • 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
  • Issues
  • #632

Closed
Open
Created Nov 27, 2021 by Ghmmy@GhmmyMaintainer

Add auraType options to all aura mechanics

Summary

The auraType is similar to the auraName, but can be used to categorize/filter certain auras into 1 (debuffs, buffs, cosmetic, etc). This would allow the auraRemove mechanic to remove all auras that grant debuffs, without messing with the other auras.

Usage

The auraType can contain any string, just like the auraName mechanic, but can be used in multiple auras at the same time, to prevent them from overriding eachother.

An example would be - onDamaged{auraName=WEAKENING;auraType=debuff;multiplier=1.5} @target ~onAttack which will grant the aura like normally. To remove all the debuff aura types, it would look as follow: - auraremove{aura=ANY;auraType=debuff;stacks=10} @self ~onRightClick

Value

This would allow users to create purge effects that wouldnt mess with auras that provide positive or cosmetic effects.

For servers that dont use a lot of auras, removing auras by name shouldnt be an issue. For servers that use countless amounts of different auras, it would be a no-go to enter all of those different auras.

Priority

It's crazy how I haven't come across anyone else mentioning this, but a lot of RPG games I play have some sort of purge effects that would remove either all buffs or all debuffs from a target.

Implementation

I would think it would be similar to how the auraName option works, in combination with the custom damage modifiers. But instead of it actually having a direct purpose, it only has effect during the auraremove mechanic or in a condition.

Edited Mar 30, 2025 by Brickgard
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking