In our support boards we aim to provide support for the B3 core in its current state. Older releases of B3 are NOT supported. Check our front page for the latest version. You may post feature requests in our General Discussion board. Modifications and Hacks of the core B3 code are NOT supported.
Before you ask for support: [ Read the Support Instructions ] - More info: [ Full Support Disclaimer ]

You are here: Big Brother Bot ForumSupport ForumsGeneral Usage Support (Moderator: MordyT)Command could not be processed, but it was...
Pages: [1]   Go Down
  Print  
Author Topic: Command could not be processed, but it was...  (Read 326 times) Bookmark and Share
Beta Testers
*
OS: Windows
Type: Owner dedicated server(s)
Gameservers: alterIW
Posts: 652
Offline Offline
WWW
« on: December 19, 2011, 06:12:59 PM »

I recently put my MW2 servers back online and I've noticed that when I kick someone, it's saying that the command could not be processed, but they are kicked.

Here's a section of my b3.log that shows the kick:

Code:
111219 17:37:31 CONSOLE '1432:01 say;0110000100009792;3;GrossKopf;\x15!kick ipav afk'
111219 17:37:31 VERBOSE 'Queueing event Say !kick ipav afk'
111219 17:37:31 VERBOSE 'Parsing Event: Say: AdminPlugin'
111219 17:37:31 DEBUG 'AdminPlugin: OnSay handle 5:"!kick ipav afk"'
111219 17:37:31 DEBUG 'AdminPlugin: Handle command !kick ipav afk'
111219 17:37:31 VERBOSE "RCON sending (204.93.166.244:28970) 'clientkick 7'"
111219 17:37:31 CONSOLE '1432:01 K;011000010002c0d5;14;allies;Irisas;011000010002c33c;13;axis;SirTheRev;usp_mp;40;MOD_PISTOL_BULLET;torso_lower'
111219 17:37:31 VERBOSE "Queueing event Client Kill (40.0, 'usp_mp', 'torso_lower', 'MOD_PISTOL_BULLET')"
111219 17:37:31 CONSOLE '1432:01 Q;011000010002a3c2;7;ipavkex'
111219 17:37:31 VERBOSE 'Queueing event Client Disconnect 7'

This was a few lines farther down:

Code:
111219 17:37:32 ERROR 'handler AdminPlugin could not handle event Say: TypeError: not enough arguments for format string [(\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\parser.py\', 973, \'handleEvents\', \'hfunc.parseEvent(event)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugin.py\', 158, \'parseEvent\', \'self.onEvent(event)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugin.py\', 176, \'onEvent\', \'self.handle(event)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugins\\\\admin.py\', 223, \'handle\', \'self.OnSay(event)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugins\\\\admin.py\', 368, \'OnSay\', \'results = command.execute(data, event.client)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugins\\\\admin.py\', 2002, \'execute\', \'self.func(data, client, copy.copy(self))\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\plugins\\\\admin.py\', 1192, \'cmd_kick\', \'sclient.kick(reason, keyword, client)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\clients.py\', 492, \'kick\', \'self.console.kick(self, reason, admin, silent)\'), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\parsers\\\\q3a\\\\abstractParser.py\', 468, \'kick\', "fullreason = self.getMessage(\'kicked_by\', self.getMessageVariables(client=client, reason=reason, admin=admin))"), (\'C:\\\\b3\\\\b3_dmc_aiw2\\\\b3\\\\parser.py\', 765, \'getMessage\', \'return msg % args[0]\')]'

The b3.xml is around 9 MB so I can't attach it and if needed, I can delete the log and run a test when the server isn't full so there aren't so many other messages being processed.

Something else I've noticed is that admin kicks and auto kicks (like for high ping) are not being displayed in Echelon.

Any ideas?
« Last Edit: December 19, 2011, 08:46:55 PM by GrossKopf » Logged

Senior Dev.
*
OS: Linux
Type: Home user
Posts: 3483
Offline Offline
WWW
Support Specialty: B3-Core, UrT/SmG/BFBC2 parsers, Plugin development
« Reply #1 on: December 20, 2011, 04:47:42 AM »

check your b3.xml, the kicked_by message might be incorrect, it must have the 3 $clientname, $adminname $reason variables
« Last Edit: December 20, 2011, 04:54:33 AM by Courgette » Logged

Beta Testers
*
OS: Windows
Type: Owner dedicated server(s)
Gameservers: alterIW
Posts: 652
Offline Offline
WWW
« Reply #2 on: December 20, 2011, 05:44:31 AM »

