TM,
I am working on using the travel subs in a bod fetching script. It logs onto multiple accounts/characters and runs to get bods with them.
I have it resetting the underscore sub with each toon, have all of the journal subs in and unless I get a fizzle, it runs fine. If it fizzles on a recall the script doesn't pick it up and it hangs. It does recognize a blocked location and will select the alternate rune. I think I have isolated the issue at the journal scan after the target in the spellcast sub by putting in a couple of event msg notes as follows.
NewCastSpell_skip2:
if !whichspell >= 0 && !whichspell <= 63 ; Magery
{
gosub TM_AdvJournalScan SPELLCAST VALID spell_fizzles there_is_already mana your_spirit more_reagents
}
else
{
set !cont #FALSE ; Chivalry, Necromancy, etc
finditem !whichtarget *
if !whichtarget in SELF_NONE || #FINDKIND <> -1
set !cont #TRUE
if #MANA >= !tempmana && !cont = #TRUE ; check if target is still there
set #RESULT #TRUE
else
set #RESULT #FALSE
}
repeat
until #SCNT2 > !casttimeout ; finish up cast delay
if #RESULT = #TRUE
{
event exmsg #charid 3 4 Journal scan picked up a fizzle and should head to recast
if !castretrymax > -1
{
set !castretry !castretry + 1 ; %castretrymax of -1 will cast until successful
if !castretry > !castretrymax
goto NewCastSpell_end1
}
goto NewCastSpell_loop1
}
event exmsg #charid 3 4 Journal scan was negative for fizzle, script will continue
if #SCNT2 <= !casttimeout ; finish up cast delay
goto NewCastSpell_skip2
I am thinking that my data feed to the travel subs must be good as its picking up the blocked location, but if that is the case, then I am not sure why it isn't catching the fizzle unless it is just going too fast. I am going to add a wait 5 in front of the journal check and see if that makes a difference. I suspect I am missing something though...
A wait didn't make a difference, so I am pretty sure I have something wrong with the journal scanner setup.