Supports the runtime with /callee

[EvilDragonfiend]

About The Pull Request

Supports the runtime with /callee byond native type

Why It's Good For The Game

Good for debug

Testing Photographs and Procedure

Screenshots&Videos

Changelog

🆑
code: all runtime details fully describe the proc call flow
qol: Runtime window is now bigger for the readibility.
/:cl:

[EvilDragonfiend]

DNM until this is fully clean. You may TM this for your good for now.

[EvilDragonfiend]

To-do:

• listify - direct string management seems to be slow
• a all-in-one data investigator proc
• some clean up for debug only

[LemonInTheDark]

you are not allowed to call procs (which english_list) is in this portion of error handling code (due to problems with infinite recursion). Unless that issue has been fixed, which we have yet to establish (lummox tried? he's quite vague in the post) you need to move this below the if block that handles infinite recursion

[EvilDragonfiend]

I am not sure what the issue is here. I haven't found any issue here locally.

[LemonInTheDark]

the thought is if a proc infinite recurses and gets killed by the stack depth limit, then we're like, already at the bottom of the stack when Error is called to report that. It isn't exempt from those rules.

it used to be attempting to call a proc in this situation would just kill the proc stack entirely, which is obviously bad. lumlum recently said he "fixed" this by adding an extra allotment of "space" for Error to use. this is what I'm referring to when I say we need to like, work out what that actually means.

[EvilDragonfiend]

I suppose it seems to be okay..?

[LemonInTheDark]

it's a little unclear to me what this does for us exactly, is this meant to help with really deep runtimes?

[EvilDragonfiend]

it's a little unclear to me what this does for us exactly, is this meant to help with really deep runtimes?

Yes, it is.

Click to open - Screenshots

When CRASH() is called, but the tracy is not elaborating enough in Initialize()

You can see how subtype procs have been called.

When stack_trace() is called

When the runtime even doesn't describe any tracy

When a loop from Master Controller has been detected

When a loop-failsafe has been made

Upon roundjoin - Topic is elaborated

[LemonInTheDark]

wait fuck this is beestation how did I end up here

[Tsar-Salat]

wait fuck this is beestation how did I end up here

welcome to our dark and twisted server, fruitman

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.