by all good means, but it wasn't specific, and it isn't yet
The API could be wrapped into some classes, no problem at this point. but the usage (u say for grouping, but where should this grouping be done ... plugin?botbase?cc?) is unclear and the benefit too.
While botting:
- we need no ReadyCheck
- we need no Promote Leader
- we need no remove player (as we can't really decide if a player is useful for us)
If u wanna use it as Plugin (cause u can't directly advance the function / methods / properties of partybuddy) u can do all the stuff u need much much easier. The many functions aren't needed
U need a communication between the bots, and not displaying all possible party / raidfunctions
U need to cover some things like questing for the party
U need to cover some boss logics for raidings
U need to cover some BG Logics for PVPing
But u do not need all the Party-Functions
So pls be a little bit more specific what u wanne do... from your current explanations most of this stuff is obselete / not usable / not needed.
Sure it's fine to cover all these things, but i, for myself, couldn't see anything where i could benefit from these things.
PartyBuddy doesn't provide enough functionality, DungeonBuddy2 isn't released yet, BGBuddy does not support things like that
So it is absolutely unclear what u wanna do with that
Don't get me wrong, i'm a fan of developing something, and i played often with the thoughts in developing a raidingbuddy for NH and Heroics, but even there i don't need to cover the complete Party-Api ... i do not need ready checks (except i would write (or someone wanna write) CCs for every Class / Specc which supports this api to group a party of bots for raiding / pvping / etc)