Author Topic: Bebot v0.2.10 and !whois (Read 12695 times)

ilon · « **on:** December 27, 2006, 05:08:42 pm »

Ok, tried various things, still dont get it >_>
I installed v0.2.10, and trying to get the new char ids to work in whois and towerbattles, what, exactly, does need to be changed / done in a 0.2.10 installation? anyone feels like making a list?

cheers

Khalem · « **Reply #1 on:** December 27, 2006, 05:36:52 pm »

What needs to be done is for Funcom to fix issues on their end. Until they do, the only way you are gonna get a whois reply from a character with a high charater id is from them being in your guild and updated from the guild xml.

BeBot has fixed the issues on the bot side, now we can only wait for Funcom to decide it's worth it to fix the issues with their code, which i might add, is not restricted to third party tools like BeBot, but also affects the game client itself on some areas according to reports i've read.

ilon · « **Reply #2 on:** December 27, 2006, 05:50:30 pm »

oh, that sucks bigtime :/ No current workaround? read about the local DB, but cant get it to work

================================================
0 http queries for org information done!
0 total http queries done!
0 entries in database associated with an org modified!
0 entries in database modified!
0 entries in the whois cache!
0min 0sec runtime for org updates!
0min 0sec total runtime!
================================================

dosnt fetch anything

Malosar · « **Reply #3 on:** December 27, 2006, 05:55:37 pm »

The local whois db doesn't fetch anything per se, it updates existing data. When you do a whois on a character ingame, the whois db gets the information from FC and stores that in the local db. So the next time you do a whois on that character, it retrieves the info from the db instead of FC, making it a lot faster.

The script you referred to updates the data in the db depending on how old it is based on the timestamps. But there must be existing data in the db already.

ilon · « **Reply #4 on:** December 27, 2006, 06:28:27 pm »

Ahh, ok, now i get it, i think

So I need to use the modified version of !whois to be able to see newly created chars?
Is there any replacement files to make it work? or do I have to edit the files by hand?
Would be nifty with a sticky including replacement files to get it working, i cant be the only one having trouble >_>

well, hope someone could help me, really lost on how to do it

jjones666 · « **Reply #5 on:** December 27, 2006, 10:11:37 pm »

Use the search facility, I wrote a topic regarding this issue with links to all needed files.

-jj-

Glarawyn · « **Reply #6 on:** December 27, 2006, 10:36:33 pm »

Quote from: Khalem on December 27, 2006, 05:36:52 pm

Until they do, the only way you are gonna get a whois reply from a character with a high charater id is from them being in your guild and updated from the guild xml.

The Auno fallback in the 0.3 dev trunk whois/whois cache module solve the whois issue for any characters who are in an org. Auno's site discovers new players when they join an org, and is able to provide single player XML data if the person is in an org.

At the moment, it's the best that can be done on the client side of things.

ilon · « **Reply #7 on:** December 28, 2006, 09:00:15 am »

ok, i'll go struggle with that workaround once more, tried it already, didnt get it to work (like the noob i am :O) >_>

ilon · « **Reply #8 on:** December 31, 2006, 01:40:48 pm »

now it dosnt work with old char ids either, CRAP! >_>

pusikas · « **Reply #9 on:** January 02, 2007, 01:28:26 am »

Go slowly, I needed a few tries to get the 2.10 BeBot to run with all the nice stuff from this forum. Get it to run in an unmodified version first. Then perhaps try to get the whois-cache to run. Since it is not started by the bot, you have to make a cronjob for it - I sure hope you are using some kind of *nix, no idea how to schedule tasks in windows.

It will first look like it doesn't fetch anything, but if it runs without error messages, that's a good thing already. Then try to add the new !whois module. A !whois on a "new" toon will still not work, but if you do that on an "old" toon in the same org, you should get an anwer. Now run the external update script again, and the whole org of the queried person should be fetched into the whois-cache. If you do a !whois on the new toon after this, you should not get a "blabla was too slow to respond" anymore, but a nice answer already.
At that point, I ran madly through borealis and did !whois on all people I could find to seed the cache with data. Once you have done this with all major orgs, the whois-update can take quite a while, I think it pulled over 40K toons into the cache after my first !whois-spree. ^^*
Up to this point, you should not have to fiddle with any important tables from the bot, and only have touched the !whois module, so the changes are still easy to revert. It gets messier when you start to swap out the Alts, roster_guild and tower modules. Make sure you keep backups of all the files and tables you touch.
Actually, I don't think I found a tower module that uses the whois-cache and works for me, so I had to modify that by hand. Can post it when you reach the point where you got the cache running.