Bots don't zone
 

Hi,

Currently pulling a fresh svn 2282 from trunk, compiling in 2010 express configured with Release X64/RelaseBots X64. Applied all .sql updates in trunk from 2214-2280. Started with peqdb 2214.

Problem: Create a bot, try to zone with it. After you zone the bot shows as in group in the group panel but it looks like its either in another zone or dead. #bot spawn will bring them back.

I have looked through botsandmercs branch to see if any fixes exist, running out of ideas, anyone have any?? Thanks.

There is nothing in debug file and the following is only zone errors..

[12.08. - 12:13:49] Starting Log: logs/eqemu_error_zone_3608.log
[12.08. - 12:13:49] Warning: charid 1 has an invalid item_id 150009 in inventory slot 15
[12.08. - 12:13:59] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 4112
[12.08. - 12:13:59] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 4112
[12.08. - 12:14:01] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 1
[12.08. - 12:14:01] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 4
[12.08. - 12:14:01] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_TargetMouse (#125 eq=0x0000), size: 4

BotsAndMercs is an experimental branch. Use the main branch for bots.

Yah i didn't phrase that very well. I did in fact build from the main branch with bots option, not the botsandmercs branch. I meant to say i was desperate so i went looking in there to see if i could find any fixes.

Thank you for the reply thou, any other suggestions?

Are you getting this in every zone or just certain ones?

Sorry, this was a sql issue. I did not follow the directions properly. Once i resourced DB properly(using load_bots.sql at right time), bots seem to work fine. Sorry for false alarm.

ive had this issue in the past but i didnt realize it was due to not sourcing the sqls in the right sequence, thats good to know, thanks for posting how you solved this