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 147
    • Issues 147
    • 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
  • #735

Closed
Open
Created Mar 10, 2022 by Naiwhy@Naiwhy

[Bug] region conditions __global__ not working

I've noticed when trying to use the global region for the region condition that it does not seem to work. The region condition works when I state another one of my regions.

Each one of the region conditions listed does not work.

  • region{r=global} true
  • region{r=GLOBAL} true
  • region{r=global} true
  • region{r=GLOBAL} true

I do not believe that the region condition is considering global as a proper region, if I am missing anything let me know, I've looked through past discord discussions of people trying to use global as a region condition as far back as 1/10/2021, but their issues were ignored without a proper fix to their issues.

Screenshot_5

Screenshot_4

Edited Mar 10, 2022 by Naiwhy
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking