Can't get permissionsbukkit and essentials to work

Discussion in 'Bukkit Help' started by Darkbanisher, Jun 10, 2014.

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

    Darkbanisher

    Hi, I just want to start off saying I have tried everything I can think off, googled everything I can think off and found nothing, posting is my last last resort if I can't figure thing out myself.

    Anyways! A friend of mine decided to host an rp server and asked my help. I got everything set up the version he asked for 1.6.4 with older versions of the plugins.

    Now for the interesting part, he want to limit player from doing things outside of their "job".
    Thus a miner can't cut trees and a lumberjack can't mine iron ore.
    And then I found out something interesting.
    As far as I can see only permissions.build: true/false seems to be working for me.
    And using only that means the difference to a player being only able to walk & talk or do everything.

    For some reason no matter what I tell essentials it just won't restrict players.
    To spare from giant lists.
    Just assume I told the server the following:

    for jobs I used lines like this to enable doing things:
    essentials.build.break.16: true

    those jobs inherit from the group "general" wich contains a list of all items ANY player should be able to craft or "break".

    "general" in turn inherits from "user" (the "user" group contains all plugin permissions): (permissions.build is only true atm because else we can't do ANYTHING regardless of what I type)
    essentials.build.break.*: false
    essentials.build.craft.*: false
    permissions.build: true
    permissions.use: true

    As far as I can see permissionbukkit's anti-build is always eighter forcing everything to be allowed or disallowed. Or I managed to spend the last 2 days being a retard.
    Could someone tell me if I am correct and thus need to remove permissionsbukkit or if there is something i'm doing wrong?
    Perferably someone could show me a proper permissions.yml folder that uses both permissionsbukkit and essentials and then still manages to do the essentials.build things.
    Also for the record, no errors were found, permissionsbukkit and essentials are both working without errors "as far as I can see".
     
  2. Offline

    Necrodoom

    It doesn't sound like you have essentialsantibuild.jar on your server, paste startup log please.
     
  3. Offline

    Darkbanisher

  4. Offline

    Necrodoom

    So, yes, you don't have it.
     
  5. Offline

    Darkbanisher

    line 240: 2014-06-11 01:27:30 [INFO] [EssentialsAntiBuild] Enabling EssentialsAntiBuild v2.12.1
    [​IMG]

    I'm pretty sure I do.
     
  6. Offline

    Necrodoom

    Darkbanisher Oh, misread then. Do /ess debug, try build, paste console please.
     
  7. Offline

    Darkbanisher

    I have been playing arround alot with different setups trying to get some functionality working.
    It seems I was somehow able to block everything exept a few things with:
    permissions.build: false
    essentials.build.place.*: false
    essentials.build.place.58: true
    essentials.build.break.58: true
    essentials.build.place.17:0: true
    essentials.build.place.17: true
    essentials.build.break.17:0: true
    essentials.build.break.17: true
    essentials.build.place.58:0: true
    essentials.build.break.58:0: true

    and with debug on, these popped up:
    2014-06-11 15:23:58 [INFO] [Essentials] checking if Biocomm has essentials.build - false
    2014-06-11 15:23:58 [INFO] [Essentials] checking if Biocomm has essentials.build.break.58:0 - true
    2014-06-11 15:24:04 [INFO] [Essentials] checking if Biocomm has essentials.build - false
    2014-06-11 15:24:04 [INFO] [Essentials] checking if Biocomm has essentials.build.break.58:0 - true
    2014-06-11 15:24:19 [INFO] [Essentials] checking if Biocomm has essentials.build - false
    2014-06-11 15:24:19 [INFO] [Essentials] DataValue perm on Biocomm is not directly set: essentials.build.break.2:0
    2014-06-11 15:24:19 [INFO] [Essentials] checking if Biocomm has essentials.build.break.2 - false

    Even still essentials.build.place.17 doesn't seem to work unless :0 is added at the end.
    When I inverted it (place.*: true and the others false) it didn't quite work.
    I'm just confused even more now. Reason I didn't just pastebin the console log is cause its littered with restarts and like 100 different configurations I tried. Though what I put up is what came out first. Hope its still somewhat helpfull.
    EDIT: Just realised that permissions.build: false was set to true aswell, my bad. Il test again.
     
  8. Offline

    Necrodoom

    Darkbanisher I see only you trying to break 58 and 2, both working as expected. 58 is allowed, 2 is blocked. If you try to place 17, paste log showing it.
     
  9. Offline

    Darkbanisher

    Alright this test is performed with the following:
    build: false
    permissions.*: true
    permissions.build: true
    essentials.build.place.*: true
    essentials.build.break.*: false
    essentials.build.place.17: false

    console reply:
    11.06 16:14:51 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:14:49 [Server] INFO checking if Biocomm has essentials.build.place.4 - true
    11.06 16:14:49 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.place.4:0
    11.06 16:14:49 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:14:47 [Server] INFO checking if Biocomm has essentials.build.place.17 - false
    11.06 16:14:47 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.place.17:0
    11.06 16:14:47 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:21:11 [Server] INFO checking if Biocomm has essentials.build.break.17 - false
    11.06 16:21:11 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.break.17:0
    11.06 16:21:11 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:21:04 [Server] INFO checking if Biocomm has essentials.build.place.17 - false
    11.06 16:21:04 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.place.17:0
    11.06 16:21:04 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:22:13 [Server] INFO checking if Biocomm has essentials.build.place.5 - true
    11.06 16:22:13 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.place.5:0
    11.06 16:22:13 [Server] INFO checking if Biocomm has essentials.build - false
    11.06 16:22:12 [Server] INFO checking if Biocomm has essentials.build.place.5 - true
    11.06 16:22:12 [Server] INFO DataValue perm on Biocomm is not directly set: essentials.build.place.5:0
    11.06 16:22:12 [Server] INFO checking if Biocomm has essentials.build - false

    visible result:
    wood log place: "you are not permitted to place log here" -> works
    wood log break: "you are not permitted to break logs here" -> works
    cobblestone place: vanishes without a message back to my inventory. -> should not be happening
    dirt break: does not break, no message like the cobble -> not sure if it worked

    notes:
    nothing I place down seems to work even though essentials.build.place.* is true
    same way I don't think essentials.build.break.* is even working as the only message displayed is with logs.
    Any other case that the essentials.build.place.17: false just doesn't work but with the difference of not giving a message.
    I don't think wildcards apear to be working. Though I know they are as permissions.* is working.
     
  10. Offline

    Necrodoom

    Darkbanisher if you are getting denied with no error, its not essentialsantibuild causing this. Check other causes like permissionbukkit or spawn protection. Your debug is returning expected permission results.
     
  11. Offline

    Darkbanisher

    If you are sure that setup I tried is supposed to work. And the results indicate no errors. Then I will try one more thing.
    Let ya know if it works.
    EDIT: Alright it seems to work now for break / place.
    However 'craft' regardless of being false still seems to be allowing people to craft.
     
Thread Status:
Not open for further replies.

Share This Page