next »

[Miramar]

the FUD BINDKICKER for example can do a auto setup for enabling pbucon in a few seconds...
so this should not be the problem...

for the keybind checks my idea was to do it in two ways...
1. let it run automatically every x minutes...
and/or
2. start it per command !bindcheck (or something else) manually

[MordyT]

the FUD BINDKICKER for example can do a auto setup for enabling pbucon in a few seconds...
so this should not be the problem...

for the keybind checks my idea was to do it in two ways...
1. let it run automatically every x minutes...
and/or
2. start it per command !bindcheck (or something else) manually

As for keybinding check, we are not looking for keybinding, pb is. Therefor, we don't need to worry about the "how to check" issue or "how often to check". Leave that up to pb.
All the plugin would be doing is enforcing a ___ (notice, kick, tempban, ban) when it reads it in B3 logs.

There is 2 plugins here (or maybe more) that would be great to have.

1) A plugin to read/parse/store the pb logs.
2) A plugin to send (all?) rcon commands over ucon (can't flood ucon.. let the n00bs flood the rcon - pb web tool / power system uses ucon for this reason). You can send 100's of commands a second without issue (great for spam in cod4, I could issue 14 commands to take up al lines with my message, but then pb crashes out).
3) A plugin to enforce penalties for items in the pb log.

[Spoon]

ive looked at this and it could be done without pb ucon as long as you can get B3 to read the number.var files in pb\svlogs folder

[Courgette]

a B3 plugin could read those files I guess

[Miramar]

the manual to the antiscript-script thingy say you have to add these lines to the pbsvuser.cfg

pb_sv_task 1 20 pb_sv_cvarsrch +attack
pb_sv_task 2 20 pb_sv_cvarsrch -attack
pb_sv_task 3 20 pb_sv_cvarsrch +frag
pb_sv_task 4 20 pb_sv_cvarsrch +gostand
pb_sv_task 5 20 pb_sv_cvarsrch +melee
pb_sv_task 6 20 pb_sv_cvarsrch screenshot
pb_sv_task 7 20 pb_sv_cvarsrch wait
pb_sv_task 8 20 pb_sv_cvarsrch vstr
pb_sv_task 9 20 pb_sv_cvarsrch bind
pb_sv_task 10 20 pb_sv_bindsrch +attack
pb_sv_task 11 20 pb_sv_bindsrch -attack
pb_sv_task 12 20 pb_sv_bindsrch +frag
pb_sv_task 13 20 pb_sv_bindsrch +gostand
pb_sv_task 14 20 pb_sv_bindsrch +melee
pb_sv_task 15 20 pb_sv_bindsrch screenshot
pb_sv_task 16 20 pb_sv_bindsrch wait
pb_sv_task 17 20 pb_sv_bindsrch vstr
pb_sv_task 18 20 pb_sv_bindsrch com_maxfps
pb_sv_task 19 20 pb_sv_bindsrch rate
pb_sv_task 20 20 pb_sv_bindsrch exec
pb_sv_task 20 20 pb_sv_bindsrch bind

if it finds

Code:

KEY_MWHEELDOWN = +attack
KEY_MWHEELUP = +attack

for example then it warns/kicks the player because of the mousewheel shooting...


here is a part of the script which checks the pb logs

Code:

#!/bin/bash

grep -h "wait" /---COD4dir---/pb/svlogs/*.log > /---COD4dir---/pb/sp01.cfg

grep -h "KEY_MWHEELDOWN = +attack" /---COD4dir---/pb/svlogs/* >> /---COD4dir---/pb/sp01.cfg

grep -h "KEY_MWHEELUP = +attack" /---COD4dir---/pb/svlogs/*.log >> /---COD4dir---/pb/sp01.cfg

find . -name sp01.cfg -type f -exec sed '{/pb_sv_bindsrch/d}' {} \; > /---COD4dir---/pb/sp02.cfg

find . -name sp02.cfg -type f -exec sed '{/pb_sv_cvarsrch/d}' {} \; > /---COD4dir---/pb/sp03.cfg

find . -name sp03.cfg -type f -exec sed '{/wait = ""/d}' {} \; > /---COD4dir---/pb/sp04.cfg

find . -name sp04.cfg -type f -exec sed '{/PB Scheduled/d}' {} \; > /---COD4dir---/pb/sp05.cfg

find . -name sp05.cfg -type f -exec sed '{/pb_sv_SsCmd/d}' {} \; > /---COD4dir---/pb/sp06.cfg

find . -name sp06.cfg -type f -exec sed '{/pb_sv_sscmd/d}' {} \; > /---COD4dir---/pb/sp07.cfg

find . -name sp07.cfg -type f -exec sed '{/result/d}' {} \; > /---COD4dir---/pb/sp08.cfg

find . -name sp08.cfg -type f -exec sed '{/Issued/d}' {} \; > /---COD4dir---/pb/sp09.cfg

find . -name sp09.cfg -type f -exec sed -i '{s/;/:/g;}' {} \;

find . -name sp09.cfg -type f -exec sed -i '{s/[]]/ /g;}' {} \;

find . -name sp09.cfg -type f -exec sed '{/Command/d}' {} \; > /---COD4dir---/pb/sp10.cfg

find . -name sp10.cfg -type f -exec sed '{s/^.........................................../pb_sv_kick /}' {} \; > /---COD4dir---/pb/kicklist.cfg

find . -name sp10.cfg -type f -exec sed '{s/^.........................................../say /}' {} \; > /---COD4dir---/pb/saylist.cfg

sort /---COD4dir---/pb/kicklist.cfg | uniq  > /---COD4dir---/mods/pam/kickall.cfg

sort /---COD4dir---/pb/saylist.cfg | uniq  > /---COD4dir---/mods/pam/sayall.cfg

sleep 20

mv /---COD4dir---/pb/svlogs/* /---COD4dir---/pb/backup

[cluzzz]

Could you explain how does it work? I really need something to parse my PB logs containing cvars...

[Miramar]

it first deletes the pb logs... (moved to a backup folder) so it starts with a clean one...
then it searches for the unwanted variables... they are written in the new pb log
then it filters out everything which has nothing to do with the lines which include the found variables and the userdata
this data will be written in a cfg file which punkbuster can execute ingame to tell the players who is using the forbidden variables or to kick them instantly...

after that the pb log will be cleaned again (moved to a backup folder) to startover with a clean logfile at the next search...

[cluzzz]

Courgette are you going to work out any parser for PB logs? I would be very helpful and I would be very gratefull if you did it.

[KaGDeadz]

Just come across this topic and firstly

Anyone getting any futher with this?

Secondly
I like the sound of a lot of the ideas flying around but cant help but feel as if people dont think its actually possible

So do we still have it on a todo list?
or
Found a massive roadblock not allowing certain things communicate in the way we would like?

[MordyT]

It is possible, don't think anyone is working on it.

I guess we should put together a solid list of what would need to be done...