05-29-2023, 09:00 AM
And to answer to myself:
-Maybe a simpler alternative to code for the first suggestion would be to store gear-config files (in yaml form or something like that) associated with bot names and that are editable (either via the add-on GUI but that would be hard to implement, or just via a text editor outside of the game) and that can be passed as arguments.
E.g.: I have a command ".partybot create " that creates an entry stored client-side which would probably be a simple yaml or json file containing:
name
class
spec
gear: {
1hweapon: XXX
etc...
}
Then I would have an alternative like .partybot recruit and would have the choice either to use .partybot add like currently for generically geared bots, and .partybot recruit that would transmit the information stored in the local file to the server to spawn the correct bot (possibly with a random seed added in the name to avoid duplicate names).
Then, anyone could have their own policy as to how they would gear their bot. In my case, my personal policy would be that when an item drops in a raid that I don't use, I would allow myself to change the configuration of one of my bots to include it in their gear preset if it improves it. The flexibility would also allow people to stuff their bots with gear that are not simply lootable (such as benediction, thunderfury etc...).
I think this approach, in addition to not changing the overall philosophy that you have put in place, has multiple advantages:
-doesn't put too much load on the server (since everything is stored client-side), apart from requiring it to use on-the-fly generated gear rather than a preset on your side. I'm guessing most people would still use presets anyway to avoid the hassle.
-isn't a "cheat" over the current because it's litterally a downgrade in all cases compared to BiS
-is extensible if you want to extense it one day (for example for talents or anything else)
-Maybe a simpler alternative to code for the first suggestion would be to store gear-config files (in yaml form or something like that) associated with bot names and that are editable (either via the add-on GUI but that would be hard to implement, or just via a text editor outside of the game) and that can be passed as arguments.
E.g.: I have a command ".partybot create " that creates an entry stored client-side which would probably be a simple yaml or json file containing:
name
class
spec
gear: {
1hweapon: XXX
etc...
}
Then I would have an alternative like .partybot recruit and would have the choice either to use .partybot add like currently for generically geared bots, and .partybot recruit that would transmit the information stored in the local file to the server to spawn the correct bot (possibly with a random seed added in the name to avoid duplicate names).
Then, anyone could have their own policy as to how they would gear their bot. In my case, my personal policy would be that when an item drops in a raid that I don't use, I would allow myself to change the configuration of one of my bots to include it in their gear preset if it improves it. The flexibility would also allow people to stuff their bots with gear that are not simply lootable (such as benediction, thunderfury etc...).
I think this approach, in addition to not changing the overall philosophy that you have put in place, has multiple advantages:
-doesn't put too much load on the server (since everything is stored client-side), apart from requiring it to use on-the-fly generated gear rather than a preset on your side. I'm guessing most people would still use presets anyway to avoid the hassle.
-isn't a "cheat" over the current because it's litterally a downgrade in all cases compared to BiS
-is extensible if you want to extense it one day (for example for talents or anything else)

