Brauche Hilfe bei Essentials-Group Manager

[HeaDii]

hi,

ich brauche hife für meinen Server ich will gerne Group Manager benützen. Ich habe alles in der config auf meinen offline server gemacht und habe dann die config auf meinen server hochgeladen. Dort funkt aber nichts so wie ob die beiden plugins nicht zusammen arbeiten ich meine Essentials und group manager.

############################################################
# +------------------------------------------------------+ #
# |               	EssentialsChat                 	| #
# +------------------------------------------------------+ #
############################################################

chat:
  

  radius: 0
  

  
  format: '{GROUP} {DISPLAYNAME}&7:&f {MESSAGE}'
  #format: '&7[{GROUP}]&f {DISPLAYNAME}&7:&f {MESSAGE}'
	
  group-formats:
  #  Default: '{WORLDNAME} {DISPLAYNAME}&7:&f {MESSAGE}'
  #  Admins: '{WORLDNAME} &c[{GROUP}]&f {DISPLAYNAME}&7:&c {MESSAGE}'

  # If your using group formats make sure to remove the '#' to allow the setting to be read.



############################################################
# +------------------------------------------------------+ #
# |             	EssentialsProtect                	| #
# +------------------------------------------------------+ #
############################################################

protect:
  # Database settings for sign/rail protection

  # mysql or sqlite
  datatype: 'sqlite'

  # If you specified MySQL above, you MUST enter the appropriate details here.
  # If you specified SQLite above, these will be IGNORED.
  username: 'root'
  password: 'root'
  mysqlDb: 'jdbc:mysql://localhost:3306/minecraft'


  alert:
	on-placement: 10,11,46,327
	on-use: 327
	on-break: 

  blacklist:

	# Which blocks should people be prevented from placing
	placement: 10,11,46,327
	
	# Which items should people be prevented from using
	usage: 327
	
	# Which blocks should people be prevented from breaking
	break:
	
	# Which blocks should not be pushed by pistons
	piston:

  # General physics/behavior modifications
  prevent:
	lava-flow: false
	water-flow: false
	water-bucket-flow: false
	fire-spread: true
	lava-fire-spread: true
	flint-fire: false
	lightning-fire-spread: true
	portal-creation: false
	tnt-explosion: false
	tnt-playerdamage: false
	fireball-explosion: false
	fireball-fire: false
	fireball-playerdamage: false
	creeper-explosion: false
	creeper-playerdamage: false
	creeper-blockdamage: false
	enderdragon-blockdamage: true
	enderman-pickup: false
	villager-death: false
	# Monsters won't follow players
	# permission essentials.protect.entitytarget.bypass disables this
	entitytarget: false
	# Prevent the spawning of creatures
	spawn:
  	chicken: false
  	cow: false
  	creeper: false
  	ghast: false
  	giant: false
  	monster: false
  	pig: false
  	pig_zombie: false
  	sheep: false
  	skeleton: false
  	slime: false
  	spider: false
  	squid: false
  	zombie: false
  	wolf: false
  	cave_spider: false
  	enderman: false
  	silverfish: false
  	ender_dragon: false
  	villager: false
  	blaze: false
  	mushroom_cow: false
  	magma_cube: false
  	snowman: false
  
  # Maximum height the creeper should explode. -1 allows them to explode everywhere.
  # Set prevent.creeper-explosion to true, if you want to disable creeper explosions.
  creeper:
	max-height: -1
  
  # Protect various blocks.
  protect:
	# Protect all signs
	signs: true

	# Prevent users from destroying rails
	rails: true

	# Blocks below rails/signs are also protected if the respective rail/sign is protected.
	# This makes it more difficult to circumvent protection, and should be enabled.
	# This only has an effect if "rails" or "signs" is also enabled.
	block-below: true

	# Prevent placing blocks above protected rails, this is to stop a potential griefing
	prevent-block-on-rails: false
	
	# Store blocks / signs in memory before writing
	memstore: false

  # Disable various default physics and behaviors
  disable:
	# Should fall damage be disabled?
	fall: false

	# Users with the essentials.protect.pvp permission will still be able to attack each other if this is set to true.
	# They will be unable to attack users without that same permission node.
	pvp: false

	# Should drowning damage be disabled?
	# (Split into two behaviors; generally, you want both set to the same value)
	drown: false
	suffocate: false

	# Should damage via lava be disabled?  Items that fall into lava will still burn to a crisp. ;)
	lavadmg: false

	# Should arrow damage be disabled
	projectiles: false

	# This will disable damage from touching cacti.
	contactdmg: false

	# Burn, baby, burn!  Should fire damage be disabled?
	firedmg: false
	
	# Should the damage after hit by a lightning be disabled?
	lightning: false

	# Should people with build: false in permissions be allowed to build
	# Set true to disable building for those people
	build: true
	
	# Should people with build: false in permissions be allowed to use items
	# Set true to disable useing for those people
	use: true

	# Should we tell people they are not allowed to build
	warn-on-build-disallow: true


	# Disable weather options
	weather:
  	storm: false
  	thunder: false
  	lightning: false

