Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google Log In with Steam Sign In
  • Create Account
Photo

Identical PBGUID on bans

- - - - -

  • Please log in to reply
9 replies to this topic

#1
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
When reviewing our (short, only 3 bans) banlist, I realized that all bans are shown with the same PBGUID, but different Silent UID.

Is there a standard PB guid awarded to users without etkey or some other known issue that might cause this?

Or can I assume that they have all been playing with the same etkey?

Thanks :)

#2
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
Ok just noticed something else odd. When I banned a fourth user (using !userban and silent ID) the pbguid of the first changed to the same as the last ban.

PBGUIDS are not listed correctly in accordance with silent guid bans. Perhaps this should be moved to bugs?

Edited by fleshpulse, 21 January 2012 - 01:40 AM.


#3
OFFLINE   gaoesa

gaoesa

    Advanced Member

  • Management
  • PipPipPipPip
  • 4391 posts
341
Will become famous
  • LocationFinland
Thanks for reporting. There has been couple fixes made to the bans already. I'll check this one also.

#4
OFFLINE   gaoesa

gaoesa

    Advanced Member

  • Management
  • PipPipPipPip
  • 4391 posts
341
Will become famous
  • LocationFinland
The bug does not appear to happen on my server. There is a bug that with g_identOptions 16 (creating new bans automatically based on ident checks) does not handle the PB GUID correctly. Also the temp bans had a bug regarding the silent GUID.

#5
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
Will this also apply when I use !userban <silentID>? I can have the setting checked.

#6
OFFLINE   gaoesa

gaoesa

    Advanced Member

  • Management
  • PipPipPipPip
  • 4391 posts
341
Will become famous
  • LocationFinland
Do you have g_identOptions flag 16 set?

Forgot to mention one more bug introduced in 0.5.0. Because the ban checks were moved later in the 0.5.0. The g_identOptions 16 was autocreating bans even when the player was already getting dropped otherwise.

After disabling the temporary bans (g_tempbans) and removing the g_identOptions flag 16 there hasn't been any problems with the bans.

#7
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
Thanks. Will look into this and reply. Great response :)

#8
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
g_identOptions is not set.

It appears we figured it out though. The bans were added with console and it copied the PBguid from earlier bans. Set ingame the pbguid is correctly displayed as invalid.

#9
OFFLINE   gaoesa

gaoesa

    Advanced Member

  • Management
  • PipPipPipPip
  • 4391 posts
341
Will become famous
  • LocationFinland
Sounds like the bug is/was in !showbans command. Is that the way you checked the bans after adding?

#10
OFFLINE   fleshpulse

fleshpulse

    Newbie

  • Members
  • Pip
  • 12 posts
0
Unknown
Yes, this was checked using showbans.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users