Quote:1) Displaying IF:M messages in a FU77006 trigger seems to screw up the SN:X parameters (stack and side) - maybe when I press Enter to end the display?

SN:X array of parameters is global. Key press event rewrites the parameters. Solution: save parameters first!

!?FU77006;
!!SN:X?v500/...;
...

Quote:2) Using the same yn or y-n variables in an FU77xxx trigger section as in another ERM trigger runs the risk that the values will change between the times when they are set in the other trigger and when they are used in that trigger. That is, an FU77xxx (or some of them) seems to be able to interrupt another trigger in progress without saving and restoring y-variables.

Valery, remember. Triggers don't save y-vars. Example:

!?CM2;
!!VRy1:S777;
!!HE0:Ed999999/d0; // trigger Level-up
!!IF:M^%Y1^;

!?HL-1;
!!VRy1:S666;

You should not include actions in triggers or your code is not safety. The solution:
!?...;
!!FU@My trigger handler@;

Functions have separate local vars and they are saved.

Quote:5) There are some DL command parameters used in the TPM script90.erm which are not mentioned in the ERM Help. For example, sometimes a 4th, "/1" parameter is used at the end of some commands for which only three parameters are shown in the ERM Help. (I added the /1 in some places and it seemed to help prevent crashes but that may have been a coincidence.)

Once MOP asked about the reasons of DL crash. I found out unmentioned parameter /1, which should always be used. Don't remember that command, but you'll find it, I think.