Rollover Management

Hi, Thanks so much for this script. I love it and use it every day.
Today I have been getting the following message and the script will not run.

Cannnot apply operator && to ( have_familiar() && have_familiar() ) (boolean) and get_property() (string) (Rollover Management.ash, line 73)

The below shows each time also, but doesn't seem to cause a problem. Just thought I would include it while I was here. :)

Changing "Miniature Sword & Martini Guy" to "Miniature Sword & Martini Guy" would get rid of this message (Rollover Management.ash, line 60)

Thanks again, TaPol :D
 
TaPol said:
Cannnot apply operator && to ( have_familiar() && have_familiar() ) (boolean) and get_property() (string) (Rollover Management.ash, line 73)

Changing "Miniature Sword & Martini Guy" to "Miniature Sword & Martini Guy" would get rid of this message (Rollover Management.ash, line 60)
Click to expand...

The problem should be fixed.

The Miniature Sword & Martini Guy is a mafia issue. It has been discussed in this forum already.
 
Not sure if this is still being maintained or not, but it's been a lifesaver so thank you! I noticed one strange bug that literally just started for me in the last few days. The script no longer seems to be recognizing when the specialty bounty has been turned in. I've been getting the "You can still grab a Filthy Lucre (speciality)" message even though I've turned in the bounty and received my lucre. Not sure what's changed but I've been noticing it over at least the past two or three days - I don't always do the specialty bounty depending on if I have the item needed or if it's available cheaply, so it may have started even earlier. It's not a huge issue, obviously - it's easy to ignore - but I thought I'd mention it.
 
GwynMyrddin said:
Not sure if this is still being maintained or not, but it's been a lifesaver so thank you! I noticed one strange bug that literally just started for me in the last few days. The script no longer seems to be recognizing when the specialty bounty has been turned in. I've been getting the "You can still grab a Filthy Lucre (speciality)" message even though I've turned in the bounty and received my lucre. Not sure what's changed but I've been noticing it over at least the past two or three days - I don't always do the specialty bounty depending on if I have the item needed or if it's available cheaply, so it may have started even earlier. It's not a huge issue, obviously - it's easy to ignore - but I thought I'd mention it.
Click to expand...
I haven't done a bounty in.... Umm... Roughly a year after he was released... I'll look into this though.
EDIT: Easy bounty done, still have hard, and special available...
I switched it to check specialty first. I finished all bounty today, lets see if that fixes the problem.

I'm 2 computers past the last time I updated this file, and I don't play anymore, so I'll upload the fix here.
 

Attachments

Last edited:
hey guys! Im getting an error code that is making me scratch my head a bit: "Could not find a known, usable skill of yours uniquely matching "910 Seal Clubbing Frenzy"". Any ideas why?

EDIT: my awesome clannie Captain Yaksworth came up with a solution, in case anyone else has the same issue:

set lastChanceBurn="". Might want to run prefref lastChanceBurn first to see what it's actually set to; if I'm right it'll be cast # Seal Clubbing FrenzyBasically, most "efficient" scripts will try and use all the mana they can when refreshing (e.g. if you have 900 max and are about to refill 1,000, they'll try and spend to 0 to maximize the value of the MP refill). lastChanceBurn is the "final" thing they'll spend mana on if there's not MP for more useful buffs, and is usually set to the basic class skills (since they're extremely cheap).

If you use set lastChanceBurn="" (or alternatively to a cheap skill you do actually have, like cast # Ghostly Shell, your script will either:
  1. Understand, and either skip the step or cast the skill you actually have
  2. Still break, but leave lastChanceBurn untouched
  3. Just override your lastChanceBurn again and break
If (1), you'll have fixed your issue, all good.If (2), then I'm wrong, and your issue is coming from elsewhere - sorry!If (3), then the script is bugged; your only option is to (a) get the script fixed, either personally or by reporting the bug, or (b) perming Seal Clubbing Frenzy.

end of edit, hope it helps, worked for me!
 
Last edited:
You must log in or register to reply here.
Back
Top