check your b3.xml, the kicked_by message might be incorrect, it must have the 3 $clientname, $adminname $reason variables

I don't see anything wrong with the b3.xml. It's the stock b3.xml modified:

Code:
<configuration>
<!--
 If you want to generate a new config file and make sure the format is
 correct, you can invoke the setup procedure with the
 command : b3_run -s b3.xml

 This is B3 main config file (the one you specify when you run B3 with the
 command : b3_run -c b3.xml)

 For any change made in this config file, you have to restart the bot.
 Whenever you can specify a file/directory path, the following shortcuts
 can be used :
  @b3 : the folder where B3 code is installed in
  @conf : the folder containing this config file
 -->
<settings name="b3">
<!--
Next line: the parser defines the game:
cod/cod2/cod4/cod5/iourt41/etpro/wop/smg/smg11/bfbc2/oa081 (it should NOT be 'changeme')
-->
<set name="parser">cod6</set>
<!-- Your database info: [mysql]://[db-user]:[db-password]@[db-server[:port]]/[db-name] -->
<set name="database">mysql://db_user:db_password@webserver IP/db_name</set>
<!-- Name of the bot -->
<set name="bot_name">b3</set>
<!-- Ingame messages are prefixed with this code, you can use colorcodes -->
<set name="bot_prefix">^0(^2b3^0)^7:</set>
<set name="time_format">%I:%M%p %Z %m/%d/%y</set>
<!-- The timezone your bot is in -->
<set name="time_zone">CST</set>
<!-- How much detail in the b3 logfile: 9 = verbose, 10 = debug, 21 = bot, 22 = console -->
<set name="log_level">9</set>
<!-- Name of the logfile the bot will generate -->
<set name="logfile">b3.log</set>
</settings>
<settings name="server">
<!-- The RCON pass of your gameserver -->
<set name="rcon_password">rcon_password</set>
<!-- The port the server is running on -->
<set name="port">28971</set>
<!-- The gameserver generates a logfile, put the path and name here (very important !) -->
<set name="game_log">c:/servers/qczm_aiw2/m2demo/games_mp.log</set>
<!-- If you want to run b3 on a different computer than where your server reside (remote access to the gamelog), you can connect via ftp or http by using the following syntax:
<set name="game_log">ftp://username:password@serverhost/path/to/games_mp.log</set>
<set name="game_log">http://serverhost/path/to/games_mp.log</set>
Note: you can protect your http access with a .htaccess, b3 can authenticate itself.
-->
<!-- The public IP your gameserver is residing on -->
<set name="public_ip">204.93.166.244</set>
<!-- The IP the bot can use to send RCON commands to (127.0.0.1 when on the same box) -->
<set name="rcon_ip">204.93.166.244</set>
<!-- Is the gameserver running PunkBuster Anticheat: on/off -->
<set name="punkbuster">off</set>
<!-- Delay between each log reading. Set a higher value to consume less disk ressources or bandwidth if you remotely connect (ftp or http remote log access) -->
<set name="delay">0.05</set>
<!-- Number of lines to process per second. Set a lower value to consume less CPU ressources -->
<set name="lines_per_second">1000</set>
</settings>
<settings name="autodoc">
<!-- Autodoc will generate a user documentation for all B3 commands
* type : can be one of : html, htmltable, xml
* maxlevel : if you want to exclude commands reserved for higher levels
* destination : can be a file or a ftp url
by default, a html documentation is created in your conf folder
-->
<set name="type">html</set>
<set name="maxlevel">100</set>
<!-- <set name="destination">C:\Users\b3\Desktop\test_doc.htm</set> -->
<!-- <set name="destination">ftp://user:pass@somewhere.com/www/test_doc.htm</set> -->
</settings>
<settings name="messages">
<set name="kicked_by">%s^7 was kicked by %s^7 %s</set>
<set name="kicked">%s^7 was kicked %s</set>
<set name="banned_by">%s^7 was banned by %s^7 %s</set>
<set name="banned">%s^7 was banned %s</set>
<set name="temp_banned_by">%s^7 was temp banned by %s^7 for %s^7 %s</set>
<set name="temp_banned">%s^7 was temp banned for %s^7 %s</set>
<set name="unbanned_by">%s^7 was un-banned by %s^7 %s</set>
<set name="unbanned">%s^7 was un-banned %s</set>
</settings>
<settings name="plugins">
<set name="external_dir">@b3/extplugins</set>
</settings>
<plugins>
<!-- plugin order is important. Plugins that add new in-game commands all
depend on the admin plugin. Make sure to have the admin plugin before
them. -->
<plugin name="admin" config="@conf/plugin_admin.xml" />
<!-- <plugin name="censor" config="@conf/plugin_censor.xml" /> -->
<!-- <plugin name="spamcontrol" config="@conf/plugin_spamcontrol.xml" /> -->
<!-- <plugin name="tk" config="@conf/plugin_tk.xml" /> -->
<plugin name="stats" config="@conf/plugin_stats.xml" />
<plugin name="pingwatch" config="@conf/plugin_pingwatch.xml" />
<plugin name="adv" config="@conf/plugin_adv.xml" />
<plugin name="pingkicker" config="@b3/extplugins/conf/plugin_pingkicker.xml"/>
<plugin name="status" config="@conf/plugin_status.xml" />
<plugin name="ctime" config="@b3/extplugins/conf/plugin_ctime.xml"/>
<plugin name="xlrstats" config="@b3/extplugins/conf/xlrstats.xml"/>
<plugin name="makeroom" config="@b3/extplugins/conf/plugin_makeroom.xml"/>
<!-- <plugin name="rotationmanager" config="@b3/extplugins/conf/rotationmanager.xml"/> -->
<!-- <plugin name="b3twitter" config="@b3/extplugins/conf/b3twitter.xml"/> -->
<!-- <plugin name="welcome" config="@conf/plugin_welcome.xml" /> -->
<!-- <plugin name="punkbuster" config="@conf/plugin_punkbuster.xml" /> -->

