Skip to content

bugfix: Contact weapons are no longer blocked by obstacles #3194

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.

Sign up for GitHub

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

Open
Stubbjax wants to merge 3 commits into
base: main
Choose a base branch
from
+19 −0
Open

bugfix: Contact weapons are no longer blocked by obstacles #3194

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
592e43e
bugfix: Contact weapons are no longer blocked by obstacles
Stubbjax Aug 23, 2026
d5c5069
chore: Expand condition coverage
Stubbjax Sep 2, 2026
7f170b2
docs: Add comments
Stubbjax Sep 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions Core/GameEngine/Source/GameLogic/AI/AIPathfind.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9576,6 +9576,13 @@ Bool Pathfinder::isAttackViewBlockedByObstacle(const Object* attacker, const Coo
}
if (w)
{
#if !RETAIL_COMPATIBLE_CRC
// TheSuperHackers @bugfix Stubbjax 23/08/2026 Don't consider the attack blocked if it is a contact weapon.
// This allows weapons such as suicide bombs to be triggered if the unit is blocked by building geometry.
if (w->isContactWeapon())
Comment thread
xezon marked this conversation as resolved.
return false;
#endif

Bool viewBlocked;
if (victim)
viewBlocked = !w->isClearGoalFiringLineOfSightTerrain(attacker, attackerPos, victim);
Expand Down
6 changes: 6 additions & 0 deletions Generals/Code/GameEngine/Source/GameLogic/Object/Update/AIUpdate.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3399,7 +3399,13 @@ void AIUpdateInterface::privateAttackPosition( const Coord3D *pos, Int maxShotsT
// this fixes an obscure bug with mine-clearing: if you tell someone to clear mines and put the centerpoint
// inside a building, the dozer/worker will just go thru the building to that spot. ick. so if you find that
// this clause (below) is problematic, you'll probably have to find another way to fix this mine-clearing bug. (srj)
#if RETAIL_COMPATIBLE_CRC
if (weapon && weapon->isContactWeapon() && !isPathAvailable(&localPos))
#else
// TheSuperHackers @bugfix Stubbjax 23/08/2026 Only find a new position if the target is not within the attack range of the weapon.
// This allows contact weapons such as suicide bombs to immediately detonate without first pathing to a nearby position.
if (weapon && weapon->isContactWeapon() && !weapon->isWithinAttackRange(getObject(), &localPos) && !isPathAvailable(&localPos))
#endif
Comment on lines +3402 to +3408

@qodo-free-for-open-source-projects qodo-free-for-open-source-projects Bot Aug 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

3. Unpathable contact target preserved 🐞 Bug ≡ Correctness

privateAttackPosition now skips the “find a nearby pathable spot” adjustment for contact weapons
if isWithinAttackRange() is true, even when isPathAvailable() is false. Combined with the LOS
bypass, this lets a unit execute a contact attack on an explicitly unpathable goal point (e.g.,
inside blocking geometry) as long as it can get within range outside the obstacle.
Agent Prompt 
### Issue description
The new condition in `privateAttackPosition()` bypasses the existing safety behavior for contact weapons (“must be able to path to the target pos”) whenever the attacker is merely within attack range, even if the goal point is unpathable.

### Issue Context
`Weapon::isWithinAttackRange(source, pos)` is distance-only, while the comment/behavior here is about reachability/pathing. For contact weapons, “within range” can still be on the other side of a blocking obstacle.

### Fix Focus Areas
- Generals/Code/GameEngine/Source/GameLogic/Object/Update/AIUpdate.cpp[3398-3415]
- GeneralsMD/Code/GameEngine/Source/GameLogic/Object/Update/AIUpdate.cpp[3553-3561]
- Generals/Code/GameEngine/Source/GameLogic/Object/Weapon.cpp[2056-2070]

### Suggested direction
Only skip the `isPathAvailable()`/fallback relocation when the unit is effectively already at the target point (very small positional epsilon), rather than when it is merely within attack range.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@xezon xezon Sep 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about this comment from the Ant Eater?

{
FindPositionOptions fpOptions;
fpOptions.minRadius = 0.0f;
Expand Down
6 changes: 6 additions & 0 deletions GeneralsMD/Code/GameEngine/Source/GameLogic/Object/Update/AIUpdate.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3554,7 +3554,13 @@ void AIUpdateInterface::privateAttackPosition( const Coord3D *pos, Int maxShotsT
// this fixes an obscure bug with mine-clearing: if you tell someone to clear mines and put the centerpoint
// inside a building, the dozer/worker will just go thru the building to that spot. ick. so if you find that
// this clause (below) is problematic, you'll probably have to find another way to fix this mine-clearing bug. (srj)
#if RETAIL_COMPATIBLE_CRC
if (weapon && weapon->isContactWeapon() && !isPathAvailable(&localPos))
#else
// TheSuperHackers @bugfix Stubbjax 23/08/2026 Only find a new position if the target is not within the attack range of the weapon.
// This allows contact weapons such as suicide bombs to immediately detonate without first pathing to a nearby position.
if (weapon && weapon->isContactWeapon() && !weapon->isWithinAttackRange(getObject(), &localPos) && !isPathAvailable(&localPos))
#endif
{
FindPositionOptions fpOptions;
fpOptions.minRadius = 0.0f;
Expand Down
Loading