Author Topic: Useing Trace(1);  (Read 530 times)

I've heard about it so I tryed it. All I got was 50 pages of console spam.

It basically shows the structure of all functions being activated. Not specific ones. Every single function that is called, Trace shows it, indented, and when that function ends. All functions called inside of it, etc. so you can see vaguely how certain things work and determine what's happening.

Not something to leave active for any length of time.

If you have any mods with repeatedly called functions (e.g. the Portal Gun), are using rapid-fire weapons, lots of events at once or move the mouse when running trace(), you'll get spam.

If you have any mods with repeatedly called functions (e.g. the Portal Gun), are using rapid-fire weapons, lots of events at once or move the mouse when running trace(), you'll get spam.
The RtB IRC will also shoot off several lines every time a message is recieved. Also, Badspot should have it filter the mouse movement out when using trace.

The RtB IRC will also shoot off several lines every time a message is recieved. Also, Badspot should have it filter the mouse movement out when using trace.
Or just plain make it so we can have a custom-filter.

Trace works much better when you use it on a clean install of Blockland.

Oh, and even some useful stuff comes out on 50 pages. 50 pages can mean a lot, spam or not.
You just need to be patient.