Not Allowing OP's To Place Blocks #35

  • New
  • Defect
Open
Assigned to
View AxelDios's Profile
axeldios
  • View SoftwareDev's Profile
    SoftwareDev created this issue Jan 30, 2013

    What steps will reproduce the problem?
    1. Being an OP
    2. OR having the protectionstones.superowner permission
    3. OR having a group assigned to you that has a 100 block limit (also gave perms)

    What is the expected output? What do you see instead?
    I was expected to be able to place the stone. (tried all 3 I specified in Config)

    What version of the product are you using?
    R: ProtectionStones 1.8j for CB 1.4.7-R0.1 Jan 23, 2013

    Do you have an error log of what happened?
    No error logs were recorded.

    Please provide any additional information below.
    When attempting to place the block, I had OP, and the  - '*' permission node.
    I was trying this outside of a protected region, and outside of an existing Protection Stones region.

  • View SoftwareDev's Profile
    SoftwareDev     added the tags New Defect Jan 30, 2013
  • View AxelDios's Profile
    AxelDios posted a comment Feb 7, 2013

    First of all the "protectionstones.superowner" permission only effects some commands on existing regions, has nothing to do with placing new PS's.

    As far as the other issues sounds like a configuration problem in your group assignments, can you post your config.yml so I can take a look at it?

To post a comment, please login or register a new account.