EQoffline, bots and more..

[Magoth78]

It's 992, yes.

[drakelord]

Alright, something is definately not loading correctly.

In the database, the bots "npc_spells_id" is set to 600.
600 is the number of the npc_spells field created for the druid bot.
In npc_spells_entries, the spells are selected.

The bot is loaded and updated, and with #bot debug spells, he is showing spells that are not even on my list. Does it not actually use the npc_spells_id field in the database?

[Magoth78]

To be sure that it's loading your spells, target your bot and do "#ai spellslist 600".

[drakelord]

Sweet, it worked.

Now, next couple things, :3; First off, is there a way to get a bot to cast DoT's before it casts it's direct damage spells?

Also, how can I increase the casting rate in the source code?

[John Adams]

Might require some manual effort on your part, but I believe the npc_spell_entries table has a "priority" field. If it does what I think, the NPC should cast it's spells in the order of priority. I haven't tested this, but it would make sense.

You know how some NPCs pop, and immediately start buffing themselves or summon pets... I think this is what controls that.

[Zengez]

I May be totally off target but I thought I read somewhere that that field governed some weird idea about how many times the npc casts that in a given amount of time... i.e. if priority is 5 then the npc casts that spell 5 times per however long that time period is...

That could be dating myself though and not have been true since the dawn of time, but I remember that from somewhere if it matters... My server is down though so no ability to test it unfortunately.

[John Adams]

I wouldn't be the least bit surprised if a field aptly named "priority" ended up having nothing whatsoever to do with prioritizing what order to cast, but quantities of casts.

Considering I am still wrestling with understanding conditional spawns...