ShadowRift

[Magus_Prime]

Will VMF automatically take advantage of the new behavior? I'm running VSR with the defaults, as part of VMF, with the addition of telling it to use a PYEC. I'm particularly interested in this section of your post:

fought 1 shadow bat, 1 shadow guy, 1 shadow prism, 3 shadow slab, 4 shadow snake (10 normal shadow monsters)
fought 1 shadow cauldron, 3 shadow matrix, 1 shadow spire, 1 shadow tongue (6 shadow bosses)
spent 3 shadow bricks.
found 1 shadow bread, 6 shadow brick, 3 shadow flame, 1 shadow fluid, 1 shadow glass, 3 shadow nectar, 2 shadow sausage, 7 shadow sinew, 3 shadow skin, 1 shadow stick (net gain of 25 items)
And ended up with 180 turns of Shadow Waters.

 

[Veracity]

If you own a Jurassic Parka, yes, Shadow Rift will use it automatically for 5 quests a day.
If you want to do entity quests rather than artifact quests, you have to indicate it in VMF.ShadowRiftCommand2

 

[Magus_Prime]

Will "telling" VSR to do entity quests also automatically use shadow bricks and, potentially, end up with many turns of Shadow Waters banked when finishing in the rifts?

 

[Veracity]

Yes. VMF lets you configure two quests in VMF.ShadowRiftCommand1 and VMF.ShadowRiftCommand2.
The first one will be an "items" quest using no turns and gets Shadow Waters, and the second one will be an "artifact" or "entity" quest and will do the forest once and then Shadow Waters for additional quests. You will end up with 6-9 items from the forest and 150 turns of Shadow Waters.

Note that you have to use ShadowRiftConsult - doing so is the default for a VSR setting - since that knows to launch spikolodon spikes 5 times in order to fulfill 5 quests a day.

With a PYEC - 16 turns of Shadow Affinity per day - I believe I can set ShadowRIft up to get 5 1/2 quests a day - i.e., 5 on day 1, 6 on day 2, and so on. I haven't done that, yet, and won't have time until I finish my vacation; I am in NYC, now, and I can answer forum posts, but, will not be coding for 3 more weeks.

 

[Magus_Prime]

Thank you for the time and attention you spend on scripting for KoLmafia. It significantly improves "quality of life" in playing the game.

 

[neomaster]

I've noticed an issue when fighting the shadow scythe with the parka. The script switches from spikolodon mode to kachungasaur mode before the boss without healing to accomodate the increase in max HP. So when it tries to take advantage of the turn 1 miss to use silent treatment, it just causes you to be one shot by the 90% max HP hit on turn 2.

 

[Veracity]

I've noticed an issue when fighting the shadow scythe with the parka. The script switches from spikolodon mode to kachungasaur mode before the boss without healing to accomodate the increase in max HP. So when it tries to take advantage of the turn 1 miss to use silent treatment, it just causes you to be one shot by the 90% max HP hit on turn 2.

How odd.

void prepare_for_boss()
{
    // If we want to have Jurassic Parka in kachungasaur mode for bosses, make it so.
    if (parka_mode == "both" & get_property("parkaMode") != "kachungasaur") {
    cli_execute("parka kachungasaur");
    }

    // Restore to 100% HP to avoid insta-kill from the shadow scythe
    restore_hp(my_maxhp() - my_hp());

I specifically do the parka first for exactly that reason.

Did changing the parka not change what KoL thinks your maximum HP is? Or am calculating HP to restore incorrectly?

Edit: It is the latter. We want:

    restore_hp(my_maxhp());

 

[Veracity]

Fixed in revision #26

 

[neomaster]

That's amazing, thanks so much for even looking at it while you're away! Hope you enjoy your vacation!

Edit: Just thought I'd report that I ran the script today, encountered the scythe and had zero issues. Thanks again!

 

[Veracity]

Bug:

Did a quest for Rufus.
He gave me a shadow lodestone.
Adventured to cash it in and collect the reward.
I was shunted into the Violet Fog.
Result: I still had the lodestone but the script thought we were done.

I thought the Shadow Rifts could not be interrupted like that?
Apparently I was wrong.

This is rare enough that I won't be looking at it until I get back.

 

[Veracity]

Revision #27 handles that issue: when we attempt to turn in a shadow lodestone by adventuring through a rift, if it didn't consume a shadow lodestone, try again.

That revision also uses my no "varargs" technique for command-line arguments, so if you want to simply adventure using whatever the configuration properties are set to, you no longer need to use a "default" keyword to avoid being prompted for input.
In fact, I removed the "default" keyword and updated the help text and README.md file to reflect that.