Author Topic: raid bot errors on first run (Read 6858 times)

clashbot · « **on:** February 21, 2008, 02:03:57 am »

I went through the steps to create the raid bot, but on first run, got an error "could not redeclare function raid calling raidtime.php on line 52" that was from raid.php. commented out raidtime, and got this error on second run: "call to a member function connect() on a non-object in bot.php on line 237."

What am I doing wrong, and what can I do to fix it.

Blueeagle · « **Reply #1 on:** February 21, 2008, 02:17:41 am »

The error occures when you try to declare a class or a function and a class or function with the same name has already been declared in the same scope.

The most likely cause for such an error to occur on BeBot is if you've got two modules that does the same thing or a custom module that uses the same class- or function name.

I thought that such an error also produced some message along the lines of "function was first declared in <filename> on line <number>" or somesuch.

Now I'm not a wizz on the raidbot setup but I would guess that both raidtime.php and raid.php attempt to declare the class named raid. It would seem that both these does essentially the same thing but in different ways. Prefixing one of them with _ (ie. disabling them) should help.

The error "call to a member function connect on a non-object" is caused by the bot attempting to access a method on a class that was not properly or correctly declared.

This all runs down to what I think are incompatibillities between modules and or a module and the core bot.

If you are trying to run old modules with the latest bot that might cause the problem.

Please re-try with a clean installation and a clean database to see if that fixes things.

clashbot · « **Reply #2 on:** February 21, 2008, 02:52:32 am »

ok, on the bot.php error, I tested it out with a guildbot and everything worked fine, it was only when I switched it to a raid bot...I configured the bot.conf correctly according to the help files, I also rem'd out all the guild mods and enabled all the raid mods per the core and modules folder. there shouldn't be any incompatibles *that I know of* as all the modules work fine with guild. The database I hope is not the issue, as part of the purpose of this is to share online lists with all the bots (running 3 guild bots, and hopefully a raid bot if I can get this error taken care of)

Thanks for the fast reply

Blueeagle · « **Reply #3 on:** February 21, 2008, 03:10:10 am »

Ok, after reviewing the modules I see that modules/Raid.php and modules _RaidTime.php are in conflict. That is you can enable one but not the other. The difference between the two appears that _RaidTime.php offers the participants points per minute and Raid.php does not.

I am not sure how stable these two modules are as I don't dabble with such things. Khalem was the one who developed on those modules and he is no longer active in development.

For now you'll have to choose which one of the two modules you want to use.

I guess Glarawyn can offer some advice aswell when he reads this.

clashbot · « **Reply #4 on:** February 21, 2008, 05:47:43 pm »

well I did as suggested as far as commenting out one of the raid items, but the bot.php error is also killing the bot, so not sure on that one.

Alreadythere · « **Reply #5 on:** February 21, 2008, 06:11:14 pm »

Quote from: clashbot on February 21, 2008, 02:03:57 am

"call to a member function connect() on a non-object in bot.php on line 237."

What am I doing wrong, and what can I do to fix it.

One of the modules you got has defined a $commands["connect"][] = &$module entry, but doesn't offer a connect() function. Check the modules with a line like that, if they don't have a connect() function in the object body simply comment the $commands["connect"] line out. Should solve that problem.

clashbot · « **Reply #6 on:** February 22, 2008, 12:57:20 am »

found the error and kicking my self with a very large boot, somehow in my enabling of raid mods and disabling the guild mods, I wound up enabling the examplemod.php. That was my problem with the command error. problem solved due to being over anxious on enabling things...