So for EN and anyone else interested... I've figured out how I wanted to do my journal update wait.
If TM's sub is the "Advanced," version... then this is the "get a bigger hammer" remedial version of journal scanning:
event sysmessage mining at Book %bookcnt Rune %runecnt Vein %onvein
finditem %digtools * c_ , #backpackid
set #lobjectid #findid
set %jupdate #jindex + 1
event macro 17 0
target
event macro 22 0
set %digwaitbegin #systime
...
jup:
scanjournal #jindex
if There_is_no in #journal
{
if #weight > %nrweight && %onvein = %veincnt && %stripmine = no
{
gosub travel home
gosub secops
}
set %stopdigging now
goto stopdigging
}
if You_have_worn in #journal
{
gosub checkingots
gosub tinker shovel
}
if That_is_too in #journal || Target_cannot in #journal
{
event sysmessage Whoops, travel broke... HOLD ON
gosub travel nextrune %runecnt
set %stopdigging now
goto stopdigging
}
set %endcheck #systime - %digloopwaitcheck
set %digwaitend ( #systime - %digwaitbegin )
if %digwaitend > 300 && %endcheck > 980
{
;event sysmessage %digwatend | %endcheck
goto keepdigging
}
goto jup
The only way I've broken it so far is if I spam event sysmessages during the update loop... I believe it should be fast enough to read through the global chat spam on my server... and if not, I'll just turn global chat off...
*edit* oh, and by moving to scanjournal dependant catches, I was able to improve my move to nextvein rate by about 30%... it catches the "no_metal" at about an average of 200ms (was a "wait 6..." ~315ms), and moves to the nextvein at an average of about 650-750ms.
Pretty happy with the results