next »

[lemekill]

At the beginning of a round, the bot will say "Please, No nades, airstrike, tubes !!!".

Now that's not exactly what I have it doing on my server. I changed the banned only info message, which is what that is, in antinoob.xml. I checked antinoob.py and the same message is there, when I tried changing that, the plugin crashed.

I need to either stop that message, or edit it to show "Please, don't use Noob Tubes.", as I edited it in the xml.

[MordyT]

So, after you made changes to the antinoob.xml, you restarted the bot and it had the same message?

Can you post your antinoob.xml and your b3.log

[lemekill]

So, after you made changes to the antinoob.xml, you restarted the bot and it had the same message?

Can you post your antinoob.xml and your b3.log

Indeed. And it seems as I said, the message is only displayed at the beginning of a round. So for games such as Search and Destroy, this message is displayed quite often. Since the message isn't accurate... Yeah.

Logs, etc...:
b3.log http://www.pastie.org/2252241
antinoob.xml http://www.pastie.org/2252261
My console_mp.log excerpt, which occurred after a fresh restart of the server.
I also noticed there's a lot of unnecessary code in antinoob.xml, I simply haven't cleaned it up since I fully tested and employed the plugin. As you can see I changed the info message in the xml, to no effect. And since the info message supersedes (priority="9") all other b3 messages, it's always the first message shown at the beginning of the round.

"Line 4691: [     12603] handled rcon: say ^0(^2b3^0)^7: ^3 Please, No nades, airstrike, tubes !!!"
"Line 6206: [    644732] handled rcon: say ^0(^2b3^0)^7: ^3 Please, No nades, airstrike, tubes !!!"

[MordyT]

Something looks funny.
Can you post your antinoob.py please?

[lemekill]

Something looks funny.
Can you post your antinoob.py please?

I tried once to change the info messages in antinoob.py, to reflect the changes I made in antinoob.xml, but that caused a crash. So I reverted to the original .py.

Antinoob.py
http://www.pastie.org/2255479

[MordyT]

That is a VERY old .py file.

Download a copy from here and just replace the .py:

http://www.host4b3.com/client/dl.php?type=d&id=7

That should be version 1.0.8 instead of 1.0.5

[lemekill]

That is a VERY old .py file.

Download a copy from here and just replace the .py:

http://www.host4b3.com/client/dl.php?type=d&id=7

That should be version 1.0.8 instead of 1.0.5

Edit:
I finally got that link to resolve, thank you. I pasted the new .py and am testing to see if it still displays the info message...

Edit2:
It seems that worked, so far I do not see that info message at the beginning of a round. I will continue to monitor my logs to make sure. The info messages, I believe, should only be displayed in the event of a rule violation or kick, so it seemed odd it was still being displayed at round start.

Thanks again, Morty.

[MordyT]

No problem. Enjoy and let us know if it happens again

[lemekill]

No problem. Enjoy and let us know if it happens again

After some monitoring and feedback from the clan, it seems not only did the messages stop, so did the plugin. I'm going to tinker with it a bit, use both updated antinoob.py/and .xml. Though I will mention I gave that a quick test, and that caused b3 to crash altogether.

If I can't resolve this, I'll upload a running log with the updated files... See if we can identify the problems.

Edit:

Plugin loaded fine this time with the updated .py and xml. files. I copied over my list of banned weapons from the old antinoob.xml to the new one. I'll have to wait until I either see some auto-kicks in Echelon, or I get some feedback from my testers.

Edit:

After testing with a clan member, I found that no warnings were being issued for the weapons specified. Here's the config I used in antinoob.xml.
http://www.pastie.org/2279106

Everything launched and loaded properly. I even checked b3.log for the 2 instances where he killed me with an RPG and a Thumper, which were there. I'm using the xml and py in the zip from the link you provided.

Here's the log:
http://www.pastie.org/2279147

[MordyT]

I am not seeing any kills in the log you posted....

[lemekill]

I am not seeing any kills in the log you posted....

Sorry, pasted the wrong logfile, I had like 4 open looking for the right one.
Here's one, line 692 he got me with the Thumper.
http://www.pastie.org/2282039

[MordyT]

Pastie keeps cutting it off.
Try pastebin

[lemekill]

Pastie keeps cutting it off.
Try pastebin

Well Mordy, nevermind the log. I searched it thoroughly, and found that the kills were being registered with the appropriate checks, but no warnings were made. I saw all the instances, and I can assure you if you were to run a test with this plugin version using the settings I posted up there, you would find the same end result, no penalties.

That tells me either something is wrong with the version language, or my settings are screwed up. Since I can't verify anybody's successfully running the version with positive results, I have to assume it's the version language, since I followed the syntax verbatim.

A simple "MOD_GRENADE_SPLASH" with a restricted weapon should register a penalty, it does not. Even whereas one is not using a grenade weapon and simply using a rocket weapon like RPG or AT4, no "MOD_..." is necessary since any "kill" with "AT4 or RPG" wouldn't need a specific "MOD_...".

The fact is, I'm successfully using an "outdated" version made for CoD4, that spams an unnecessary message, whereas the "current" version doesn't work at all. All logic indicates either my settings are wrong, or the version is screwed up.

[MordyT]

Here is a copy of the .py I am using and the .xml

Modify and test please?

[lemekill]

Here is a copy of the .py I am using and the .xml

Modify and test please?

Indeed. I will employ this version, and have my testers report back with their findings, as well as my logs in Echelon.

We'll see soon enough.

Thank you.