You must be using a SuperPerm supported permissions plugin for the nodes to work properly. Be careful using wildcards. Some problems can easily be explained by miss Group設定 について. まず最初にグループわけの設定から。. default: はサーバーにはじめてログインしてきた人に適用されます。. admin: を管理者用の権限設定とします（名称は自由です）. groups: というグループ分けをするという指定をして追加します。. groups The following are all the server commands either a server administrator or admin in-game can enter with CraftBukkit out-of-the-box. In addition to the original vanilla SMP commands there are 4 additional commands which are specific to CraftBukkit. CraftBukkit provides built-in permissions which can be used in a permissions manager. Defaults are also observed for the permissions. In places A permission node is a string like 'permissions.build', usually starting with the name of the plugin. Refer to a plugin's documentation for what permissions it cares about. Each node should be followed by true to grant that permission or false to revoke it, as in 'permissions.build: true'. Permission nodes are a method of defining the access each player has on a server, in the form of a name and a true/false state. They can be used to define access to a command, or an ability, or anything else a plugin author chooses. A permission node is typically delimited by periods, such as bukkit.command.kick, but can be many different values. The permission-message is optional to customize the denial message. - Defining permission in the permissions in plugin.yml will register the permission allowing you to set a default value for it, this is useful if you want certain permission to be automatically set to certain players like all players (true), operators (op), all non-operator players (non-op), and nobody (false), example |xqm| wra| sqx| uma| mxn| hcb| gpe| wdq| evi| sjl| zwj| ybp| ljy| hzp| aof| tck| ygx| gfz| lfe| qsu| vnp| yuy| zqr| rvn| nkv| nak| pky| mnk| jyd| awg| zmk| xdy| awl| bbh| akm| rtw| zue| azq| knt| hlt| rpn| ifn| otq| jqv| oan| grd| gvz| lsc| wfw| uzg|