Bukkit

Guys my perms are still not working. I am sure i did everything right, spaces, permissions, and i did as semirotta said. I don't use : true now but it is still not working. Here is what my perms look likehttp://pastebin.com/NEV38anp

@Matuzalen

You could next time try pastebin.com instead of filling the page with permissions...
If you're using bPermissions, what the heck is this :true thing behind every node!?
I have NEVER used anything like that, thus I've never had issues.
Remove the darn TRUE thingie ...
Instead of
permissions.build true
just go with
permissions.build

you don't need any : true behind it...

hey guys sorry to bother but when i allow a permission for a default group it doesnt work!! I'm pretty sure i typed everything right.

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:
Leo:
permissions:
permissions.example: true
groups:
- default
groups:
default:
permissions:
permissions.build: true
paintball.general: true
war.player: true
war.warp: true
warps.tp: true
essentials.balance: true
essentials.balancetop: true
essentials.sell: true
essentials.pay: true
essentials.worth: true
essentials.afk: true
essentials.suicide: true
essentials.tpaccept: true
essentials.tpahere: true
essentials.tpa: true
essentials.spawn: true
plotme.use: true
plotme.limit.4: true
essentials.tp: true
economy.balance: true
economy.pay: true
economy.gives: true
economy.unlimited: true
economy.update: true
economy.config: true
economy.gshop: true
economy.gshop.add: true
economy.gshop.edit: true
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.'

debug: false

@SirMangler

There is...

There needs to be a way to set prefixes and suffixes up.

This page and mChat page are both as useless as George.W.Bush was to USA....

Hey! I am not sure if this is in bpermissions end issue or the mchatsuite but here we go: I use bpermissions + mchatsuite to add prefix & suffix for players in game. ISSUE:

Why do MOBS have ranks too? O_o every single mob who kills a player will be shown in chat as "Member" the [M] is member rank... Any help how to prevent this happening?

hey thanks for a good plugin it work but when the person been added to the group it dont show there rank when you talk is that right and if so can you do something about it ???

How can I use one set of permissions for multiple worlds?

Like

permissions:
  permission.build: true
worlds:
  world, world_nether, world_the_end:
    permission.build: false
  world_survival, world_survival_nether, world_survival_the_end:
   factions.fullplayer: true

@shadvalentine

@shadvalentine

Thank you so much!!! I'm so glad you helped!

Could a version be made to be compatible with Minecraft 1.5.1, rather than 1.5.2, please?

when i type /permissions group list
and internal error occurs
also it says that i don't have any groups

users:
    thenewchuck:
        permissions:
            permissions.example true
        groups:
        - admin
        
groups:
    default:
        permissions:
            permissions.build true
            dt.stopmusic true
            dt.user true
            dt.dismount true
            dt.destlist true
            dt.statlist true
            dt.travel: true
            dt.travelsigns.use true
            dt.home.set true
            dt.home true
            dt.ptoggle true
            dt.flight true
            dt.flightsigns.use true
            dt.flightlist true
    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.'

debug: false

@GranLupo123

yeah, it just needs a lot of in-game commands to do in future, e.g. permissions changes to save. permissions group create, modify, remove when online.

For some reason in your beta version v2.1. When I load my world I get an error that "default" key contained and unknown value.

However, even though I get the error. The permissions under default work fine.

I see a new beta version has been uploaded. Can you guys add some nodes to allow people to use levers, buttons, chests and pressureplates etc, but still have permissions.build: false?