You are not logged in.

  • Login
Bitte besucht unser neues Forum unter https://forum.nitrado.net | Please visit our new Forum at https://forum.nitrado.net

Dear visitor, welcome to Nitrado.net Prepaid Gameserver Community-Support - Archiv. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Hendrik124

Moderator im Ruhestand

  • "Hendrik124" is male
  • "Hendrik124" started this thread

Posts: 1,495

Thanks: 17

  • Send private message

1

Sunday, July 24th 2011, 7:24pm

Hifle [PERMISSIONS] BUKKIT

Hallo ich wollte fragen ob mir einer bei den permissions helfen kann?!





Hier die daten:

Die Gruppen

Admin, VIP, Moderator, Registriert, Gast, Server Admin


Vom [color=#3b3b3b

PermissionsBukkit[/color]]

# PermissionsBukkit configuration file
#
# 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'.
# Some plugins provide permission nodes that map to a group of permissions -
# for example, PermissionsBukkit has 'permissions.*', which automatically
# grants all admin permissions. You can also specify false for permissions
# of this type.
#
# Users inherit permissions from the groups they are a part of. If a user is
# not specified here, or does not have a 'groups' node, they will be in the
# group 'default'. Permissions for individual users may also be specified by
# using a 'permissions' node with a list of permission nodes, which will
# override their group permissions. World permissions may be assigned to
# users with a 'worlds:' entry.
#
# Groups can be assigned to players and all their permissions will also be
# assigned to those players. Groups can also inherit permissions from other
# groups. Like user permissions, groups may override the permissions of their
# parent group(s). Unlike users, groups do NOT automatically inherit from
# default. World permissions may be assigned to groups with a 'worlds:' entry.
#
# The cannot-build message is configurable. If it is left blank, no message
# will be displayed to the player if PermissionsBukkit prevents them from
# building, digging, or interacting with a block. Use '&' characters to
# signify color codes.

users:
ConspiracyWizard:
permissions:
permissions.example: true
groups:
- admin
groups:
default:
permissions:
permissions.build: false
admin:
permissions:
permissions.*: true
inheritance:
- user
user:
permissions:
permissions.build: true
worlds:
creative:
coolplugin.item: true
inheritance:
- default
messages:
build: '&cYou do not have permission to build here.'



Die Plugins

ChairCraft
Citizens

ColouredChat

Essentials

EssentialsChat

EssentialsGeoIP

EssentialsProtect

EssentialsSpawn
FalseBookBlock

FalseBookCart

FalseBookChat

FalseBookCore

FalseBookExtra
FalseBookIC

MinecartManiaAdminControls
MinecartManiaAutocart

MinecartManiaAutomations

MinecartManiaChestControl

MinecartManiaCore

MinecartManiaSignCommands

MinecartManiaStation

WelcomeMessage

WorldEdit

IChat
Iconomy
iconomychestshop

mothernature
treeassist



Alle Plugins sind für build 1000 oder noch 953




Ich bedanke mich im voraus! Es wäre sehr nett wenn das einer machen würde weil ich in diese Permissions bekloppt geworden bin!

This post has been edited 1 times, last edit by "Hendrik124" (Jul 24th 2011, 7:30pm) with the following reason: kp


boggler17

User / Kunde

Posts: 33

  • Send private message

2

Sunday, July 24th 2011, 9:14pm

Falsche Section - poste die config im PHP-Quelltext.

Hendrik124

Moderator im Ruhestand

  • "Hendrik124" is male
  • "Hendrik124" started this thread

Posts: 1,495

Thanks: 17

  • Send private message

3

Sunday, July 24th 2011, 9:17pm

PHP Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# PermissionsBukkit configuration file
#
# 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'.
# Some plugins provide permission nodes that map to a group of permissions -
# for example, PermissionsBukkit has 'permissions.*', which automatically
# grants all admin permissions. You can also specify false for permissions
# of this type.
#
# Users inherit permissions from the groups they are a part of. If a user is
# not specified here, or does not have a 'groups' node, they will be in the
# group 'default'. Permissions for individual users may also be specified by
# using a 'permissions' node with a list of permission nodes, which will
# override their group permissions. World permissions may be assigned to
# users with a 'worlds:' entry.
#
# Groups can be assigned to players and all their permissions will also be
# assigned to those players. Groups can also inherit permissions from other
# groups. Like user permissions, groups may override the permissions of their
# parent group(s). Unlike users, groups do NOT automatically inherit from
# default. World permissions may be assigned to groups with a 'worlds:' entry.
#
# The cannot-build message is configurable. If it is left blank, no message
# will be displayed to the player if PermissionsBukkit prevents them from
# building, digging, or interacting with a block. Use '&' characters to
# signify color codes.

users:
ConspiracyWizard:
permissions:
permissions.exampletrue
groups:
- admin
groups:
default:
permissions:
permissions.buildfalse
admin:
permissions:
permissions.*: true
inheritance:
- user
user:
permissions:
permissions.buildtrue
worlds:
creative:
coolplugin.itemtrue
inheritance:
- default
messages:
build'&cYou do not have permission to build here.'

_NameLess_

Moderator im Ruhestand

  • "_NameLess_" is male

Posts: 8,321

Location: Tirol, Österreich

Occupation: Studierender | Foren-Moderator | Anime Hero | Nitrado Minecraft Testserver

Thanks: 16

  • Send private message

4

Sunday, July 24th 2011, 10:55pm

Also, konfigurieren wird sie dir hier keiner.
Über Fehler ausbessern lässt sich reden.

1. Im richtigen Unterforum posten. ...Ich verschiebe es.
2. Welche Permissions Version verwendest du?
3. Deine Ordner Struktur+Inhalt auflisten. Bsp. /plugins/permissions/...
Inhalt von Permissions Ordner: globalconfigs, storage....
4. groups.yml und users.yml posten.
5. ggf. Fehlermeldung des server.logs posten.

Das wären dann wohl mal die wesentlichen Schritte.

MFG
Name
Die deutsche Sprache ist Freeware.
Das heißt, du darfst sie uneingeschränkt nutzen. ABER(!) die deutsche Sprache ist NICHT Open Source.
Das heißt, du darfst sie nicht nach deinen Vorstellungen verändern!

Ein Problem ist halb gelöst, wenn es klar formuliert ist.


Bitte besucht unser neues Forum unter https://forum.nitrado.net| Please visit our new Forum at https://forum.nitrado.net

Similar threads