<!-- The next plugins are external, 3rd party plugins and should reside in the external_dir. Example: -->
<!-- plugin config="@b3/extplugins/conf/newplugin.xml" name="newplugin" -->

<!-- You can add new/custom plugins to this list using the same form as above. -->

<!--
This is a non-standard plugin, and quite resource heavy. Please take
a look in the B3 forums (look for XLR Extensions) for more
information before enabling this. Extra database tables are
necessary.
<plugin name="xlrstats" config="@b3/extplugins/conf/xlrstats.xml"/>
-->

<!-- You can find many others plugin for B3 which can extend functionalities a lot !
Please take a look at the official website for more informations. -->
</plugins>
</configuration>
Logged
Senior Dev.
*
OS: Linux
Type: Home user
Posts: 3483
Offline Offline
WWW
Support Specialty: B3-Core, UrT/SmG/BFBC2 parsers, Plugin development
« Reply #3 on: December 20, 2011, 05:48:53 AM »

the messages block is in a old unsupported format. See how it looks since B3 1.5 : https://github.com/BigBrotherBot/big-brother-bot/blob/master/b3/conf/b3.distribution.xml#L71
Logged

Beta Testers
*
OS: Windows
Type: Owner dedicated server(s)
Gameservers: alterIW
Posts: 652
Offline Offline
WWW
« Reply #4 on: December 20, 2011, 05:55:18 AM »

the messages block is in a old unsupported format. See how it looks since B3 1.5 : https://github.com/BigBrotherBot/big-brother-bot/blob/master/b3/conf/b3.distribution.xml#L71

I am running 1.7.1. It's a fresh install as of 2 weeks ago. I'm not using an old b3.xml. Is the old format in that b3.xml that I attached?

*edit* I replaced that section in the b3.xml. Odd that an old version of the b3.xml would be distributed with 1.7.1 though.
« Last Edit: December 20, 2011, 06:00:23 AM by GrossKopf » Logged
Senior Dev.
*
OS: Linux
Type: Home user
Posts: 3483
Offline Offline
WWW
Support Specialty: B3-Core, UrT/SmG/BFBC2 parsers, Plugin development
« Reply #5 on: December 20, 2011, 06:33:08 AM »

I'm curious : from where did you download the 1.7.1 package you used ?

I went through all 1.7.1 distributions hosted on sourceforge plus the bigbrotherbot github and none has the old messages format
Logged

Beta Testers
*
OS: Windows
Type: Owner dedicated server(s)
Gameservers: alterIW
Posts: 652
Offline Offline
WWW
« Reply #6 on: December 20, 2011, 08:57:53 AM »

I know I got B3 from here, but I can't say for sure if the b3.xml was with it now. Maybe I got that someplace else, I don't really remember. In any case, it's fixed. I just tested it. Thanks for the excellent support, as usual! Smiley
Logged
Tags:
Pages: [1]   Go Up
  Print  
 
Jump to:  


Rate this page +1 at Google Search


SimplePortal 2.3.1 © 2008-2009, SimplePortal