Trouble in Terrorist Town - a GMod gamemode

[Bad King Urgrain]

Time to stop talking about people's age!

edit: Seriously, all posts on the topic from this point on will be deleted.

[Rectal Exambot]

Anyone else when traitor have the violent urge to go poltergesit + kevlar + HUGE and see how many people they can get?

[Sly]

Anyone else when traitor have the violent urge to go poltergesit + kevlar + HUGE and see how many people they can get?

Statistically, 90% of my poltergeist shots result in a dead traitor buddy. So no, not really.

[StormX]

Just made my second last words exploit. Sadly I don't think it can be fixed.
ill post more info later

[Raneman]

I spawned invisible to everyone, anyone know why that might be?

[Rectal Exambot]

I spawned invisible to everyone, anyone know why that might be?

Happens every once in a while, I can only put it down to source glitches (I no nozing!)

[Bad King Urgrain]

Just made my second last words exploit. Sadly I don't think it can be fixed.
ill post more info later

If you let me know ASAP I can look at it before releasing v20.

[JoTheShmo]

Garry said he won't be updating Gmod for a while because he will be going on vacation soon, and doesn't want anything to break.
You should have a while to work on v20.

[Bad King Urgrain]

I'm doing at least one .zip release in the meantime.

[StormX]

I'm doing at least one .zip release in the meantime.

ill wait on it, since i still am going through code, and ive already made a confirm body hack too, i only think there is one more thing that you can hack though, give me a day

[JoTheShmo]

I changed my name as a joke to get banned, but apparently it printed my second name in chat saying I left the game.
I thought it was supposed to avoid that.

[StormX]

I changed my name as a joke to get banned, but apparently it printed my second name in chat saying I left the game.
I thought it was supposed to avoid that.

nope
bku: right now i have a working identify any body on the map, to do a fix on CORPSE.ShowSearch send a curtime + math.random in a usermessage so you can't just grab the id. because all you have to do right now is just loop through all ragdolls, get the eidx and then add on the death time. putting this into a usermessage in CORPSE.ShowSearch will make it 99% secure. theres only one way to get the usermessage is looking at the corpse, but theres still ways to remotely look at the corpse and get the umsg(hooking and returning the ent you want).
ill think up a fix for the last words exploit sometime
sorry for the shit grammar, late at night

[Bad King Urgrain]

nope
bku: right now i have a working identify any body on the map, to do a fix on CORPSE.ShowSearch send a curtime + math.random in a usermessage so you can't just grab the id. because all you have to do right now is just loop through all ragdolls, get the eidx and then add on the death time. putting this into a usermessage in CORPSE.ShowSearch will make it 99% secure. theres only one way to get the usermessage is looking at the corpse, but theres still ways to remotely look at the corpse and get the umsg(hooking and returning the ent you want).
ill think up a fix for the last words exploit sometime
sorry for the shit grammar, late at night

Are you certain that works? You need to pass a serverside check of ply.search_id when using the identify concommand, which is only set by the server when you search a body and is keyed to the eidx and death time of that body. You can spam the concommand with other ragdoll eidx and death times (which you'd have to guess, client does not know death time for all ragdolls), but you won't get past that check. Unless there's a bug in it, of course.

If anything the problem was that there was no distance check, I fixed that last night.

(Of course, if you run an SE bypass you can easily run aimhacks and other such things, I'm not sure identifying bodies is going to be the main problem there. Not that I don't appreciate you looking into these things.)

[Raneman]

Could you do something to prevent bodies and scoreboards from being screwed up? I always lose important information because people ragequit. Maybe replace them with placeholder bots until the round ends.

[StormX]

Are you certain that works? You need to pass a serverside check of ply.search_id when using the identify concommand, which is only set by the server when you search a body and is keyed to the eidx and death time of that body. You can spam the concommand with other ragdoll eidx and death times (which you'd have to guess, client does not know death time for all ragdolls), but you won't get past that check. Unless there's a bug in it, of course.

If anything the problem was that there was no distance check, I fixed that last night.

(Of course, if you run an SE bypass you can easily run aimhacks and other such things, I'm not sure identifying bodies is going to be the main problem there. Not that I don't appreciate you looking into these things.)

I am certain it works. Think of it this way BKU: I have a timer activating the function that identifies players every 10 seconds. It will do ents.GetAll() and find all ragdolls not identified. So to get the search_id you would only have to guess the death time upto ten. Or an even simpler method of logging all players death times for wanting to ident corpses at certain times. but the distance should fix it

[Bad King Urgrain]

Could you do something to prevent bodies and scoreboards from being screwed up? I always lose important information because people ragequit. Maybe replace them with placeholder bots until the round ends.

What do you mean by "screwed up"?

I see how it works now, you can make an old search_id work with a different eidx as long as you adjust the death time correctly. I can fix that more fundamentally by storing and checking the eidx separately besides the id. This should make it impossible to use the identify cmd for any corpse that you did not just search even if you get the id right.

[StormX]

What do you mean by "screwed up"?
I see how it works now, you can make an old search_id work with a different eidx as long as you adjust the death time correctly. I can fix that more fundamentally by storing and checking the eidx separately besides the id. This should make it impossible to use the identify cmd for any corpse that you did not just search even if you get the id right.

The last words exploit cannot be fixed. Unless you can find a way where the client doesn't know the last_words_id.

[Raneman]

Well, I don't know how many players were in the game, I lose evidence, I lose the number of traitors and innocents dead, and for my playstyle that usually ends in false positives and innocents getting killed.

[Bad King Urgrain]

The last words exploit cannot be fixed. Unless you can find a way where the client doesn't know the last_words_id.

We'll see. I don't know what it is yet.

[Bad King Urgrain]

Just pushed a few changes into the SVN. Besides fixes for the exploit discussed here, there's now a ttt_ragdoll_pinning_innocents convar that allows non-traitors to hang corpses.

Let me know if you run this version on your server. If no bugs turn up after a day or two I'll release v20 as .zip.