Nemesis quest script
- Thread starter slyz
- Start date
What do you feel about the suggestion from illarion to scrap the major releases entirely and simply refer to the daily builds at all times? Is there any great benefit in having the version control we do when it seems to confuse so many people?
The point releases notify people that there is a new version. However, I think it's better to train people to not rely on that any more. Also, mallprices.txt currently only gets updated with point releases (if you don't have that one setting turned on), so those processes would need to be decoupled.
Well, that would be entirely the point. The problem is people thinking that they are the new versions.
Fair point. How big of an issue would that be?
Veracity posted a script for that on the dev forum. Start the script, check back after a while, then submit the update however frequently it seems necessary.
Bought clown items manually and equipped them and re-ran the script. Works perfectly. Thanks!
The script should try to maximize once (in case you already have enough items), then try to use retrieve_item() on the cheapest clownosity items. If you don't have mall access, or if you don't allow Mafia to buy from the mall, the script will stop.
What I don't understand is that it should print a "More Clownosity needed!" message in red, which I don't see in your gCLi output. Maybe I should replace
with
What I don't understand is that it should print a "More Clownosity needed!" message in red, which I don't see in your gCLi output. Maybe I should replace
PHP:
cli_execute( "maximize 4 clownosity -familiar -tie" );
PHP:
maximize( "4 clownosity -familiar -tie", false );Apparently, if the value of a failed cli_execute( "maximize ..." ) isn't captured, it will force the current function to just return false now and then, just like when adventure() returns false:
The "maximizing done" message is missing.
This doesn't happen with maximize():
This is probably some kind of ASH bug. People have been capturing the return value of adventure() to avoid this for a long time, so I hope it has nothing to do with the recent change to the return values of ASH functions.
PHP:
boolean test()
{
cli_execute( "maximize 7 raveosity -familiar -tie" );
print( "maximizing done" );
return ( numeric_modifier( "Raveosity" ) >= 7.0 );
}
if ( test() ) print( "OK" );
else print( "NOT OK" );
Code:
> call test.ash
Maximizing...
104 combinations checked, best score 0.0 (FAIL)
[COLOR="#ff0000"]Unable to meet all requirements via equipment changes.[/COLOR]
See the Modifier Maximizer for further suggestions.
NOT OKThis doesn't happen with maximize():
PHP:
boolean test()
{
maximize( "7 raveosity -familiar -tie", false );
print( "maximizing done" );
return ( numeric_modifier( "Raveosity" ) >= 7.0 );
}
if ( test() ) print( "OK" );
else print( "NOT OK" );
Code:
> call test.ash
Maximizing...
104 combinations checked, best score 0.0 (FAIL)
maximizing done
NOT OKThis is probably some kind of ASH bug. People have been capturing the return value of adventure() to avoid this for a long time, so I hope it has nothing to do with the recent change to the return values of ASH functions.
Theraze
Active member
Doesn't a failed CLI_EXECUTE make the rest of that function fail? So your subroutine test, as soon as CLI_EXECUTE fails, stops, which then makes it print NOT OK.
If you wanted to make this work, you'd probably have to do !CLI_EXECUTE similar to the old !adventure thing to tell it that you don't really care what it returns...
If you wanted to make this work, you'd probably have to do !CLI_EXECUTE similar to the old !adventure thing to tell it that you don't really care what it returns...
Jar of Jam
Member
What a great script. Cheers!
New version: 1.3.
I switched all the cli_execute( "maximize ..." ) to maximize(). Someone reported a problem where the auto-attack was killing slimes before the bottle of gu-gone could be used, so the script now disables your auto-attack and restores it when it exits. The setting will be lost when you stop the script using escape though.
I switched all the cli_execute( "maximize ..." ) to maximize(). Someone reported a problem where the auto-attack was killing slimes before the bottle of gu-gone could be used, so the script now disables your auto-attack and restores it when it exits. The setting will be lost when you stop the script using escape though.
Thanks!
Thanks for this script! I used it successfully on my last ascension, but now I've got an error as a SC. Am I doing something wrong? Here's what the CLI sais:
Code:
> call scripts/nemesis.ash
Internal checkpoint created.
Resetting mind control device...
Mind control device reset.
Restoring initial settings...
CCS set to default
You already know LTS.
Checking passive damage sources on the KoL Wiki...
Something happened while parsing the KoL Wiki for passive damage sources.
Could not obtain the hellseal disguise.
Restoring initial settings...
CCS set to default
Resetting mind control device...
Mind control device reset.
Problem occured while opening the Nemesis Lair, exiting...It might be due to the wiki being down for upgrades.
two days later and I'm still getting the same error. the wiki doesn't seem down...
Theraze
Active member
Yeah... the page itself is up, but the parsing is failing. It's possible that the page itself was modified, since it was looking for a specific break-point. Personally, I just commented out the two lines that made it abort if the passive check has no entries and left the avoiding of passive damage sources to me.