You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that my issue may get closed without notice if I intentionally remove or skip any mandatory* field
This is NOT a bug/crash report
I've searched the bugtracker for similar questions/requests including closed ones
Description
Just a suggestion.
Bots are OP in BGS as they stand, they have to be nurfed through the settings to make them killable.
What if they can accumulate Honor every time they are used in a BG, and the Honor determines the gear/power they have in a BG? (via kills like a player, or just a simple # of Honor each time they are used, and the power is a percentage of the MAX power) Once they max out, they can reset after a certain number of times being used at that level, ensuring a rotation of bots and all bots dont max out. I understand this would require two more fields in the SQL table (something like Honor Points and MaxPlays) Possible Starting Honor could be random amounts with the bots (%'s) when first implemented.
This can all be nurfed or empowered via the config as it is now.
The text was updated successfully, but these errors were encountered:
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Description
Just a suggestion.
Bots are OP in BGS as they stand, they have to be nurfed through the settings to make them killable.
What if they can accumulate Honor every time they are used in a BG, and the Honor determines the gear/power they have in a BG? (via kills like a player, or just a simple # of Honor each time they are used, and the power is a percentage of the MAX power) Once they max out, they can reset after a certain number of times being used at that level, ensuring a rotation of bots and all bots dont max out. I understand this would require two more fields in the SQL table (something like Honor Points and MaxPlays) Possible Starting Honor could be random amounts with the bots (%'s) when first implemented.
This can all be nurfed or empowered via the config as it is now.
The text was updated successfully, but these errors were encountered: