T3 Mass Fabs: reduce death‑weapon blast radius

[NoryGit]

Description of the proposed changes

The blast radius of T3 mass fabs is 14, which is higher than that of T3 Pgens (10). This makes their explosion extremely deadly to gunships. Right now, players are forced to either avoid the blast radius (difficult) or micro the gunships around the mass fabs (often impractical). Their new blast radius is set to 8.

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 Changes
  • Reduced the area of effect for death weapons across four unit types. The damage radius has been decreased from 14 to 8, affecting the explosion footprint during combat.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request reduces the Death Weapon area of effect across four unit blueprints by decreasing the DamageRadius property from 14 to 8. Changes are applied to UAB1303, UEB1303, URB1303, and XSB1303 unit files.

Changes

Cohort / File(s)	Summary
Unit Death Weapon Damage Radius Adjustments units/UAB1303/UAB1303_unit.bp, units/UEB1303/UEB1303_unit.bp, units/URB1303/URB1303_unit.bp, units/XSB1303/XSB1303_unit.bp	Reduced Death Weapon DamageRadius from 14 to 8 across all four units, affecting the weapon's area of effect footprint.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• Rhaelya
• BlackYps

Poem

🐰 Hopping through blueprints with balance so keen,
Death Weapon radius—shrinking the scene!
From fourteen to eight, the numbers realign,
Four units now gleam with this tuning so fine,
This rabbit rejoices in gameplay delight! 🎮

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: reducing the death-weapon blast radius for T3 mass fabricators.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	PR description includes rationale for changes and confirms changelog was created, but reviewers were not requested as required by the checklist.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[BlackYps]

Hello, it's nice to see a new contributor!
We have a workflow to discuss changes that are not strictly bugfixes. We have the community suggestions channel on our discord (https://discord.com/channels/197033481883222026/1090315187397087362) to propose changes and to have them discussed. This is especially important for balance-related changes. Once an agreement has been reached, the implementation can follow.

[lL1l1]

I opened a community suggestion post for you on the discord: https://discord.com/channels/197033481883222026/1473802009265049682