Author Topic: A little help needed (Read 19831 times)

Keyra · « **on:** December 30, 2007, 08:29:02 pm »

I put in my correct org ID (Is it supposed to be in quotes"?)I'm not really sure whats wrong with it. but it's not seeing any org members it doesn't notice anyone. But !whois is working fine... also !roll and !say aren't working.

I think it needs a roster update. but not sure how to force it.

Any help is much appreciated.

Temar · « **Reply #1 on:** December 31, 2007, 12:26:12 am »

to force update its !rosterupdate
!say simple outputs to your GC
if u do /tell !say hello
and it replies check the access control as it prob means u dont have permission to do it (!commands)
if the problem is the bot isnt talked or responding to anything on GC then check you Org name is Correct in the .conf

Keyra · « **Reply #2 on:** December 31, 2007, 06:13:29 am »

No. when I say !online it doesn't recognize any members it's says 0 members online. Also it doesn't recognize the !say or !rosterupdate commands. it says /tell Bubbot !help

I don't understand what's wrong with it. I have permission as I'm set as Owner. however it's not doing anything. timer or anything

Any ideas?

It seems all of the code is wrong for some reason.
And I'm not too versed on how to re-write it

Alreadythere · « **Reply #3 on:** December 31, 2007, 03:09:24 pm »

If whois works, then the roster update should work too.

Did you set guildbot = true? Otherwise it won't try to grab the org roster.

Keyra · « **Reply #4 on:** December 31, 2007, 07:51:25 pm »

It was actually Already set to true

Temar · « **Reply #5 on:** January 01, 2008, 08:22:19 am »

Quote

if u do /tell !say hello
and it replies check the access control as it prob means u dont have permission to do it (!commands)

I ment if it replied /tell botname !help
then check access control (!commands)
if !commands dont work then u dont have full access to bot as !commands can't be disabled

Wolfbiter · « **Reply #6 on:** January 01, 2008, 10:28:41 pm »

Before you all bang your head into the wall too much.. in his first post, before he edited.. he mentioned an error on line 36 (but not what error or which file)...