Port recursion limit error handling from TG#5273
Merged
MistakeNot4892 merged 1 commit intoNebulaSS13:devfrom Jan 14, 2026
Merged
Port recursion limit error handling from TG#5273MistakeNot4892 merged 1 commit intoNebulaSS13:devfrom
MistakeNot4892 merged 1 commit intoNebulaSS13:devfrom
Conversation
out-of-phaze
force-pushed
the
fix/recurse-error
branch
from
a4a08eb to
0f3bc11
Compare
MistakeNot4892
approved these changes
Jan 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
ports tgstation/tgstation#92251
tl;dr: trying to call a non-builtin/byond proc in world/Error when we hit the recursion limit will abort the proc causing a log failure
tested on #5271, it worked to catch the issue.
Why and what will this PR improve
actually log infinite recursions
Authorship
LemonInTheDark at TG