warrior player with clr bot.

[daerath]

Originally Posted by bad_captain

The code was in there, but was changed to only be cast by #bot command because people got tired of being turned into scarecrows..

Scarecrow is awesome! I spent weeks of playtime as one. =)

[secondattack]

rebuilt my DB, sourced all required updates from C:\EQEmuSVNFiles\EQEmu\trunk\EQEmuServer\utils\sql \svn going back to 1711, did every single required update, also sourced bots.sql from the same folder, it drops botinventory table and doesn't replace it... sourced it back in from C:\EQEmuSVNFiles\EQEmu\DB\peqdatabase\player_table s that's fine working as it should. but i still have the same problem. bots will not cast any spells, i have checked and double checked everything that has been asked, wtf am i doing wrong?

[secondattack]

ok i fixed it.. took me for ever but it works.

started with a fresh build for the 1751 DB, sourced anything that didn't say optional in the file name from C:\EQEmuSVNFiles\EQEmu\trunk\EQEmuServer\utils\sql \svn
went all the way back as far as i could, and sourced bot.sql from the same loc.
was banging my head against a wall there for awhile

[Huppy]

Originally Posted by secondattack

i play a warrior, i have a clr bot in tow. if i leave the bot on follow, he melees with me and never heals.. if i make him guard he does nothing.. how do i correct this? atm we are level 5

The only problems I ever had when testing out a cleric bot, when it wasn't
healing, I had to play with the spells, because it only casted a HoT all the
time. It seemed there was no direct heal, but eventually fixed that and
tested it out in Valdeholm. I just let the mob beat on me without fighting
back, and found the bot would only cast a direct heal after my health was
down to less than 50-60% (sometimes even got a exceptional heal)
But believe it or not the only other problem I noticed, was the heals were
as reliable as the "Sony Mercs" LOL. Once in awhile, it sat there and did
nothing, out of the blue ...

[daerath]

Got it working as well. I went through every update and examined the changes to ensure I wasn't going to break anything.

It turns out that was a good idea because a number of the updates will cause tables to be dropped and recreated, but you'll lose a lot of data in the process that the patch won't put back.

Here are the patch files I had to run.

1723_required_sql_corruption - Added this one manually because one of the entries already existed.
1736_optional_sql_feral_swipe
1737_required_sql_rule_and_aa_update
1753_required_sql_healing_adept_aa
1754_required_sql_healing_adept_aa_fix
1755_required_sql_fear_resist_aas
1786_required_update_to_aas
1790_required_aa_required_level_cost
1793_resist_adjust <-- This is probably the root cause (thanks bad_captain)
1803_required_tasks_xpreward_signed
1804_required_ae_melee_updates
1802_required_doppelganger - Change IDs to 682, 683, 684 and then run. You have to do this or it won't run successfully, and if you do, you can ignore 1813_required_doppleganger_npcid_change.

Thanks to bad_captain and Congdar for the advice!