Inactive [SEC] EpicZones v0.37 - Polygon Based Area Protection - Now with Economy Support! [1.3.1-R2.0]

Discussion in 'Inactive/Unsupported Plugins' started by jblaske, Feb 2, 2011.

  1. Offline

    jblaske



    Features
    • Polygonal and Circular area creation. (Not just cuboids!)
    • In-game zone creation.
    • Provide a Circular border to your map.
    • Hierarchical Permissions with Child and Parent Zones.
    • Display Entering and Exiting messages in chat.
    • Enhanced /who
    • Advanced control of zone based regeneration
    • Many zone specific controls for things like Fire, Explosions and Mob spawning control
     
  2. Offline

    rthardin

    Thanks for addressing my question.

    Now, about Permissions and child zones: I would like to be able to define a locker room inside a building using zones, such that each administrator has access to their own small zone that no other administrators can enter. Unfortunately, I cannot get the behavior I am looking for.

    The building, hq1, is the parent zone. The individual lockers, al1 through al3, are smaller zones that exist within hq1, and are defined as child zones in zones.txt:

    Code:
    #Zone Tag|World|Zone Name|Flags|Enter Message|Exit Message|Floor|Ceiling|Child Zones|PointList
    hq1|world|Administrator HQ|pvp:false nomobs:false regen:false |Entering Administrator HQ...|Leaving Administrator HQ...|0|128|al1 al2 al3 |-5:-26 -11:45 46:46 46:100 -151:120 -145:62 -126:28 -70:0 -68:-31
    al1|world|Eric's Locker|pvp:false nomobs:false regen:false |Entering Eric's Locker...|Leaving Eric's Locker...|76|79||-30:-1 -25:-1 -25:1 -30:1
    al2|world|Simon's Locker|pvp:false nomobs:false regen:false |Entering Simon's Locker...|Leaving Simon's Locker...|76|79||-30:3 -25:3 -25:5 -30:5
    al3|world|Jake's Locker|pvp:false nomobs:false regen:false |Entering Jake's Locker...|Leaving Jake's Locker...|76|79||-30:7 -25:7 -25:9 -30:9 
    EpicZones is set up to allow build, destroy, and entry by default. The config.yml in Permissions is set up to deny default users the rights to edit the building (hq1), and deny Eric the rights to Simon's and Jake's lockers, while doing the same for Simon and Jake:

    Code:
    # Supports "Default" and "GroupUsers"
    plugin:
        permissions:
            system: default
    
    groups:
        Default:
            default: true
            info:
                prefix: '&f[&cGST&f] &e'
                suffix: '&f'
                build: false
            inheritance:
            permissions:
                - 'epiczones.hq1.build.deny'
                - 'epiczones.hq1.destroy.deny'
        Admins:
            default: false
            info:
                prefix: '&f[&bADM&f] &e'
                suffix: '&f'
                build: true
            inheritance:
            permissions:
                - 'essentials.*'
                - 'bb.admin.*'
                - 'epiczones.*'
                - 'permissions.*'
    
    users:
        Eric:
            group: Admins
            permissions:
                - 'epiczones.al2.build.deny'
                - 'epiczones.al2.destroy.deny'
                - 'epiczones.al2.entry.deny'
                - 'epiczones.al3.build.deny'
                - 'epiczones.al3.destroy.deny'
                - 'epiczones.al3.entry.deny'
        Simon:
            group: Admins
            permissions:
                - 'epiczones.al1.build.deny'
                - 'epiczones.al1.destroy.deny'
                - 'epiczones.al1.entry.deny'
                - 'epiczones.al3.build.deny'
                - 'epiczones.al3.destroy.deny'
                - 'epiczones.al3.entry.deny'
        Jake:
            group: Admins
            permissions:
                - 'epiczones.al1.build.deny'
                - 'epiczones.al1.destroy.deny'
                - 'epiczones.al1.entry.deny'
                - 'epiczones.al2.build.deny'
                - 'epiczones.al2.destroy.deny'
                - 'epiczones.al2.entry.deny'
    Note that the Admins group does not inherit anything from the Default group, so the two definitions that belong to Default should not apply to the Admins.

    The incorrect behavior: The deny lines for each administrator have no effect. For example, Eric is not denied entry to al2 or al3, can build within al2 and al3, and can destroy within al2 and al3. According to the documentation, the deny statements should override the default settings and prevent Eric from entering al2 and al3. Furthermore, since al2 and al3 are child zones, their rules should override the settings for the parent zone, hq1.

    I think I have the syntax right, since I have confirmed that a player that belongs to Default is unable to build or destroy within hq1.

    Am I going about this the wrong way? I would really appreciate some help.
     
  3. Offline

    jblaske

    Everything looks good except that admins have epiczones.* this means they get the ignorepermissions flag. So no permissions will apply to any admin whatsoever.

    It also let's them ignore borders, but you may have intended that.
     
  4. Offline

    rthardin

    Thanks for the quick reply.

    I removed the - 'epiczones.*' line from the Admins section, and restarted the server. I can confirm that the line was removed and the new file was loaded because I logged in as an administrator and the command /reloadez had no effect.

    Sadly, the behavior did not change. As Eric, I was able to walk into al2 and al3 and create/destroy as normal, which should be denied.
     
  5. Offline

    jblaske

    I apologize for the seemingly lazy tech support. I'm on my phone so its hard to troubleshoot. Are the defaults for entry build and deny set to true in your epic zones config.yml?

    If so, try setting them to false and adding specific allow permissions to each user for their locker. That's about the best I can come up with right now.

    Edit: you might also want to verify that your world name is correct in th zone file.
     
  6. Offline

    Duh102

    Setting the default behavior to deny entry, I was unable to enter any zone, even those that I had .entry permissions to, and also if I had .ignorepermissions enabled.
    Similarly, if I had entry defaulted to allow, I was able to enter any zone, including those I had specifically put .entry.deny to, without .ignorepermissions.
    *five minutes later*
    I found out that if you are Minecraft op (in ops.txt), per-player or per-group permissions get ignored entirely, but only up to the defaults.
    Subtracting myself from ops.txt fixed this so that behavior was obeyed, but that's really weird. Should it do that?
     
  7. Offline

    jblaske

    That does sound odd, but it's definitely something in Permissions, as I entirely ignore ops.txt I would ask on Nij's thread about why ops.txt overrides permissions, and if that is intended.
     
  8. Offline

    rthardin

    Haha, I think your tech support is far from lazy. You've been very prompt.

    Well, I tried setting the default to deny and inverted the permissions, and had the same incorrect behavior. I am fairly certain that the world file is correct because I get messages from EpicZones alerting me to entry and exit from the zones. I just get no denial of the specified actions for the child zones. The permission settings to deny default users from building and destroying within the parent zone work just fine.

    From the testing I have done, it looks to me that the permissions on the parent zone always override the permissions on the child zone. In other words, I haven't been able to create a child zone with different permissions than its parent.

    Has anyone had any luck with this? If so, I'd love to see your zones.txt and Permissions config.yml files so I can get mine working.
     
  9. Offline

    jblaske

    I've added a WorldGuard > Zones.txt converter to the op. But for convienence here is the link.
    Convert Your WorldGuard Regions.txt into a EpicZones Zones.txt



    I actually have a global zone with child zones and permissions are inheriting fine. Here are my files for comparison. Also do you have your users in the ops.txt, like Duh102 had?


    EpicZones Config.yml
    Code:
    defaultEnter: true
    defaultDestroy: false
    defaultBuild: false
    mapRadius: 2250
    enableRadius: true
    zoneTool: 280
    EpicZones Zones.txt (outlands encompasses the whole map, every other zone is a child to it)
    Code:
    #Zone Tag|World|Zone Name|Flags|Enter Message|Exit Message|Floor|Ceiling|Child Zones|PointList
    outlands|ceres|Outlands||Entering Outlands...||0|128|elderstone comp talu nexus kuruna hyperion arrakis ferro trathira nmafarm |-2500:-2500 2500:-2500 2500:2500 -2500:2500
    ferro|ceres|Ferro||Entering Ferro...|Leaving Ferro...|0|128|elderstone |-1652:1468 -1596:1260 -1272:972 -1240:828 -1180:800 -1036:832 -704:584 -656:580 -620:644 -496:628 -404:476 -388:396 -264:344 -112:368 152:296 388:572 600:660 848:1444 776:1620 628:1684 552:1896 388:1812 340:1900 228:1796 -16:1788 -36:1884 -20:1992 -288:2200 -464:2212 -592:2016 -596:1952 -860:1856 -988:1564 -1380:1520 -1444:1564
    nexus|ceres|Nexus||Entering The Nexus...|Leaving The Nexus...|0|128||-764:-620 -224:-620 -460:-356 -632:-396
    hyperion|ceres|Hyperion||Entering Hyperion...|Leaving Hyperion...|0|128||-1064:-1116 -1048:-872 -668:-376 -748:40 -628:144 -652:264 -604:536 -716:560 -1040:808 -1184:776 -1252:808 -1296:968 -1620:1248 -1676:1452 -1828:1320 -2079:624 -2400:552 -2436:248 -2236:172 -2184:-428 -1912:-508 -1840:-588 -1672:-608 -1456:-896 -1340:-900 -1300:-1012 -1304:-1060
    kuruna|ceres|Kuruna||Entering Kuruna...|Leaving Kuruna...|0|128||124:88 316:20 928:36 1056:120 1448:44 1616:80 1696:-60 1896:-32 1972:-64 2304:248 2012:724 1648:852 1544:1364 1280:1492 880:1432 620:632 408:548 168:276
    trathira|ceres|Trathira||Entering Trathira...|Leaving Trathira...|0|128||-620:576 -584:556 -564:416 -596:136 -720:36 -708:-72 -184:-608 -56:-588 52:-608 52:-664 16:-704 348:-1004 680:-1040 952:-988 1168:-1152 1384:-1108 1480:-976 1896:-992 1968:-780 1940:-656 1848:-568 1844:-512 1700:-372 1708:-176 1604:44 1448:20 1064:96 940:12 300:0 96:76 148:272 -108:332 -296:316 -412:368 -516:604 -608:612
    comp|ceres|CompGrounds||Entering Competition Grounds...|Leaving Competition Grounds...|0|128||1724:-1612 1952:-1324 1932:-1200 1596:-1004 1444:-1056 1312:-1284 1360:-1468
    arrakis|ceres|Arrakis||Entering Arrakis...|Leaving Arrakis...|0|128||-1048:-1368 -908:-1484 -556:-1528 -76:-1280 228:-1384 312:-1508 388:-2068 504:-2072 776:-1944 876:-1992 892:-1964 888:-1920 1060:-1732 1112:-1740 1204:-1676 1316:-1720 1516:-1712 1536:-1596 1432:-1580 1344:-1504 1248:-1248 936:-1008 692:-1060 328:-1028 -8:-704 -84:-640 -776:-644 -1024:-884
    talu|ceres|Talu||Entering Talu...|Leaving Talu...|0|128|nmafarm |-1708:-1784 -2224:-1104 -368:-2452 -284:-2348 -312:-2236 -264:-2104 -140:-2028 308:-1868 316:-1788 288:-1536 196:-1400 -76:-1320 -544:-1564 -928:-1512 -1076:-1372 -1060:-1144 -1324:-1080 -1356:-1040 -1360:-928 -1476:-928 -1688:-640 -1972:-604 -2064:-688 -2196:-704 -2232:-852 -1916:-1240 -1928:-1328 -1696:-1516 -1660:-1632
    nmafarm|Ceres|nmafarm||Entering Talu NMA...|Leaving Talu NMA...|0|128||-512:-2128 -560:-2128 -560:-2176 -512:-2176
    elderstone|Ceres|Elderstone||Welcome to Elderstone!||0|128||-689:1309 -690:1259 -641:1259 -640:1309
    Permissions config.yml (minus users, as i only use users to set groups and don't assign individual permissions there)
    Code:
    # Supports "Default" and "GroupUsers"
    plugin:
        permissions:
            system: default
    groups:
        Default:
            default: true
            info:
                prefix:
                suffix:
                build: true
            inheritance:
            permissions:
                - 'lwc.protect'
                - 'simpleshop.buy'
                - 'simpleshop.sell'
                - 'iConomy.payment'
                - 'iConomy.rank'
                - 'iConomy.list'
                - 'tplus.history'
                - 'epiczones.who'
        Outlander:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.outlands.build'
                - 'epiczones.outlands.destroy'
                - 'epiczones.ferro.build'
                - 'epiczones.ferro.destroy'
                - 'epiczones.hyperion.build'
                - 'epiczones.hyperion.destroy'
                - 'epiczones.kuruna.build'
                - 'epiczones.kuruna.destroy'
                - 'epiczones.trathira.build'
                - 'epiczones.trathira.destroy'
                - 'epiczones.arrakis.build'
                - 'epiczones.arrakis.destroy'
                - 'epiczones.talu.build'
                - 'epiczones.talu.destroy'
        Ferronian:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.ferro.build'
                - 'epiczones.ferro.destroy'
        Hyperionite:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.hyperion.build'
                - 'epiczones.hyperion.destroy'
        Kurunian:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.kuruna.build'
                - 'epiczones.kuruna.destroy'
        Trathiran:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.trathira.build'
                - 'epiczones.trathira.destroy'
        Arrakian:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.arrakis.build'
                - 'epiczones.arrakis.destroy'
        Taluan:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'epiczones.talu.build'
                - 'epiczones.talu.destroy'
        Moderator:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'lwc.mod'
                - 'tplus.tp.to'
                - 'tplus.tp.coords'
                - 'tplus.jump.jump'
                - 'tplus.history'
                - 'general.spawn'
                - 'kiwiadmin.ban'
                - 'kiwiadmin.kick'
                - 'kiwiadmin.unban'
                - 'kiwiadmin.reload'
                - 'bb.admin'
                - 'epiczones.outlands.build'
                - 'epiczones.outlands.destroy'
                - 'epiczones.ferro.build'
                - 'epiczones.ferro.destroy'
                - 'epiczones.hyperion.build'
                - 'epiczones.hyperion.destroy'
                - 'epiczones.kuruna.build'
                - 'epiczones.kuruna.destroy'
                - 'epiczones.trathira.build'
                - 'epiczones.trathira.destroy'
                - 'epiczones.arrakis.build'
                - 'epiczones.arrakis.destroy'
                - 'epiczones.talu.build'
                - 'epiczones.talu.destroy'
        SrMod:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Moderator
            permissions:
                - 'tplus.tp.here'
                - 'tplus.tp.others'
                - 'general.spawn'
        Admins:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Moderator
            permissions:
                - '*'
     
  10. Offline

    rthardin

    Thank you very much for posting your config files.

    It looks like your world is designed in such a way that it would be hard to test if child zones' permissions override the permissions of the parent. Outlanders, for example, have the right to build and destroy (and, by default, entry) in the Outlands region, but also have the same permissions for the child zones. Likewise, Ferronians can build and destroy in Ferro, but also in Elderstone. In these cases, the expected behavior is that the permissions of the parent region match the permissions of the child regions. The rights of the Outlanders never change when moving from parent zone to child zone.

    It looks like the inheritance is working just as expected. For example, I didn't see any specific permissions given to Elderstone. Can your Ferronians build and destroy in Elderstone just as they can in Ferro? If so, the permissions of Elderstone are inheriting properly from Ferro and are overriding the default behavior of being unable to build or destroy. Similarly, I would guess that removing ...

    Code:
                - 'epiczones.ferro.build'
                - 'epiczones.ferro.destroy'
                - 'epiczones.hyperion.build'
                - 'epiczones.hyperion.destroy'
                - 'epiczones.kuruna.build'
                - 'epiczones.kuruna.destroy'
                - 'epiczones.trathira.build'
                - 'epiczones.trathira.destroy'
                - 'epiczones.arrakis.build'
                - 'epiczones.arrakis.destroy'
                - 'epiczones.talu.build'
                - 'epiczones.talu.destroy'
    ... from the Outlanders would not change the behavior, since their permissions in the Outlands would be applied to the child zones, just as the permissions in Ferro are applied to Elderstone.

    Is it possible to deny Ferronians, for example, entry into Elderstone? If so, that would demonstrate that the .deny tag, when used on a child zone, correctly overrides the permissions of its parent. Right now, I can't get that sort of behavior to work correctly. My "Ferro" always overrides my "Elderstone," no matter how I set up the default permissions.

    For what it's worth, I don't use the ops.txt file either. All my permissions are defined in the Permissions config.yml file.
     
  11. Offline

    jblaske

    I do not have any explicit deny's yet, but when i get home tonight I can test a few.

    I'd like to figure out what the kink in this is for you, It's now driving me crazy that it's not working for you.
     
  12. Offline

    rthardin

    I wish there was more that I could do to help! I feel kinda bad just whining on your thread, haha.
     
  13. Offline

    jblaske

    We will get it figured out. Can you please PM me all 3 of your files? That way i can set up my test environment with your settings and get to the bottom of it.
     
  14. Offline

    rthardin

    Sent, thanks again.
     
  15. Offline

    jblaske

    Version 0.7
    • Fixed a bug in permissions where child explicit deny was being overridden by the parent zone.
    • Fixed a bug where permissions were not properly refreshing when using /reloadez
    If you are explicitly denying access in a child zone, you will need this update, otherwise you should be fine till 0.8
     
    rthardin likes this.
  16. Offline

    Kainzo

    Is there anyway to 1) have it where only you can edit the zone you create (and the other users you want to edit it) so you have an owner system and 2) an admin style permission where they can edit all zones etc.


    Would be nice to have groups being restricted to what they can and cannot use.
     
  17. Offline

    rthardin

    As soon as I loaded the new code, my configuration started working as expected! Thanks!!
     
    jblaske likes this.
  18. Offline

    jblaske

    Currently EpicZones does not support delegation, but may in the future.

    If you add epiczones.ignorepermissions to a group or user, they can edit anywhere. But are still limited by the map border. if you want them to be able to go past the border give them epiczones.ignoremapradius
     
  19. Offline

    Brad Phusion

    Thanks for this, Jblask. So far, I haven't found any problems. Well, one, but I fixed it myself :p
    Curious though, how are you coming along with the nomobs? This would be sooo helpful. Thanks in advance, and goodwork (Keep it up!)
     
  20. Offline

    Xemnas33

    The war plugin also uses the /zones command =/
     
  21. Offline

    jblaske

    Thanks for the heads up. I will be talking with the plugin dev so we can work out a resolution.
     
  22. Offline

    JakeNova

    Alright, I just moved to the new version as the past few times I tried it didn't work and I just kept the old way as that still worked. So, my zones.txt is attached to this, I only have 1 world, no nether. But that really isn't a problem. I have the correct JAR in the plugin folder, but the /reloadez command is not giving me anything. Plus, the logs say it is an unknown command. I have tried reloading all plugins and re-placing the JAR into the server while it is down, but that did nothing. So, IDK what else to try, leading me to post here.

    Thanks in advance for the help. And great plugin!
     

    Attached Files:

  23. Offline

    jblaske

    Do you have the "epiczones.admin" permission? That is required for /reloadez since version 0.6 I'm pretty sure.
     
  24. Offline

    JakeNova

    I had tried adding that, although I didn't think it was necessary if I already just had a "*" node for my permissions. That didn't do anything. And if that were the problem, would the logs still not say I tried that command but I did not have sufficient permissions/access? I just tried reloading with Essentials and that did nothing. Essentials still lists EpicZones as green, or installed, though.
     
  25. Offline

    jblaske

    I can't reproduce this behavior... anybody else out there getting this?

    I usually just reload from the console anyway, makes me feel better knowing everything is refreshed properly.
     
  26. Offline

    JakeNova

    I just reloaded and it now works for some strange reason. At least, the actual plugin. I am still trying to play with the settings. So, that zones.txt outlines 4 zones, the spawn, which I want everyone to be allowed to go in but not modify, the PVP area, which I only want PVP members to go in and to modify, the PVE area, which I want only PVE members allowed in and to modify. Then there is "world" which I don't want anyone to go into so that it stops people from going out of their desired zones. How would I set up the child system and the permissions system to allow that? I have the areas where spawn and the two other main zones touch overlapping so that people can walk over the border between them and not have to deal with the "world" zone stopping them. I have tried many different ways, but when ever I have the epiczones.world.entry.deny in to the permissions, they can't go anywhere, even when I have world as a child zone to all the rest.

    Thanks for the help!
     
  27. Offline

    Brad Phusion

    For JakeNova, do you use permissions? I'm no expert, but you could add a group for each. Say there is Admins, Moderators, and Default. I don't know if this will work, but you could add PvE_Users and PvP_Users, add the users you want into each group, then add the permission commands, like deny, etc. Like I said, I'm no expert, I'm just trying to help.
     
  28. Offline

    Mercury

    Doesnt' work. They still spawn. #304.
     
  29. Offline

    Brad Phusion

    He is yet to implement the nomobs. It doesn't work yet. I'm still waiting for that. :p
     
  30. Offline

    Mercury

    Ah ok, Ill wait also then :D
     
  31. Offline

    Morczor

    Oh nice WorldGuard converter, but please make Realms converter since durron seems to have dissapeared forever!
     

Share This Page