Skip to content

Conversation

@wookieejedi
Copy link
Member

#7051 cleaned up the bomb/bomber targeting function, but also specified arguments for TARGET_NEXT_CLOSEST_HOSTILE to make it internally consistent with TARGET_PREV_CLOSEST_HOSTILE. There was a typo though, and the second argument needs to be 1 and not 0. Having it be 0 makes 'Target Next Hostile' not work correctly.

Tested fix and confirms this restores proper behavior.

scp-fs2open#7051 cleaned up the bomb/bomber targeting function, but also specified arguments for `TARGET_NEXT_CLOSEST_HOSTILE` to make it internally consistent with `TARGET_PREV_CLOSEST_HOSTILE`. There was a typo though, and the second argument needs to be `1` and not `0`. Having it be `0` makes 'Target Next Hostile' not work correctly.

Tested fix and confirms this restores proper behavior.
@wookieejedi wookieejedi added this to the Release 25.0 milestone Jan 14, 2026
@wookieejedi wookieejedi added the fix A fix for bugs, not-a-bugs, and/or regressions. label Jan 14, 2026
@wookieejedi wookieejedi merged commit d9a6330 into scp-fs2open:master Jan 16, 2026
20 checks passed
@wookieejedi wookieejedi deleted the fix-target-next-hos-regression branch January 16, 2026 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix A fix for bugs, not-a-bugs, and/or regressions.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants