A ban-flinging QoL update

Sabotages the exploitable ban-dodging mob-lock "feature" of the ban system. Like dude we're banning a client, not a mob so shut up and let us work.
This commit is contained in:
Verkister
2020-01-26 13:06:26 +02:00
committed by GitHub
parent 4505684fbd
commit 1392f268ec

View File

@@ -51,8 +51,8 @@ datum/admins/proc/DB_ban_record(var/bantype, var/mob/banned_mob, var/duration =
validckey = 1
if(!validckey)
if(!banned_mob || (banned_mob && !IsGuestKey(banned_mob.key)))
message_admins("<font color='red'>[key_name_admin(usr)] attempted to ban [ckey], but [ckey] has not been seen yet. Please only ban actual players.</font>",1)
return
message_admins("<font color='red'>The validmob system attempted to block [key_name_admin(usr)] from banning [ckey], but the devs jammed a screwdriver into its workings. Please ban whomever deserves it.</font>",1) //VOREStation Edit
//return //VOREStation Edit
var/a_ckey
var/a_computerid