Buff Mercy BT

[Isocinetic]

Description of the proposed changes

Mercies can be a highly effective unit, however their hyper-specialization means that their application is narrow as well, including timeframe usage. It's hard to get enough mercies to make enough impact. It's especially true since big T2 air stage is less common than say big T2 land stage. And by the T3 stage mercies are usually obsolete. All this factors put a big constraint on volume of mercies' production.

Current Mercy mass production drain is 7.6 m/s compared to 10.8 m/s when producing beetles (after recent beetle BT nerf). We would reduce BT time 1200-> 800-900. This would put mercies production mass drain one tier above t1/t2 bombers but within the same category as beetles.

Making more mercies when needed would allow to spam enough mercies to be and feel impactful on the battlefield without directly buffing the unit itself.

Additional context

Discord balance thread discussion

Checklist

• Changes are annotated, including comments where useful
• Changes are documented in a changelog snippet according to the guidelines.
• Request 2-3 reviewers from the list of reviewers and their areas of knowledge.

Summary by CodeRabbit

• Balance Adjustments
  • Reduced Mercy unit build time for faster production and improved combat readiness

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR applies a balance change to the Mercy unit, reducing its BuildTime economy cost from 1200 to 800, with an accompanying changelog entry documenting the adjustment. The PR also updates deployment metadata to identify the game type as "FAF" with a specific commit hash, and adjusts debug output flags to disable spewing, logging, warnings, and drawing while preserving error reporting.

Changes

Mercy Unit Balance & Deployment Update

Layer / File(s)	Summary
Unit Balance Change units/DAA0206/DAA0206_unit.bp	Mercy unit BuildTime reduced from 1200 to 800.
Balance Changelog changelog/balance.7112.md	New changelog entry documents Mercy BuildTime cost reduction (1200 → 800) for issue #7112.
Deployment Metadata & Debug Configuration lua/version.lua, lua/shared/components/DebugComponent.lua	Version GameType set to "FAF" with commit hash 2ae081b063aba82df3c679780f0ba8460e06a63e; debug flags (spewing, logging, warnings, drawing) disabled while error reporting remains enabled.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• FAForever/fa#7047: Both PRs modify version and changelog-related files, including updates to lua/version.lua and changelog entries.

Poem

🐰 Mercy swift now costs less time,
From twelve to eight, a cleaner rhyme,
With changelogs and versions bright,
The payload's ready, packaged right! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Buff Mercy BT' is concise and directly describes the main change—reducing build time for the Mercy unit to increase production volume.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description explains the rationale and context well, but the required checklist items are not completed and no reviewers were explicitly requested.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

changelog/balance.7112.md (1)

1-1: 💤 Low value

Consider minor grammar improvements for clarity.

The description is clear but could be more polished:

• "to allow spam enough mercies" → "to allow spamming enough Mercies" or "to enable producing more Mercies"
• "to deal impact" → "to make an impact" or "to have meaningful impact"

✍️ Suggested grammar refinements

-- (`#7112`) Mercy receives BT cost reduction to allow spam enough mercies to deal impact on the battlefield.
+- (`#7112`) Mercy receives a Build Time reduction to enable producing enough Mercies to make an impact on the battlefield.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@changelog/balance.7112.md` at line 1, Update the changelog entry text
"(`#7112`) Mercy receives BT cost reduction to allow spam enough mercies to deal
impact on the battlefield." to improve grammar and clarity: replace "to allow
spam enough mercies" with either "to allow spamming enough Mercies" or "to
enable producing more Mercies" and replace "to deal impact" with "to make an
impact" (e.g., "(`#7112`) Mercy receives BT cost reduction to allow spamming
enough Mercies to make an impact on the battlefield.").

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@lua/shared/components/DebugComponent.lua`:
- Around line 34-38: Revert the debug flag flips in DebugComponent by restoring
the prior default values for EnabledSpewing, EnabledLogging, EnabledWarnings,
and EnabledDrawing (i.e., re-enable them) while keeping EnabledErrors as-is;
find the DebugComponent table/definition that contains the fields
EnabledSpewing, EnabledLogging, EnabledWarnings, EnabledErrors, and
EnabledDrawing and change those four flags back to their previous true/default
settings so this PR only contains balance changes, not global observability
changes.

In `@lua/version.lua`:
- Around line 31-33: The inline comments stating "The use of `'` instead of `\"`
is **intentional**" next to the GameType and Commit declarations (symbols
GameType and Commit) are incorrect and misleading because the code uses double
quotes; remove or update those comments to reflect the actual usage (e.g.,
delete the quote-note or change it to say that double quotes are used
intentionally) so the declaration lines for GameType and Commit match the
comment text.
- Around line 31-33: The PR only updates deployment metadata (GameType and
Commit in lua/version.lua) but does not implement the promised Mercy BuildTime
buff; update the actual unit blueprint instead: locate the Mercy unit definition
(unit blueprint file in units/ or similar containing the Mercy unit's BuildTime
field), change its BuildTime from 1200 to the target 800–900 value, add a short
changelog entry referencing the Mercy BuildTime change, and remove any
accidental CI-only edits to GameType/Commit so the PR contains only functional
changes for the Mercy unit (use symbols: GameType, Commit to identify the
unrelated metadata and the unit blueprint's BuildTime field to apply the fix).

---

Nitpick comments:
In `@changelog/balance.7112.md`:
- Line 1: Update the changelog entry text "(`#7112`) Mercy receives BT cost
reduction to allow spam enough mercies to deal impact on the battlefield." to
improve grammar and clarity: replace "to allow spam enough mercies" with either
"to allow spamming enough Mercies" or "to enable producing more Mercies" and
replace "to deal impact" with "to make an impact" (e.g., "(`#7112`) Mercy receives
BT cost reduction to allow spamming enough Mercies to make an impact on the
battlefield.").

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 43b0913d-b7a2-41cf-b1f4-fc28adb9c213

📥 Commits

Reviewing files that changed from the base of the PR and between 714ea80 and 9f5b68d.

📒 Files selected for processing (4)

• changelog/balance.7112.md
• lua/shared/components/DebugComponent.lua
• lua/version.lua
• units/DAA0206/DAA0206_unit.bp