############################################################
# +------------------------------------------------------+ #
# |        	Essentials Spawn / New Players        	| #
# +------------------------------------------------------+ #
############################################################

newbies:
  # Should we announce to the server when someone logs in for the first time?
  # If so, use this format, replacing {DISPLAYNAME} with the player name.
  # If not, set to ''
  #announce-format: ''
  announce-format: '&dWilkommen {DISPLAYNAME}&d auf unserem Server!'
  
  # When we spawn for the first time, which spawnpoint do we use?
  # Set to "none" if you want to use the spawn point of the world.
  spawnpoint: Spieler

# Set this to lowest, if you want Multiverse to handle the respawning
# Set this to normal, if you want EssentialsSpawn to handle the respawning
# Set this to highest, if you want to force EssentialsSpawn to handle the respawning
respawn-listener-priority: normal

# End of File <-- No seriously, you're done with configuration.

wenn ich im chat schreibe steht dort: "default Mein Name" obwohl ich keine groupe mit diesem name habe.
hoffe auf hilfe!

mfg
HeaDii

 

[Stonehengeflk98]

poste mal die groupmanager yaml

 

[HeaDii]

Das ist die groups.yml

groups:
  Gast:
	default: false
	permissions:
	inheritance:
	info:
  	prefix: ' [Gast]&f '
  	build: false
  	suffix: ''
  Spieler:
	default: true
	permissions:
	inheritance:
	- Gast
	info:
  	prefix: '&8 [Spieler]&f '
  	build: true
  	suffix: ''
  VIP:
	default: false
	permissions:
	inheritance:
	- Spieler
	info:
  	prefix: '&1[VIP]&f '
  	build: true
  	suffix: ''
   Supporter:
 	default: false
 	permission:
 	inheritance:
 	- VIP
 	info:
  	prefix: '&6 [Supporter]&f '
  	build: true
   Admin:
 	default: false
 	permission:
 	inheritance:
 	- Supporter
 	info:
  	prefix: '&4 [Admin]&f '
  	build: true
  Leitung:
	default: false
	permissions:
	- '*'
	inheritance:
	- Moderator
	info:
  	prefix: '&4 [Leitung]&f '
  	build: true
  	suffix: ''

config.yml

settings:
  config:
	# With this enabled anyone set as op has full permissions when managing GroupManager
	# The user will be able to promote players to the same group or even above.
	opOverrides: true
	
	# If enabled any plugins bukkit permissions which default to true will be left enabled.
	# If the player is op any permissions set to Op will follow suit.
	bukkit_perms_override: false
	
	# Default setting for 'mantoglevalidate'
	# true will cause GroupManager to attempt name matching by default.
	validate_toggle: true
	
  data:
	save:
  	# How often GroupManager will save it's data back to groups and users.yml
  	minutes: 10
  	# Number of hours to retain backups (plugins/GroupManager/backup)
  	hours: 24
  	
  logging:
	# level of detail GroupManager will use when logging.
	# Acceptable entries are - ALL,CONFIG,FINE,FINER,FINEST,INFO,OFF,SEVERE,WARNING
	level: INFO
	
  mirrors:
    	# Worlds listed here have their permissions mirrored in their children.
    	# the first element 'world' is the main worlds name
    	# subsequent elements '- world_nether' are worlds which will use the same
    	# user/groups permissions as the parent.
    	world:
      	- world_nether
      	- world_the_end

Eine yml die "groupsmanager.yml" heißt habe ich nicht.

mfg

 

[little_psycho11]

Du musst Dir das Plugin GroupManager runterladen. Das packst Du in den plugins Ordner. Daraufhin erstellt sich dort ein neuer Ordner "GroupManager"
In dem ist dann ein weiterer Ordner "worlds" für jede Deiner Welten ist in diesem wiederrum ein weiterer Ordner, in dem eine groups.yml vorhanden ist. Und da kannst Du die Permissions eintragen.

 

[Spongebob1399]

Ich würd dir Group-Manager nicht empfehlen da der die SuperPerms nicht Unterstützt die man für manche Plugins braucht.
Ich würd dir bPermissions, BukkitPermissions oder Perission*** (mein Liebling) empfehlen

Mfg Sponge