Skip to content

Conversation

mastercoms
Copy link
Contributor

@mastercoms mastercoms commented Sep 16, 2025

Use the provided utility functions for trigger_hurt and respawn room to determine the relevance of the trigger, rather than doing a broader, incorrect bounds check. This takes into consideration all the relevant conditions for each respective trigger to be valid, and checks if the currency's point is truly within the trigger.

This fixes an error where some maps with more complex geometry for their triggers will cause a currency pickup in random locations, which was exacerbated by #618, which added respawn rooms to the logic.

Use the provided utility functions for trigger_hurt and respawn room to determine the validity of the trigger, rather than doing a broader, incorrect bounds check.
@HyperionCoding
Copy link

#1307 duplicate

@mastercoms
Copy link
Contributor Author

mastercoms commented Sep 16, 2025

#1307 duplicate

That PR differs with this one, this PR uses the shared utility functions and does not do other changes.

Bitl added a commit to BitlDevelopmentStudios/source-sdk-2013-bds-base that referenced this pull request Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants