Shen should be handled sooner

[taltamir]

Context

• KolMafia version: r20004
• Class: sauceror
• Run type (Casual/Normal/Hardcore/Aftercore): normal
• Challenge Path (Standard/Path Name/None): heavy rains
• Number of Ascensions: 350+
• Are you using the beta version of autoscend?: beta

Expected/Desired Behavior

shen should be done sooner. on rain run it just did it when the only remaining things were palindrome, zeppling, itself, and war. it already had the bridge finished when it was looking for the shen drop at smut orcs, it already had completed hole in the sky when it looked for the drop there. not sure what its third locale was. but it was wasteful

[jeparo]

I've written boolean[location] shenSnakeLocations(int day, int snakes_defeated) and am currently expanding the rest. Might need some help with testing. My current plan is roughly:

• Up the priority of the Shen quest.
• Track the day we unlock the Shen quest and "lock in" the relevant snakes. This is used in some wrapper to shenSnakeLocations(). Before we "lock in" the snakes, our shenSnakeLocations() wrapper returns all possible snake zones - we are extremely conservative.
• On startup, set auto_skipSnakeZones=true. Modify quest code to early return false; in quest code that would adventure in snake zones.
• The above might cause some accounts to run out of tasks to complete, especially if we're not asdf. So as soon as we have no tasks to do, if auto_skipSnakeZones is set, instead of powerlevelling we unset auto_skipSnakeZones and call doTasks() again". As a micro-optimization, we might be able to get away with setting auto_skipSnakeZones=true again when we level up and new tasks become available.

Comments welcome.

[Malibu-Stacey]

453 has some changes that would help facilitate this and example pathing which works well in LKS.