SQLPerms Configuration

Apr 26, 2015
SQLPerms Configuration
  • SQLPerms (Configuration)

    This page is part of a series of SQLPerms documentation pages
    Overview:
    There are 2 main configuration files for SQLPerms, config.yml and permissions.yml. Both files are automatically generated if they do not already exist when the server starts.

    Files:
    config.yml:
    Code (Text):

    general:
      refreshIntervalSeconds: 60 #how often should we ping the database to both update users' ranks and keep the connecting alive
      debugMode: true #print stack traces
      enabledChannels: #what channels are enabled
      - default
    tabListColor:
      enabled: true #should a player's name in the tab list reflect the tabcolor setting in their rank? WARNING: this feature will not work if other plugins attempt to modify the tab list as well.
      channel: default #what channel should be checked for the tabcolor setting if this setting is enabled
    mysql:
      host: 127.0.0.1 #hostname of MySQL server
      port: 3306 #port of MySQL server
      database: sqlperms #database name for this plugin
      username: sqlperms #MySQL username for this plugin
      password: pass #MySQL password for this plugin
     

    permissions.yml:
    Code (Text):
    #What rank should new users be given?
    #You can set a different default rank for each channel, this instance will initialize every channel enabled in this instance's config.yml with the default ranks listed here
    defaultRank:
      default: guest
    ranks:
      guest:
        #The prefix for this group
        prefix: '&e[Guest] '
        #The number or letter of the color to use for this group in the tab list if enabled in config.yml
        tabColor: 'e'
        #Should players in this group be op?
        op: false
        #What permissions should players in this group have?
        #Prefix a permission with '-' to make it negative
        permissions:
         - -bukkit.command.plugins
         - -bukkit.command.version
        #What groups' permissions should this group inherit
        #Inherits work multigroup. ex if admin inherits moderator and moderator inherits guest, then admin has the permissions of guest
        #A groups permissions will override other permissions set in inherited groups
        #Inheritance MUST be formatted as a list (see admin for example), otherwise it will not work
        inheritance: []
      admin:
        prefix: '&c[Admin] '
        op: false
        tabColor: 'c'
        permissions:
         - bukkit.command.plugins
         - bukkit.command.version
        inheritance:
         - guest
      owner:
        prefix: '&4[The Owner] '
        op: true
        tabColor: '4'
        permissions: []
        inheritance:
         - admin
  • Loading...
  • Loading...