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 144
    • Issues 144
    • 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
  • #721

Closed
Open
Created Feb 24, 2022 by LcorpOfficial@LcorpOfficial🔨Reporter

[Suggestion] nearClaim condition with GriefDefender, add GD claimtypes condition

Summary

nearClaim condition only seems to work with GriefPrevention. If there is a possible way for it to also handle GriefDefender it would be great as there are currently no ways to handle this without using worldguard in tandem.

Usage

setting a condition for nearClaim should identify if GD or GP is used, and adjust accordingly. Additionally, accepting GD claim-type as a condition could be super useful in setting spawn conditions in town claims, basic claims not being able to fire certain skills, etc etc.

Value

GD is used more and more as GP becomes more deprecated. GD claims are usually decently protected areas as well. Claims are identifiable by category/type as well

Priority

3-5; it would trim my randomspawns config alone down by nearly 30%, and streamline preventing MM skills from doing things they shouldn't do.

Implementation

I believe the GD nearClaim condition should be seamless and be part of the current nearClaim condition.

The GDclaimtype condition would be likely setup as such:

skillname:
  Conditions:
  - GDClaimtype{t=town,basic,admin,subdivision} true #can be true|false|orElseCast|etc
    #can be one or multiple types? basic should include subdivision by default though.
  Skills:
  - skill{s=badassskilliuse} @target ~onkill
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking