Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Balance]: Support response ramp is faster than intended #3385

Closed
jaj22 opened this issue Aug 21, 2024 · 0 comments · Fixed by #3386
Closed

[Balance]: Support response ramp is faster than intended #3385

jaj22 opened this issue Aug 21, 2024 · 0 comments · Fixed by #3386
Labels
Balance For issues and PRs regarding game balance.
Milestone

Comments

@jaj22
Copy link
Collaborator

jaj22 commented Aug 21, 2024

The support system uses this calculation as an element to determine how many resources to spend on a support response:
(2*recentDamage + enemyStrength) / friendStrength

Because recentDamage also reduces friendStrength, this calculation scales to the maximum value of 2 (meaning send the maximum allowed for this location) excessively quickly. As an example, a garrison might have 400 defence strength, with 100 strength of attackers. After 10 garrison kills (100 strength), the result reaches 1.0, or the minimum response level. The maximum response is reached at only 18 garrison kills, or less than half of the garrison, frequently not long after the minimum response. Hence multiple QRFs or other supports may be sent within a short time. Ideally the maximum response would be reached at closer to 2/3 deaths in this case.

@jaj22 jaj22 added the Balance For issues and PRs regarding game balance. label Aug 21, 2024
@Bob-Murphy Bob-Murphy added this to the 3.8.0 milestone Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Balance For issues and PRs regarding game balance.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants