I like what you've done with the ARCHTYPEs. I had been considering doing something similar, but I wouldn't have time to start for a few weeks and I don't know enough C, so I couldn't do much more than pseudo-code anyway. That being said, I thought I'd throw this idea out there in case anyone was interested until I have time to work on it further:
The idea is roughly similar to ARCHTYPE changes, but it allows for a little more fine tuning from the client. Basically, I though it would be nice to have bot commands that lets the user assign roles in the group. For example:
#bot group assign tank OR #bot group assign healer (or maybe better: #bot group assign primehealer/secondhealer)
The AI could then take these roles into consideration. Let's say you have a group with a cleric and a druid. If you assign the cleric as primary healer and the druid as the secondary healer, the druid could spend more mana nuking and not worry as much about heals, while the cleric will always be sure to save some mana for heals. (for example, maybe the secondary healer will nule to 25% mana but the primary healer will never nuke below 50m) Or a group might want to have the cleric heal while the shaman debuffs, etc.
It might also be helpful to assign melee roles. If there's a primary tank, other melee bots would be careful not to steal aggro. This might also make enchanters easier to code. If the chanter has been given the crowd control role (or maybe it has that role by default), it can try to mez any aggro'd mobs except the one the assigned Tank is targeting. It could also help healing - primary healer focuses on primary tank while secondary healer heals other group members.
Like I said, in a couple weeks I'll gladly try to work out some of the AI (although most of my experience is with monks), but since the ARCHETYPEs mentioned in this thread were somewhat similar, I thought I'd throw this out there now
|
Threaded Mode
