The $PerformAction function you are trying to step into is a C++ side function, not a GPL function so the debugger can 'step' into it. The debugger is just going to run that function and try to return to the debugger at the next GPL operation. However, that call you show is at the end of the function you are debugging. i.e. There are only 'end' opcodes, which can't be stopped on, so essentially, once you say Step Into on that $PerformAction, the debugger is not going to be able to stop until another GPL function is called, which is why you are seeing it stop on some other Ranger's function.

In answer to (2), pressing the Callstack button in the debugger shows how the function was called, with the current function at the top of the list and what called it below. The C++ side calls the script functions that are attached to the object, i.e. its "Activescript" so off the bottom of the list is "C++ code that called the script"

(3) seems like you want a new type of breakpoint, similar to pressing the | key when a unit is selected, but keeping the breakpoint active until you say otherwise. I will look into this.

(4) Once an agent's "ActiveScript" is set, it is not immediately run. The rest of the current function is run, then the "ActiveScript" will be run the next time the agent is given some processing time. So in your example, the whatever the agent's basicscript was pointing to will be run at the agent's next update cycle.

Are you making an override function for Berserk? You should just be able to make a new GPL file with something like this (I have'nt compiled it) and add it to your mod


You will probably have to override berserk_defend as well.

p.s. There seems to be a crash bug with the debugger if you try and use it again after starting a second game in the same session. I will fix it in the next update.

Thanks for taking a look. If you're poking around with the debug functions, could you just double-check whether DebugOut calls are showing up in the logs? Neither amantalado or I could get those to work last time I checked.

Originally posted by Alfryd:

Thanks for taking a look. If you're poking around with the debug functions, could you just double-check whether DebugOut calls are showing up in the logs? Neither amantalado or I could get those to work last time I checked.

It seems to be working for me. Do you have UseGPLDebugger set to 1 in your MajXPrefs? That needs to be on for the logging to be enabled. Do you see anything in the gpl.log file? The game should at least print out that it has started and will print the bytecode files it has loaded when you start a quest.

My PC's not usable at the moment, but I'll check it later this week once I have the mouse/trackpad sorted.

Yeah, I actually have UseGPLDebugger set to 1 along with UseDebugWindow, so in principle any log output is being flushed to the screen. Where would I normally find gpl.log?

Below is a sample of a simple adjustment I made to add log output to the Blessing spell, along with log output when I tried casting on a couple of passing henchmen. It doesn't look like the specific DebugOut arguments are showing up. Or am I doing something wrong?

https://s28.postimg.org/xrnmkkect/gpl_script_excerpt.png
https://s28.postimg.org/9zeb91cbv/debug_window_output.png

(Just to verify that the .gpl was being compiled correctly, I tried bumping up the dodge/parry etc. stat bonuses from the blessing spell itself, and that showed up in the game just fine. But no sign of DebugOut.)

Is that enough info to go on, or would you like me send on machine specs, etc.?

I think there was a separate thread for this bug, but unfortunately I've forgotten the title, so I'll just post these here:

https://s16.postimg.org/5wy1g74g5/error_1.png
https://s16.postimg.org/ipm5g4g1x/error_2.png