BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Age of Conan Archive => AoC 0.6 support => Topic started by: Rekkx on June 23, 2009, 11:30:20 pm
-
It seems that with the new patch arriving imminently, Funcom has altered the way the client authenticates with the user to maintain the session.
Instead of how it does things currently, it uses some sort of 4 byte ID for the session.
This development will render all AoC bots offline after the next patch.
I have no clue where to start to remedy this event, as I admit, I do not have the skill. Can we as a community try and solve this issue if at all possible?
-
Just /signed a post on Funcom's Test Live forum that was talking about this, totally unacceptable and makes me pretty pissed off...
Brutalisk
-
Just /signed a post on Funcom's Test Live forum that was talking about this, totally unacceptable and makes me pretty pissed off...
Brutalisk
Funcom has absolutely no obligation to support bots.
We're lucky they're allowed to begin with.
That said, someone will eventually fix and update the bots. Patience is virtue.
Unless FC intends to use this to get rid of bots, then there won't be an update and that's it.
-
Well I certainly hope there will be a fix. Thanks Guys.
-
There is an official Post by some Game Director in the Age of Conan Forum that sounds good:
Game Director Silirrion:
While strictly speaking the chatbots are an external development having chatted to one of the bot developers, I believe there will be updates available sometime this evening or tomorrow that allows the chatbots to work with our new protocols. I'll have the community guys post a link as and when it appears.
Source: http://forums-eu.ageofconan.com/showpost.php?p=1339253&postcount=5 (http://forums-eu.ageofconan.com/showpost.php?p=1339253&postcount=5)
-
Funcom has absolutely no obligation to support bots.
We're lucky they're allowed to begin with.
True, not saying that does not make it more acceptable in any way for a community driven game to not keep us updated on changes they do that affect their customers, that being official standard game mechanics or more advanced ones like this...
Anyway good news from the game director I looks like, did he speak to any of you bebot guys?
-
yeah looks promising I just hope it's sooner rather than later....
-
The AoC gameclient does not support private chatgroups, so all bots have to be guild based.
maybe this could be fixed too ;)
-
Well we can dream about it, maybe with 1.6 when they claim to look into guilds and social stuff that can extend to think a bit outside the box as well :)
-
I wonder if this means that funcom will also finally be banning the cheaters too? At least a sweet good thing can come out of the downside. :) WooT!
-
Cheaters? ChatBot's? I dont see any link here. Anyhow....
The Director said they will explain the BeBot Devs how to use the new chat protocol. And the Devs probably already know how to fix and are busy creating a new login library for the Bot's.
Lets wait for an official post from the devs here for more info.
-
http://www.conanchat.com/
seems like they have found a way to stay connected.
-
Let's hope we can find a resolution to this issue, with or without Funcom's help.
Has anyone looked into the Conan Chat sources yet?
Off-topic: Now is your chance to level up your bots while they're offline, mine is a Necro at lvl 80 ;)
-
Even if they will modify the chat protocols to allow bots again, it will be probably up to bebot AoC community to adapt IT, I DOUBT ANY OF THE bebot DEV'S will do it, simply because as they stated in other threads the ppl who helped making bebot possible for AoC are gone.
I sincerely hope I'm wrong, if I'm not we got work to do. ::)
-
People are trying it seems: http://forums-eu.ageofconan.com/showpost.php?p=1342283&postcount=17
Let's give encouragement and support where we can. We all want the same thing after all :)
-
Yes I hope this gets Fixed, Hoping someone knows how to make a new Item Database too lol
-
I have a working submitt itembase.
And if there will be to much problem with using the old one it is a solution starting over again.
But lets see first, as the item is not stored in DB with stats but only referanse (Name,level,id,link,color)
-
could we get some kind of confirmation that there are someone actually working on a fix for this?
Right now it's not really any info if someone is on it or not
-
No. nobody is on it. not any of the bebot devs are on it anyhow if thats what you want to know.
FunCom is changing its protocol soon. So why should anyone even bother at the moment to go start coding if FunCom is going to change it again ?
Hope that clarifies your question.
-
Where did you found out that FC is chancing again?
-
That's what I understood from the game director's message towards the community.
-
I've not seen anything on that, the game directors note was more in the direction of the fact that it will be possible to program and get it to work with the new protocols they got, not that they would change anything...
But I've not been following it that close so maybe you are right, but not seen such a post or hint myself at least...
-
I wrote the code for the conanchat login (both old and new) and i can help if anyone has any questions about the protocol. Since the guild im in doesnt use bebot yet im not sure ill have time to fix the login myself. But ill answer any PMs you send on this forum.
-
I was just hoping that one of the dev's could fix the bebot.... we all miss it.
-
sry for the question ... but is there now any workaround for getting the bots running ??
-
sry for the question ... but is there now any workaround for getting the bots running ??
Not yet I'm afraid, but soon I hope.
http://bebot.link/bebot-0-6-support/aoc-patch-1-05-login-information/15/
-
I'm itching to get my bot back up.
News from Chaoz here:
http://forums-eu.ageofconan.com/showpost.php?p=1351519&postcount=49
Can't be long now...
-
He made it, works fine with 0.6.3 also
http://forums-eu.ageofconan.com/showthread.php?t=125128&page=6
thnx to Chaoz.
-
Works, but:
- only on Windows
- disconects when 1st person say anything on guild channel
- ppl report problems when loging on a charater from account the bot is on.
So good job, but still need more work.
-
Yeah, running on CentOS so having issues, trying to understand the packet thing but with zero experience in linux and just simple php experience I don't think I will get anywhere...
If someone can correct the packets stuff for linux support and post the file it would be great.
-
works fine here...he can't emulate hundreds of setups and custom mods that some of us are running, so far works, from what I was reading in console ppl are chatting and using bot functions without issues.
Didn't had the chance to test and see if I can log in in and use bot in same time ...when I'm home I will probably do that also :)
-
ok i don't get the bot running on my system ... tried it with vers. 0.6.2 an 0.6.3 both are not runnig ... they could connect to aochat server ... and yes i have done the source update with the new files ... but it don't work ... could be the problem that my bot is running under a linux system ???
-
http://forums-eu.ageofconan.com/showthread.php?p=1352368&posted=1#post1352368
hes working on it
-
Can Any of the Bebot devs pleeease help Chaoz out? He has done a really good job atm implementing the new auth protocol.
Now if any of you could take his code and fix it so it works again as how it was working before the 1.0.5 patch?
-
I get Connecting
Authenticating
Read Error: EOF
Error while reading rpc header. ()
Anyone have a clue, i backed up the old filed and replaced with his new ones from his link on the Euro forums.
-
i think everyone gets that message, its not fatal for bot (i think, dont remember what error shows me)
and start bot when youre not online with your chars, you should have no problem then, atleast i dont have (with bot :) )
but then, when bot is connected i need to try 5-10 times logging onto my chars, but thats not problem for me, i just want bot to work :)
-
ok than pls pls pls tell me how u get your bot running ??? i have my bot in a linux area an he wouldn't start either log in ... i tried it with the v. 6.2 and 6.3 ... futher i tried all the ip's i could found ... nothing would get the bot running ... pls pls pls help ...
why this ist soo important for me ?? I CAN'T WITHOUT BEBOT ;)
thx
Drizzurdeen
-
I get Connecting
Authenticating
Read Error: EOF
Error while reading rpc header. ()
Anyone have a clue, i backed up the old filed and replaced with his new ones from his link on the Euro forums.
i think everyone gets that message, its not fatal for bot (i think, dont remember what error shows me)
and start bot when youre not online with your chars, you should have no problem then, atleast i dont have (with bot :) )
but then, when bot is connected i need to try 5-10 times logging onto my chars, but thats not problem for me, i just want bot to work :)
I've tried this with my Character not being online. I waited nearly an hour to connect and it just barfed. Its been a bit since I set up the Bot. Don't I have to edit a config and change server IP or name or was that updated in the Server.php
-
ok bot ist working fine by me ... but only under os: windows-server
but this could not be the workaround to switch on windows to get the bots working :( ... i would prefer that the bots will run under os: linux ...how they ever did ;)
would be an possibility to get bots runing for aoc under linux with the new files for chat-logins ??? would be perfekt ...
thanks
Drizzurdeen
-
ok bot ist working fine by me ... but only under os: windows-server
try this AOChat.php. works on debian lenny arm.
http://www.file-upload.net/download-1739567/AOChat.zip.html
server: aoc-eu-um.live.ageofconan.com', 'port'=>7000
Bebot 6.3 on Mitra
-
thanks a lot ... works prefekt with os: linux with the aochat.php file u postet ... further bebot 0.6.2 is running with the files ...
thx thx thx
drizzurdeen
-
I downloaded the AOChat.php file that was linked and I get a different error now. Going to keep looking into it, but does anyone get a similar error or know what the problem is?
AOChat: Did not receive the serveraddress for the territorymanager.
-
I am still getting the error about the address for the territory manager. I have tried multiple things and end up with the same result. The last set of changes I followed was from this post (http://forums-eu.ageofconan.com/showpost.php?p=1359819&postcount=183) on the EU forum. I thought this might be a firewall issue, but I believe all of the required ports are open now. I will list my system info and the result of my attempt to run in case anyone has any idea what is going on. Since I have not run this bot before, typically use what I create based on VhaBot, I don't know if this is a general setup issue or an issue due to the 1.05 changes.
BeBot: 0.6.3
OS: Linux
Kernel: 2.6.28-9.16
Architecture: x86_64
PHP: 5.2.9
MySQL: 5.0.75
MySQL database connection test successfull
Creating MySQL class!
Creating AOChat class!
Creating main Bot class!
MyBotName [MAIN] [DIR] Loading main functions of the bot
...
MyBotName [MOD-CUSTOM] [DIR] Loading additional modules in directory custom/modules/
MyBotName [LOGIN] [STATUS] Connecting
MyBotName [LOGIN] [STATUS] Authenticating
AOChat: Did not receive the serveraddress for the territorymanager.
-
I am still getting the error about the address for the territory manager. I have tried multiple things and end up with the same result. The last set of changes I followed was from this post (http://forums-eu.ageofconan.com/showpost.php?p=1359819&postcount=183) on the EU forum. I thought this might be a firewall issue, but I believe all of the required ports are open now. I will list my system info and the result of my attempt to run in case anyone has any idea what is going on. Since I have not run this bot before, typically use what I create based on VhaBot, I don't know if this is a general setup issue or an issue due to the 1.05 changes.
BeBot: 0.6.3
OS: Linux
Kernel: 2.6.28-9.16
Architecture: x86_64
PHP: 5.2.9
MySQL: 5.0.75
MySQL database connection test successfull
Creating MySQL class!
Creating AOChat class!
Creating main Bot class!
MyBotName [MAIN] [DIR] Loading main functions of the bot
...
MyBotName [MOD-CUSTOM] [DIR] Loading additional modules in directory custom/modules/
MyBotName [LOGIN] [STATUS] Connecting
MyBotName [LOGIN] [STATUS] Authenticating
AOChat: Did not receive the serveraddress for the territorymanager.
You can fix that with: http://forums-eu.ageofconan.com/showpost.php?p=1353313&postcount=101
Replace: displayConanError( $chatServerPacket->args[0] ); in AOChat.php with:
$this->displayConanError( $chatServerPacket->args[0]);
-
I tried that and still get the same error.
-
I put in some debug points and appear to get a value of "4294967295" for the login status. I think I saw somewhere in the code that negative values get 4294967296 added to them, so I am guessing the status was a -1. The other values come back as 0 or empty. Are there any ports other than the 7000-7013 range I might need to open up?
-
Ok, hopefully final error message... "Error while reading RPC header"
Anyone know which file this would be in to edit? The serverlist file is correct of course and I can telnet to the server without issues...
-
I get Connecting
Authenticating
Read Error: EOF
Error while reading rpc header. ()
Anyone have a clue, i backed up the old filed and replaced with his new ones from his link on the Euro forums.
bump for issue fix??
-
Please file a bugreport at https://bugs.launchpad.net/bebot/+filebug
Djkrose is working on the AoC issues based on the patches from Chaoz. Hopefully he will be able to help figure out what is going on.
-
Please file a bugreport at https://bugs.launchpad.net/bebot/+filebug
Djkrose is working on the AoC issues based on the patches from Chaoz. Hopefully he will be able to help figure out what is going on.
Ok, bug report #396248 filed... *throws wishing dust into the air*
Thank you :)
-
Please file a bugreport at https://bugs.launchpad.net/bebot/+filebug
Djkrose is working on the AoC issues based on the patches from Chaoz. Hopefully he will be able to help figure out what is going on.
Ok, bug report #396248 filed... *throws wishing dust into the air*
Thank you :)
PORT 7000 worked!!!
-
Please file a bugreport at https://bugs.launchpad.net/bebot/+filebug
Djkrose is working on the AoC issues based on the patches from Chaoz. Hopefully he will be able to help figure out what is going on.
Should I report a bug also, or does this sound more like a server setting issue in my case with not getting back info about the territory manager? I tried setting up ragebot and had the same result. I think it is based on the same chat library, so I don't think that can rule anything out really.
-
Heya :-)
I've done a rewrite of the patch I made originally so it should handle stuff much better now.
I'll put it out here - and please give me feedback on it. http://www.conanchat.com/download/BeBot_0.6.2_NewLogin.zip
I have not fixed the 64 bit issue, but I saw that someone had another patch on that :)
When it comes to the autodisconnecting bots - I made a seperate fix for that for myself by basicly muting the private channel messages (since they seem to disconnect the bot when they are used).
If any of the devs here are interested I can supply a diff file instead + some info on the changes I've made.
Chaoz
-
Hi Chaoz.
First of all i would like to extend a big thank you from the development team and the BeBot community.
Up until recently we have had no active team members with AOC accounts, making support of the major change in 1.05 next to impossible.
Without your work, i have no idea how long it would have taken to get working support for php based bots.
The 64bit issue is indeed fixed in the upcoming 0.6.4 release which is planned for as soon as your final changes have been integrated and some more testing is carried out.
A diff is not really needed as it can be created easily, but i would be interested in seeing your separate fix and have that included as well. If memory serves, private channels are not used in AoC.
If you feel there are any areas of your changes that needs commenting, feel free to do so as all information is most welcome.
I do have one question. From the AoC forum posts i've been monitoring it seems like the bot now connects pretty much like the gameclient, and actually connects to the gameworld only to be timed out. Is there any way to forcibly close the connection to the gameworld allowing players to immediately log on their play characters?
Again, thank you for your time and effort :)
-
I put in some debug points and appear to get a value of "4294967295" for the login status. I think I saw somewhere in the code that negative values get 4294967296 added to them, so I am guessing the status was a -1. The other values come back as 0 or empty. Are there any ports other than the 7000-7013 range I might need to open up?
The reason why I added the number is that the default int type in php is signed int, and the numbers used are unsigned (above the 2 billion mark), so it is basicly to flip to back to unsigned. php will make it into a long when I do that I guess.
-
I put in some debug points and appear to get a value of "4294967295" for the login status. I think I saw somewhere in the code that negative values get 4294967296 added to them, so I am guessing the status was a -1. The other values come back as 0 or empty. Are there any ports other than the 7000-7013 range I might need to open up?
The reason why I added the number is that the default int type in php is signed int, and the numbers used are unsigned (above the 2 billion mark), so it is basicly to flip to back to unsigned. php will make it into a long when I do that I guess.
Yeah that makes sense. Was just trying to figure out what the status code was to see if it would help determine an error.
The new result I get is still indicating that I do not get IP or port info.
Botname [LOGIN] [STATUS] Connecting
Botname [LOGIN] [STATUS] Authenticating
Warning: RPC_UNIVERSE_AUTHENTICATED: Error in serveraddress, [Ip::0] in /botpath/Sources/AOChat.php on line 1456
disconnect
Botname [CONN] [ERROR] Failed authenticating to server. Retrying in 60 seconds.
Also, I have to specify the password in the config file or I get other errors instead of being prompted.
<br />
<b>Warning</b>: fwrite(): supplied argument is not a valid stream resource in <b>/botpath/Sources/Conf.php</b> on line <b>60</b><br />
<br />
<b>Warning</b>: fgets(): supplied argument is not a valid stream resource in <b>/botpath/Sources/Conf.php</b> on line <b>62</b><br />
X-Powered-By: PHP/5.2.9
Content-type: text/html
===================================================
_/_/_/ _/_/_/ _/
_/ _/ _/_/ _/ _/ _/_/ _/_/_/_/
_/_/_/ _/_/_/_/ _/_/_/ _/ _/ _/
_/ _/ _/ _/ _/ _/ _/ _/
_/_/_/ _/_/_/ _/_/_/ _/_/ _/_/
An Anarchy Online Chat Automaton
And
An Age of Conan Chat Automaton
v.0.6.3 - PHP 5.2.9
===================================================
<br />
<b>Warning</b>: fread() [<a href='function.fread'>function.fread</a>]: Length parameter must be greater than 0 in <b>/botpath/Main.php</b> on line <b>170</b><br />
-
How exactly are you running this bot? Are you launching it from a webserver?
-
It is being run on a server, but I am launching it from the command line using the php5 StartBot.php command.
-
Are you all getting the bot to connect/run now after Chaoz's recent update?
I'm still getting the RPC header error. :'(
-
Are you all getting the bot to connect/run now after Chaoz's recent update?
I'm still getting the RPC header error. :'(
I'm having the same problem still.
-
Are you all getting the bot to connect/run now after Chaoz's recent update?
I'm still getting the RPC header error. :'(
I'm having the same problem still.
If you are getting the RPC error, are you sure you have the correct server and port specified in the config? When I try to connect directly to the Set server IP, I get that error. Remember we are not connecting directly to the chat server now, but we actually have to log in first. You should set your server to be "Us" or "Eu" (somewhere in the code the value from the server list gets converted to a proper case or something with the first letter upper and the rest lower, so watch your casing). Sorry if you already tried that. I have read too many posts on this stuff recently to recall who has done what.
-
Whooha! SHE's ALIVE!!!! :D
Port 7000 ... that's the trick. I'm on Cimmeria and port for all US servers listed in the serverlist.php are all shown to be above 7000. I read somewhere that 7000 was the winning port. I changed my server entry in the serverlist.php to be 7000 (was 7004) and it has worked; it stopped the RPC header error.
Of course too, I downloaded Chaoz's latest patch, found here: http://www.conanchat.com/download/BeBot_0.6.2_NewLogin.zip
I'm running the 0.6.2 bot still, so dunno how you 0.6.3 folks will fare with that patch.
-
works without problem (0.6.3) :)
-
I have posted a pre release version of BeBot 0.6.4. We are gearing up to release this soon, but would ike to have it receive some more AoC testing as we only have one developer with an AoC account.
You can find it at https://launchpad.net/bebot/0.6/0.6.4.rc
Please take it for a test spin and let me know if it works for you or not.
Preliminary changelog for this release:
- Modified the network protocol to work with AoC 1.05. Please note that PrivGroup relays are no longer an option for AoC due to chatserver changes.
- Reversing stripping of control characters on text from IRC for now.
- htmlspecialchars_decode text going to IRC to decode & and similar.
- IRC join/part/quit messages now properly prefixed on IRC and are also relayed over guild relay if UseGuildRelay is set for IRC module.
- IRC part/quit messages are now relayed ingame.
- Fixed flip command
- Added the option to make reason required for !ban add
- Added a check for botname_rules.txt before getting rules.txt
- Lots of Changes to Raid module, lots of new function and features including restart/crash support, raid logging, raid control interface, punish raiders, move countdown, min level and also fixed alot of problems with output to wrong place or unnessesary spam
- Lots of Changes to Bid module, lots of new function and deatures including using points log, !bid cancel, !bid all, and more
- Corrected some color codes and time zone for "last online" in !whois (AoC only)
- Backported some fixes from trunk to make it bearable to enable E_ALL logging
- Changed help for !aliasadmin (which didn't exist) to !alias admin
- Bot doesn't tell people that there are "No news." upon login any more. Only if they ask for "!news".
- Added more spam protection (e.g. when double clicking tell links) to message queue.
Big thanks to Chaoz for providing a patch for the 1.05 protocol changes.
-
Hi,
Having some strange problems with guild chat, cant get it to send output to, or read input from guildchat in AoC.
Every command is just ignored silently, same with !say cmd in tells.
Running Ubuntu 32bit with 0.6.4.rc on PHP 5.3.0RC1
This is what happens when the bot connects:
Muffin [LOGIN] [STATUS] Connecting
Muffin [LOGIN] [STATUS] Authenticating
Unsupported rpcpacket type (in, 5)
Unsupported rpcpacket type (in, 4170821964)
Unsupported rpcpacket type (in, 1334945164)
Unsupported rpcpacket type (in, 1525492320)
Bot is now logged in.
Muffin [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'Muffin'
Muffin [SETTINGS] [LOAD] Loaded settings from database.
Muffin [LOGIN] [RESULT] OK
All the chatter in guildchat show up in console, so afaik it can read it ok, but it is being totally ignored.
Could it be that the remove of privategroup breaked guildchat somehow?
Dobstah
I have posted a pre release version of BeBot 0.6.4. We are gearing up to release this soon, but would ike to have it receive some more AoC testing as we only have one developer with an AoC account.
You can find it at https://launchpad.net/bebot/0.6/0.6.4.rc
Please take it for a test spin and let me know if it works for you or not.
Preliminary changelog for this release:
- Modified the network protocol to work with AoC 1.05. Please note that PrivGroup relays are no longer an option for AoC due to chatserver changes.
- Reversing stripping of control characters on text from IRC for now.
- htmlspecialchars_decode text going to IRC to decode & and similar.
- IRC join/part/quit messages now properly prefixed on IRC and are also relayed over guild relay if UseGuildRelay is set for IRC module.
- IRC part/quit messages are now relayed ingame.
- Fixed flip command
- Added the option to make reason required for !ban add
- Added a check for botname_rules.txt before getting rules.txt
- Lots of Changes to Raid module, lots of new function and features including restart/crash support, raid logging, raid control interface, punish raiders, move countdown, min level and also fixed alot of problems with output to wrong place or unnessesary spam
- Lots of Changes to Bid module, lots of new function and deatures including using points log, !bid cancel, !bid all, and more
- Corrected some color codes and time zone for "last online" in !whois (AoC only)
- Backported some fixes from trunk to make it bearable to enable E_ALL logging
- Changed help for !aliasadmin (which didn't exist) to !alias admin
- Bot doesn't tell people that there are "No news." upon login any more. Only if they ask for "!news".
- Added more spam protection (e.g. when double clicking tell links) to message queue.
Big thanks to Chaoz for providing a patch for the 1.05 protocol changes.
-
I've reproduced the issue. Looking into it now.
-
Extracted tar.gz with new files over old install with "overwrite all".
Got the same messages. The bot is up and running but it only listem to tells and do not see the Guild Chat.
[edit]
Also I have noticed that some lines in log begins with "guildmessage..".
Usualy it looks like:
Mybot [TELL] [INC] Mychar: !whois Someone
and sometimes (no rulle atm) it looks like
guildmessage..Mybot [TELL] [INC] Mychar: !whois Someone
Do not know if that matters, but it starts to appear form Chaoz second patch (or at least I have never saw anything like that before).
-
Isolated the issue and uploaded fixed archives.
Manual fix if you are confortable editing files (2 lines need to be changed)
http://bazaar.launchpad.net/~bebot-devel/bebot/stable-0.6/revision/84
Apologies for the problems.
-
Still:
Mybot [LOGIN] [STATUS] Authenticating
Unsupported rpcpacket type (in, 5)
Unsupported rpcpacket type (in, 4170821964)
Unsupported rpcpacket type (in, 1334945164)
Unsupported rpcpacket type (in, 1525492320)
Bot is now logged in
Mybot [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'Mybot'
But now it is talking on Guild channel.
I'll let it work for some time and post if anything unusual happens.
-
I am running into a problem after the bot has been logged on for a minute. I get spam about mysql errors and then the bot restarts. I believe it goes from 1 to around 1160 (seems to vary). I know it is connecting and able to do things at some point as there are tables created and populated with data. I also double checked and the db user has all privileges. Note I am using the changes in revision 84 and added the one from 85 (same result). System is Linux 64bit, kernel 2.6.28-9.16, PHP 5.2.9, MySQL 5.0.75. I can post or send a full log if wanted.
Mybot [2009-07-10 14:21:45] [LOGIN] [STATUS] Connecting
Mybot [2009-07-10 14:21:46] [LOGIN] [STATUS] Authenticating
Unsupported rpcpacket type (in, 5)
Unsupported rpcpacket type (in, 4170821964)
Unsupported rpcpacket type (in, 1334945164)
Unsupported rpcpacket type (in, 1525492320)
Bot is now logged in.
Mybot [2009-07-10 14:21:50] [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'Mybot'
Mybot [2009-07-10 14:21:50] [SETTINGS] [LOAD] Loaded settings from database.
Mybot [2009-07-10 14:21:50] [LOGIN] [RESULT] OK
Mybot [2009-07-10 14:22:21] [SETTINGS] [LOAD] Loaded settings from database.
Mybot [2009-07-10 14:22:21] [ROSTER] [UPDATE] Roster update ran less than 6 hours ago, skipping!
Mybot [2009-07-10 14:23:22] [MySQL] [ERROR] (# 1) on query: Database not found or insufficient priviledges!
MySQL server has gone away
I also found one error that showed a segmentation fault:
Mybot [2009-07-10 14:23:23] [MySQL] [ERROR] (# 708) on query: Database not found or insufficient priviledges!
sh: line 1: 21378 Segmentation fault /usr/bin/php -c ./ Main.php
-
@rmb
Those notices should be perfectly safe to ignore. I believe they are RPC packets that BeBot does not need to worry about and they are left in there by Chaoz for debugging purposes.
I am running into a problem after the bot has been logged on for a minute. I get spam about mysql errors and then the bot restarts. I believe it goes from 1 to around 1160 (seems to vary). I know it is connecting and able to do things at some point as there are tables created and populated with data. I also double checked and the db user has all privileges. Note I am using the changes in revision 84 and added the one from 85 (same result). System is Linux 64bit, kernel 2.6.28-9.16, PHP 5.2.9, MySQL 5.0.75. I can post or send a full log if wanted.
Mybot [2009-07-10 14:21:45] [LOGIN] [STATUS] Connecting
Mybot [2009-07-10 14:21:46] [LOGIN] [STATUS] Authenticating
Unsupported rpcpacket type (in, 5)
Unsupported rpcpacket type (in, 4170821964)
Unsupported rpcpacket type (in, 1334945164)
Unsupported rpcpacket type (in, 1525492320)
Bot is now logged in.
Mybot [2009-07-10 14:21:50] [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'Mybot'
Mybot [2009-07-10 14:21:50] [SETTINGS] [LOAD] Loaded settings from database.
Mybot [2009-07-10 14:21:50] [LOGIN] [RESULT] OK
Mybot [2009-07-10 14:22:21] [SETTINGS] [LOAD] Loaded settings from database.
Mybot [2009-07-10 14:22:21] [ROSTER] [UPDATE] Roster update ran less than 6 hours ago, skipping!
Mybot [2009-07-10 14:23:22] [MySQL] [ERROR] (# 1) on query: Database not found or insufficient priviledges!
MySQL server has gone away
I also found one error that showed a segmentation fault:
Mybot [2009-07-10 14:23:23] [MySQL] [ERROR] (# 708) on query: Database not found or insufficient priviledges!
sh: line 1: 21378 Segmentation fault /usr/bin/php -c ./ Main.php
Could you please show me output from "php -v" using the same binary as the bot.
Your error indicates that the MySQL server allows the bot to connect, but does not allow it to select the database. Try checking your MySQL log for more information.
The code in question as far as the bot goes is on line 137 in Sources/MySQL.php
if(!mysql_select_db($this -> DBASE, $conn))
{
$this->error("Database not found or insufficient priviledges!", $initial);
return false;
}
-
Here is the output:
PHP 5.2.9 (cgi-fcgi) (built: Jun 13 2009 02:45:53)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
-
Im not sure if there is a big difference or not, but do you have a php-cli binary on your system?
That particular php version is compiled for fastcgi usage and not command line usage.
I've made a modified MySQL.php you can try if you wish with some additional debug output:
http://pastebin.com/d4fa9bcc7
The logic in that one is pretty much the same, we just go about checking in a different manner.
-
I posted a copy of the output to here (http://www.pestilence-guild.net/download/bot.log). The first error appears to be on updating the time in the bots table. After that it looks like errors are trying to be posted to the log_message table which is causing more errors. I did start the bot using php5-cli this time also.
-
Ok. Judging from the log output you are still running with the fcgi version of PHP. Please note that the StartBot script will fall back to the system default php binary which in your case is a cgi based php. Either manually change StartBot.php or start the bot using Main.php directly.
For some reason your php does not behave as it should for mysql_connect, it simply does not detect that it no longer has a valid connection to MySQL and as such tries to keep using it causing the errors to occur.
I can only think of two possibilities aside from making sure you are running a CLI version of PHP which might or might not make a difference.
If your MySQL server is on the same physical server as your bot there are two ways to connect. One is by TCP/IP (127.0.0.1) and the other is using the unix socket (localhost), try changing from the one you are using to the other and see if that helps.
If none of the above helps, try changing your error function to look like this:
function error($text, $fatal = false)
{
$this -> close();
$msg = mysql_error();
$this -> error_count++;
$this -> bot -> log("MySQL", "ERROR", "(# " . $this -> error_count . ") on query: $text\n$msg", TRUE);
// If this error is occuring while we are trying to first connect to the database when starting
// rthe bot its a fatal error.
if ($fatal == true)
{
exit;
}
}
This should force MySQL to close the connection if an error occurs, meaning the SQL call will still fail, but it should force the bot to try and reconnect with a clean connection.
-
I would like to know if anyone else have the bot losing connection to the chat server around 5 minutes after it starts too. Using 6.3 and the latest changes to login as posted in this thread on the 8th by Chaoz. Tried it out a couple of times. Just started the bot no tries to log into game. Bot connects correctly and can be accessed correctly by people in guild channel. But like i said around 5 minutes later it gets disconnected.
Also is the link above still valid as the most recent RC version ?
-
https://code.launchpad.net/bebot/+download will always lead to the latest downloads published unless otherwise indicated.
If you have Bazaar installed you can also check out the very latest version from our source code repository using the bazaar command:
bzr co lp:bebot/0.6
As for your disconnect issue, it would be helpful to know if anything is displayed in console/log just prior to disconnect and any errors or notices when the actual disconnect happens.
Would also be helpful to know if the 0.6.4 pre2 has this issue and if there are any errors, log output from this version is prefered.
-
Well, 0.6.4 pre2 is working for my guild almost 2 days.
I tried all known "post 1.05 patch" errors (like crash on logon or crash on afk) and it is still working uninterrupted.
Other then:
Mybot [2009-07-10 14:21:50] [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'Mybot'I see no problems.
-
Good to hear. Thanks for helping to test this out rmb :)
-
Same here, even the logon, the afk and the teamspeak stuff works without dc the bot.
Good job all who made it happend.
Jih.
-
The current 6.4 build is working fine without disconnections! :)
-
good work!
is it possible to run a bot and play on the same aoc account?
-
It is possible, but from what i understand you will need to wait 5-15 minutes after starting the bot to be able to log ingame, and if the bot disconnects for any reason you will also be disconnected.
-
Thanks, got our bot workin first time on *nix platform since the 1.05 update on the game! Marvelous! :-*
-
I put in the 32bit long fix in my patch for 0.6.2 as well - but I've also added the missing rpc methods to avoid the errors you get when logging in:
0.6.2 patch
http://www.conanchat.com/Download/BeBot_062_LoginPatch2.zip
Check out the defines for the 4 new rpc packets :)
Also fixed up all the server addresses now, so the non english, us and testlive server addresses in the conf/ServerList.php is working.
Chaoz
-
FYI: I just got my bot back online with the 0.6.4pre2 version and it seems to work fine.
One thing though: If you need to do a !restart command, it will not log the bot in, and will kick your in-game char out. It will take approx 5 min for you to work it all again.
Suggestion: a reload function that would reload the settings instead of a full restart.
With the next login mech, the only way to restart the bot is to log out, kill the php prog (this is on linux btw) and then wait 5 min or so. Then you can startup the bot again. Wait for a few min, then log in your char.
Thoughts?
-
This is a limitation caused by the Funcom changes. Nothing we can do about it as far as i know.
However what settings are you refering to? Only settings that would require a restart is in the Bot.conf. Everything else is done trough !settings and is effective immediately. Nothing there needs a restart.
-
Activating/deactivating modules with !modules also needs a restart. Maybe it's possible to add a dynamic loading/unloading mechanism for modules sometime, but it would be a complicated task to clean up all the settings, triggers, commands, help texts etc.
-
Speaking of which 6.4 pre , the bot's time is set to UTC for a raid schedule module for example. Where is the time being changed at?
-
At the moment, BeBot always uses UTC. The only way to modify the time shown is by changing the time (not time zone!) of your computer/server.
We are just discussing internally a way to let the user decide, which time zone the Bot is using. However don't expect this to go into 6.4...
-
What I don't understand somewhere in 6.03 it equates to the computers time zone for the raid planner, but somewhere with 6.4 pre it makes it UTC ???
-
The reason for this is that BeBot 0.6.4 explicitly sets the timezone to UTC to resolve an issue with massive warning spam from PHP.
You can either override this by setting the timezone you wish by editing Main.php and finding the line:
// Set the time zone to UTC
date_default_timezone_set('UTC');
Insert the apropriate timezone for your area (see http://no2.php.net/manual/en/timezones.php for a list of valid timezones)
Or just comment the line out for now.
-
Nice thanks!
-
Hello again, a couple questions, first a general one, while loading the bot up i get msgs along the line of:
"XXXX [ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: 'XXXX'"
i tried removing allantries connected to those apparently no longer existing characters using !admin del XXXX, and though it is saying they are no longer members of the bot i still get the above line at bot start.
The other issue and this seem to have came up only after 1.05 and while using 6.4 pre2 is the -1 member "thing" on bot start i would get the following
"XXXX [BUDDY QUEUE] [BUDDY-ADD] -1" trying to remove "-1" from buddy list does not help exactly.
Alrdy tried !buddylist clear, but as soon as i do a roster update i end up with those -1 popping up again.
The other part of it is if people log in sometimes msgs along the line of :
XXXX [GROUP] [MSG] [XX] XXXX: "-1" (Lvl 19 Herald of Xotli) Logged On :: Alt of 17114350 :: [link]Details[/link]
however after zoning around it tends to recognize them and posts the msg onemore time with the correct info as if they just came on.
Any thoughts?
[edit by Khalem for readability]
-
Hm I got the same issue now that I upgraded from 0.6.2 and 0.6.3 to 0.6.5.
I can have a quick peek into it to see why unless it is a known issue :)
Chaoz
-
my guess is you have had members leave and come again?
as such there are tables such as online, alts, and members which all have same data but when they are removed doesnt removed them from all, nor does re-rolls fully work etc.etc.
atm when i boot up my bot i have about 15 failure to identify user XXXXXXXXXXX (numbers) [Char ID]
then 15 -1 on notifies
\all coz they are ppl that had transfered off, deleted, or so on
-
Ofc FC did change something in the chatserver on 1.05.6 patch.
I do remember reading from someone that this was most likely to happen and a allready fix was made while it was on TL, could this person step forward and tell us the secret? ;)
v.0.6.6.(snapshot) - PHP 5.2.8 Windows_NT 32bit
Namebot [2009-10-27 14:36:18] [LOGIN] [STATUS] Connecting to aoc server aoc-eu-um.live.ageofconan.com:7000
Namebot [2009-10-27 14:36:18] [LOGIN] [STATUS] Authenticating
Read error: EOF
Warning: Error while reading rpc header. () in D:\AgeOfConan\Sources\AOChat.php on line 489
Warning: handleRPCPackets: Packet is not an object (no RPCPacket?) in D:\AgeOfConan\Sources\AOChat.php on line 691
Namebot [2009-10-27 14:36:21] [CONN] [ERROR] Failed authenticating to server.
Retrying in 60 seconds.
-
yes please post the fix for patch 5.6! :)
-
Found the text i was searching for:
http://bebot.link/coding-and-development-discussion/login-changes-in-aoc-1-5-6-patch/
-
Not best place, but good as any.
Wanted to say thanks to all for making being a first time Bot user a lot less painful then it could have been. Now, if i could just teach my guildies to spell :o
Beers all around to those that continue to help noobs like me!