1. Wulf

    Wulf Community Admin

    Which Oxide build?
     
  2. Happening for me on the latest Oxide build.
     
  3. Wulf

    Wulf Community Admin

    And what is the latest build to you?
     
  4. Perhaps the latest one you've released? .3105?

    I kinda thought you'd know your own releases...
     
  5. Wulf

    Wulf Community Admin

    There are newer builds than that... which is why I was asking. We have more than releases. ;)
     
  6. Yes, but your commits on Github seem to show nothing has changed to fix the issue at hand, which is why I didn't bother trying any other than the newest 'official' release.
     
  7. Wulf

    Wulf Community Admin

    When I ask which build, it helps to know the exact build number; "latest" is not a build, regardless if you feel it necessary or not. We can't help you if you can't help us. Details matter when reporting issues.
     
  8. I understand that, I do apologize for using "latest", I used it because from what I saw there were no changes (committed to Github, that is) made since that release which made me think it was pointless to give the exact version.

    If I'm not mistaken, there's no point in me trying a non-release build, right? Unless there are changes made to builds that are not committed?
     
  9. Wulf

    Wulf Community Admin

    I never said to try the latest build, I simply asked for the actual build, not "latest". There have been numerous times where a user was not using the "latest" release even, so in the future please be detailed when reporting.
     
  10. I want to apologize if I'm seeming rude, it's really not my intent, just a long and annoying day. To put it quite simply, the issue is still occurring with .3105. :)
     
  11. Wulf

    Wulf Community Admin

    No worries, just trying to figure out why I can't reproduce the issue locally with fresh or existing installs and data.

    @Austinv900, could you give me the specific line with how you are checking for it?
     
  12. One thing I'm not sure if anyone mentioned; I'm pretty sure it only occurs on players who are offline, or perhaps even offline and dead.
     
  13. Wulf

    Wulf Community Admin

    The IsAdmin checks I've seen so far are with users connecting in CanUserLogin, which is before an IPlayer is setup, but my Whitelist plugin accounts for that with player != null, though I'm not sure why some would still get it as I've tested the heck out of it and never got it.

    As far as the IsBanned check goes, it may be a similar thing, but should still be accounted for. I haven't been able to reproduce this in any of my universal plugins either, not even EBS yet.