Open Purple-23 opened 2 weeks ago
Another half-assed solution is to disable the class altogether. Disabled classes will not get selected for wandering bot generation.
I don't think I'll do this per level bracket.
Yeah I was hoping to still have them for hiring at the vendor bot.
I wrote a script in SQL I thought would work in clearing the wandering table of premade bots and then I could manually add in like 5 but it didn't work.
DELETE FROM creature_template WHERE name LIKE '%Death Knight Bot%'; UPDATE creature_template SET ScriptName = '' WHERE ScriptName = 'death_knight_bot';
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that my issue may get closed without notice if I intentionally remove or skip any mandatory* field
- [x] This is NOT a bug/crash report
- [x] I've searched the bugtracker for similar questions/requests including closed ones
Description
You can already split number of wandering bots (total) by percentage in level bracket, but it would be cool to break down by classes. Say, I don't want any DKs at all, it would be cool to remove them from the wandering table entirely. Or if at the early 0-10 levels, only see a couple warriors.
Best I can think of, now, is manipulating the SQL tables which is a lot of work.
TrinityCore or AzerothCore
AzerothCore
Core rev. hash/commit
No response
Operating system
Win11
Does this is not enought for you?
NpcBot.Classes.
There is already settings present where turn on/off class
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Description
You can already split number of wandering bots (total) by percentage in level bracket, but it would be cool to break down by classes. Say, I don't want any DKs at all, it would be cool to remove them from the wandering table entirely. Or if at the early 0-10 levels, only see a couple warriors.
Best I can think of, now, is manipulating the SQL tables which is a lot of work.
TrinityCore or AzerothCore
AzerothCore
Core rev. hash/commit
No response
Operating system
Win11