This is my Worldguard/World/region.yml file My adventurer1 section it seems like people can still access the area eventhough i flag the area Code: # # WorldGuard regions file # # WARNING: THIS FILE IS AUTOMATICALLY GENERATED. If you modify this file by # hand, be aware that A SINGLE MISTYPED CHARACTER CAN CORRUPT THE FILE. If # WorldGuard is unable to parse the file, your regions will FAIL TO LOAD and # the contents of this file will reset. Please use a YAML validator such as # http://yaml-online-parser.appspot.com (for smaller files). # # REMEMBER TO KEEP PERIODICAL BACKUPS. # regions: [B] adventurer1:[/B] [B] type: cuboid[/B] [B] min: {x: -2880.0, y: 0.0, z: -128.0}[/B] [B] max: {x: -2833.0, y: 255.0, z: -81.0}[/B] [B] priority: 0[/B] [B] flags: {entry: deny}[/B] [B] owners: {}[/B] [B] members:[/B] [B] groups: [adventurer][/B] door: type: cuboid min: {x: -3378.0, y: 94.0, z: 269.0} max: {x: -3376.0, y: 97.0, z: 273.0} priority: 0 flags: {entry: deny} owners: {} members: groups: [settler, adventurer] gate: type: cuboid min: {x: -3378.0, y: 106.0, z: 270.0} max: {x: -3376.0, y: 106.0, z: 272.0} priority: 0 flags: {entry: deny} owners: {} members: groups: [citizen] spawn: type: cuboid min: {x: -3396.0, y: 0.0, z: 252.0} max: {x: -3345.0, y: 255.0, z: 288.0} priority: 0 flags: {} owners: {} members: {} thank you
Change the priority level from 0 to something else. __global__region has priority 0 so any regions you make you have to use /rg setpriority [region] x
Priorities have nothing to do with it. You're specifying the permission groups incorrectly. See: http://wiki.sk89q.com/wiki/WorldGuard/Regions/Flags#Setting_Groups In particular the comment "This does NOT refer to a permission group. It refers to region members/owners (which can contain permission groups)" and the last two examples.
