Skip to content

Conversation

@Baezon
Copy link
Member

@Baezon Baezon commented Jan 2, 2026

"why didn't it fire?" Because object creation should always be assumed fallible, the designer can throw a million things around; there may be not slots available despite the code's best efforts.

Nothing cares about shockwave_create's return, and only the single spot which was edited cares about beam_fire_targeting()'s return, so the relevant Int3's were removed. In both cases the problem is logged if the designer/coder wants to investigate further, but it's no reason to bring debug builds to a halt.

Other object creations, such as ships, are assumed infallible but it would be a larger effort to ensure the rest of the code is properly prepared for its fallibility.

@Baezon Baezon added fix A fix for bugs, not-a-bugs, and/or regressions. Waiting for Stable Marks a pull request that is to be merged after the next stable release, due to a release cycle labels Jan 2, 2026
@Goober5000 Goober5000 added the Point Release Candidate An already merged bugfix that may be merged into a previous stable version label Jan 3, 2026
@wookieejedi wookieejedi added this to the Release 25.0.1 milestone Jan 12, 2026
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. Point Release Candidate An already merged bugfix that may be merged into a previous stable version Waiting for Stable Marks a pull request that is to be merged after the next stable release, due to a release cycle

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants