You can view a good description in the comments in your Towny/settings/config.yml file for most of the permissions. This page is more to show what you can do with them.

Here we have the default group containing the important towny.town.* and towny.nation.* permissions. Without those, a player cannot even become a resident to a town (towny.town.resident).

Next up is the admins who get all the permissions. They get the very important ‘towny.admin’ node which pretty much lets them do anything. You also set the ‘town_maxplots: -1′ so that they arn’t limited to the amount of plots they can own. Actually it’s the global number set in config.yml, but if that’s -1 as well, then it’s infinite.

Now your moderators might not be trustworthy enough with full access, so you’ll assign them the ability to travel to other town spawn points, and let them fix silly mistakes in the wild.

By default, Towny prevents players from building in the wild. You can change that in the config, but if you might like to keep it like that and assign individual groups as jobs. Below is a sketchup for a Lumberjack and Engineer. The former can destroy wood and leaves, and place the saplings to replant that forest. You might also want to give him a ladder block so he can reach the tree top. The second is the engineer, who can build railways between the cities.

groups:
  Default:
    default: true
    permissions:
    - general.spawn
    - towny.town.*
    - towny.nation.*
    - towny.spawntp
    inheritance: []
    info:
      prefix: ''
      towny_maxplots: 1
      build: true
      suffix: ''
  Admins:
    default: false
    permissions:
    - '*'
    inheritance:
    - moderator
    info:
      prefix: ''
      towny_maxplots: -1
      build: true
      suffix: ''
  Moderator:
    default: false
    permissions:
    - general.time
    - general.teleport
    - general.teleport.here
    - general.player-info
    - towny.publicspawntp
    - towny.wild.*
    inheritance:
    - default
    info:
      prefix: ''
      towny_maxplots: 3
      build: true
      suffix: ''
  Lumberjack:
    default: false
    permissions:
    - towny.wild.block.6.build
    - towny.wild.block.17.destroy
    - towny.wild.block.18.destroy
  Engineer:
    default: false
    permissions:
    - towny.wild.block.66.*
    - towny.wild.block.27.*
    - towny.wild.block.28.*
    inheritance:
    - default

6 Responses to “Permissions”

  1. Reply shaun

    ive gone into config and made it so that anyone in wild can destory blocks but its not working ingame. i am running bukkit mod. ive tryed gettin permissions to work but its being painful. any suggestions?

  2. Reply MadeYouLook

    I really need help with some perm issues. We have 3 adminis and 2 moderators on our server, me one of them. I am the lord of a metropolis, and neither me, nor one of the admins who tried, can change towny permissions. It says succesful but then i /t and look and they havent changed. The other moderator however can change HIS perms for HIS town. This is a MAJOR issue, as my residents cant build in town, whilst outsiders can enter, build and destroy freely. Need help ASAP! D:

    • Reply Shade

      Join the IRC channel. Also mention the name of your town when you do. Also if you can, ask the server operator if they see if plugins/Towny/data/town/[town name].txt is being modified.

  3. Reply Matt

    someone please help.. I cannot get the towny_maxplots: 1 to work for the life of me and i really need it for my server. I have tried everything I know.

Leave a Reply

  •  

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax