vMythicBetonAddon

vMythicBetonAddon seamlessly connects MythicMobs with BetonQuest 3.0 by adding powerful native conditions for player tags, player points, global tags, and global points.

Instead of setting up complex workarounds, this lightweight addon lets you check BetonQuest data directly inside MythicMobs skills, inline targeters, and TargetConditions blocks.

Support the Project

vMythicBetonAddon is developed and maintained with care as part of the vPlugins project. If this addon helps your server, consider making a donation to support future updates, bug fixes, documentation and new projects.

Community & Support

Need help configuring conditions, want to report a bug, or suggest a feature? Join our community or check the documentation:

Main Features

• Native Integration: Check player tags and points directly within MythicMobs mechanics.
• Global Data Support: Read global tags and global points natively without overhead.
• Flexible Syntax: Full compatibility with inline targeters and standard TargetConditions blocks.
• Advanced Comparisons: Built-in support for flexible numeric evaluations (<, >).
• Logical Grouping: Check multiple conditions at once using efficient AND logic.
• Plug and Play: Zero configuration files needed—just drop it into your plugins folder and go.

Conditions Included

• bqtag → Checks a player-specific tag.
• bqpoint → Checks a player-specific point balance.
• gbqtag → Checks global BetonQuest tags.
• gbqpoint → Checks global BetonQuest points.

Requirements

Requirement	Supported Version
Paper (or forks)	1.21+
MythicMobs	5.6.1+
BetonQuest	3.0.0+
Java	21+

---

How to Use

Check if a player HAS a tag

TargetConditions:
  - isplayer
  - bqtag{tag=mypackage>my_tag}

Check if a player does NOT have a tag

TargetConditions:
  - bqtag{tag=mypackage>my_tag} false

Inside an inline targeter

- throw{v=10} @PlayersInRadius{r=6;conditions=[- bqtag{tag=mypackage>my_tag} false]}

Multiple tags (all must match)

- bqtag{tag=mypackage>tag_a,mypackage>tag_b}

---

Point Conditions

Syntax

- bqpoint{point=(package)>(point);value=(comparison)}

Comparison Format

bqpoint and gbqpoint use flexible value evaluation structures:

• 10 → Exactly 10
• <10 → 10 or less
• 10> → 10 or more

Check if a player has exactly 10 points

TargetConditions:
  - isplayer
  - bqpoint{point=mypackage>my_point;value=10}

Check if a player has 10 or less points

TargetConditions:
  - isplayer
  - bqpoint{point=mypackage>my_point;value=<10}

Check if a player has 10 or more points

TargetConditions:
  - isplayer
  - bqpoint{point=mypackage>my_point;value=10>}

Invert the point check with false

TargetConditions:
  - isplayer
  - bqpoint{point=mypackage>my_point;value=10>} false

Multiple points (all must match)

- bqpoint{point=mypackage>point_a,mypackage>point_b;value=10>,<5}

---

Global Conditions

Check if a global tag exists

TargetConditions:
  - gbqtag{tag=mypackage>global_tag}

Check if a global point has a value

TargetConditions:
  - gbqpoint{point=mypackage>global_point;value=5>}

Invert global checks

TargetConditions:
  - gbqtag{tag=mypackage>global_tag} false
  - gbqpoint{point=mypackage>global_point;value=<3} false

---

Technical Notes

• bqtag and bqpoint evaluate data directly from the target player.
• gbqtag and gbqpoint pull strictly from global BetonQuest data.
• Multiple comma-separated elements listed inside tag/point conditions use AND logic.