Remove "ban" command - permissions help

Discussion in 'Bukkit Help' started by stuffe, Dec 19, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    stuffe

    Hi all,
    I registered just to ask this one question. My son had a Bukkit server (latest version) running on this PC, so we have full access to the console etc. The only plugins are Worldedit 5.0, Commend Book 1.7 and PermissionsBukkit 1.2.
    The server is just used by a dozen or so school friends, and everything is fine, all users are OP, no issues with griefing or such like. I have only 1 issue. Sometimes the kids get happy banning each other - as 12 year olds do...
    Please can someone explain how, whether using permissions or whatever, I can prevent any user from issuing a ban command except for straight from the console? I just don't understand the whole user/group/node things at all, it seems great for big servers but overkill for this little hobby one.
    Thanks ;)
    Dan
     
  2. Offline

    TnT

    You can use the bukkit.yml to redefine commands - this should do the trick for what you want.
     
  3. Offline

    HotelManager24

    You could also just de-op them. Bukkit gives all OPs some basic commands including "/ban". Don't tell them about "/kick". :p
     
  4. Offline

    stuffe

    @hotelmanager - rather let them keep ops, but thanks for suggestion
    @TnT - can you show me how to do this please? If I could rename ban to be bann and kick to be kickk or something it would be a godsend.

    I tried the bukkit.yml redefine, but it just adds a new alias, it doesn't rename it. I put bannn: ban into it, and both ban and bannn work now. I need to remove access to ban, and kick, via whatever method is simplest. I have console access to ban and kick, and don't want any user including ops to have them

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 22, 2016
  5. Offline

    TnT

    Read here: http://wiki.bukkit.org/Bukkit.yml#aliases

    Should just be able to add this line under aliases:
    Code:
    ban:bannnnnnn
    
     
  6. Offline

    stuffe

    Sorry, no beans - it doesn't remove the ban command, just adds a new alias to it without removing the old one.
     
  7. Offline

    yttriuszzerbus

    Deop them, then with a permissions plugin give them the bukkit.command.[commandgoeshere] permissions you need.
     
  8. Offline

    stuffe

    Is it not easier to remove the 2 commands that I don't want, than add the several doxen that they do want? Is there really no simple way to do this? I'm not a regular minecraft player, so I don't know it in that much detail, I'm just wanting to do this to stop the arguments over banning :/ I've tried including the commandbook.bans.ban: false lines in all sorts of yml files, it just isn't clearly explained how I can configure this anywhere :(
     
  9. Offline

    TnT

    @stuffe
    Hmm, I thought you could completely redefine all commands that way.

    I know this is not what you wish to go for, but if you can't redefine in the bukkit.yml, you might have to go for a permissions plugin.

    Alternatively, enforce the bans. Tell them that if they ban someone, they'll also get banned and the ban will not be lifted for 24 hours. This will take some extra work (banning the person who issued the ban) but I imagine it would calm them down quite a bit.

    I'm surprised they haven't started issuing the '/stop' command as a prank.
     
  10. Offline

    stuffe

    OK, well I'm trying with the permissionsbukkit and commandbook. I've set a group called mods, set a user into that group, and given it the command commandbook.give, but I'm unable to give myself anything. I'm sure the yml is correct in terms of errors. Basically I set the following:
    commandbukkit config.yml - no changes
    permissionsbukkit - config.yml - as follows:
    danstuffe:
    permissions:
    server.mod: true
    groups:
    - mods
    groups:
    default:
    permissions:
    server.basics: true
    admin:
    permissions:
    server.admin: true
    inheritance:
    - user
    mods:
    permissions:
    server.mod: true
    commandbook.bans.ban: false
    commandbook.give: true
    inheritance:
    - user
    user:
    permissions:
    permissions.build: true
    commandbook.bans.ban: false
    worlds:
    creative:
    coolplugin.item: true
    inheritance:
    - default
    messages:
    build: '&cYou do not have permission to build here.'
    No joy. I'm happy to create a new mod group, and put everyone in it, and manually enter the commands from the commandbook list minus the ban ones if it would work, but this initial test by givign me the give command failed.
     
  11. Offline

    Royal_Soda

    stuffe
    If you still have trouble with this issue, I wouldn't mind putting a small plugin together for you. It's easy and quick to make. I could just make it so if a player whom is op issues a ban or kick command, the event is set to null.
     
  12. Offline

    mixixp

    edit the global group file
     
  13. Offline

    Jade

    PermissionsBukkit, is rather easy, its just open in Notepad++, space 4 times, type permission... under the group you want.
    //offtopic -- Royal_Soda I like SLAMP, thanks Soda ;3
     
  14. Offline

    Royal_Soda

    Darky1126
    No problem-o! I'll be updating to the latest build very soon. I got a new comp, so I lost the src. But no worries, the old version works! :)
     
Thread Status:
Not open for further replies.

Share This Page