Ah the debugging code is turned on.
The timer trap is based off of your macro runtime, since that is in minutes.
Example: 91.10 Go:93.3
This means that at this point your macro has been running for 91.1 minutes once the runtime hits 93.3 minutes then the timer trap is over. From this I can tell that you started this part of the loop after your macro had been running for 78.2 minutes.
The timer isn't compounding.
Rich (BB code):
Line 248: /varset TMR_TaskStart ${Math.Calc[${Macro.RunTime}/60]}
For the example above TMR_TaskStart == 78.2
This is called right before the the /doevents picks the task.
Once the task is completed we /call TimerTrap.
Rich (BB code):
Line 292: /varset TMR_GoTask ${Math.Calc[${TMR_TaskStart}+15.10]}
The SOE lockout timer is 15min. So now that the task is over we need to add the 15min to time that we started the task. Using the example the lock timer should be over when the runtime clock hits 93.3.
The macro then does a runtime check every 10 seconds and then continues when ${Math.Calc[${Macro.RunTime}/60]} >= ${TMR_GoTask}
I have commented out the debugging code. If you are running a HUD that shows your macro runtime all of this is more clear. I had the debugging code spew out the time checks so I could compare them to my HUD, and make sure that it acutally kicked off after the 15.1min timer.
I am posting a new ZIP right now without the debugging code and Sorenbro's RWarp/Piggyzone.ini files.