We updated Trace which TRACE_1, TRACE_2, TRACE_3 are 32bit, TRACE_4, TRACE_5 & TRACE_6 are 16 bit.
Here is an example, of TRACE_2 32-bit:
Example using TRACE_1 thru TRACE_6.
What are traces and what do they do?
Traces are boxes of information commonly used to debug a gpc, get the information you may want from a game or get information from mods that may be running, and more. When in Zen Studio simply click Tools > Device Monitor or press the shortcut F3 on your keyboard. This will bring up Device Monitor where traces can be seen on the bottom right of the Device Monitor.
Here is where information will be displayed depending on how you have traces set in a gpc script. The example below is an example of using a trace to verify if a combo is running. When the combo is running the value of trace 1 is 1 and when the mod is off the value of trace 1 is 0.
In the GIF below we can see that the value of trace 1 is going quickly between 1 and 0. Due to the nature of the combo being re-run while the right trigger is being held this is normal and what to look for when using a trace to verify the combo is running. When the right trigger is not held the right trigger has a value of 0 and thus the value of the trace is 0 and with this information, we can determine the combo is running when it should be.
In this example is code of a basic dynamic Anti Recoil which takes advantage of the higher value limits of 32bit to scale a value up then back down to be accepted as a value to be used with a polar constant for a much greater degree of accuracy. The value being traced is the radius of the right stick scaled up higher before being scaled back. As the right stick is moved the value of the trace changes accordingly.