Bperms opping issue #743

  • Defect
  • Accepted
Assigned to vladtobehere
  • _ForgeUser8340299 created this issue Nov 7, 2016

    Describe to us the issue that you're having:
    Bperms has been known to op users due to conflicts and errors. This happened once in the past but it seems to have happened again. I believe what's happening is that a plugin such as command signs/magicspells or likely any other plugin which uses a "temporary-op" feature can result in this. It has only happened when bperms/the server crashes from other issues such as in my previous report. So it seems that a user is put into the "temporary op" state, bperms errors/server crashes and then the user is left in this state.

    Which steps will reproduce this problem?:
    1) Have bperms and have some sort of error.
    2) A user who was using another plugins temporary op feature will stay op on crash.

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

    Which version of bPermissions are you using?: (Please don't say "latest"!!!)

    Which version of CraftBukkit?: (Please don't say "latest"!!!)
    MC 1.10.2-R0.1 Spigot

    Which OS?
    Cent OS

    Any other information we may need (plugins, configs, etc):

    Please fill out this form properly! Failing to do so may result in your ticket being marked invalid.

  • _ForgeUser8340299 added the tags New Defect Nov 7, 2016
  • rymate1234 posted a comment Nov 8, 2016

    bPermissions changes nothing about the default OP behaviour. Even when using a custom bPermissible, bPermissions uses the bukkit OP behaviour rather than any custom behaviour. There's additionally no code in bPermissions that OPs users. If users are staying opped after a server crash, then that's an issue with the temporary-op feature of that plugin not properly handling unexpected server restarts / crashes.

  • rymate1234 removed a tag New Nov 8, 2016
  • rymate1234 added a tag Verified Nov 8, 2016
  • rymate1234 closed issue Nov 8, 2016
  • rymate1234 removed a tag Verified Nov 8, 2016
  • rymate1234 added a tag Accepted Nov 8, 2016
  • rymate1234 reopened issue Nov 8, 2016
  • _ForgeUser8340299 posted a comment Nov 8, 2016

    @rymate1234: Go

    This error has only ever occurred simultaneously when bperms has been the result of a crash. I'll attempt to recreate it when I get the chance, but my assumption is the plugins are passing off the temporary op to bperms and then the crash leaves them in that state.

    As you said though nothing clear in bperms could cause this issue. I'm quiet confident that it is somehow related though as I've ran these plugins for years before bperms and the issue has only ever occurred when bperms was enabled and the cause of a crash.

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