Wiki pages exist when people decide to spend the time to create them. Describing it as a problem that it hasn't been created yet seems a bit misleading.
That one is my fault. The Florist Friar let us determine KoL's name for any place that uses adventure.php at least (with no basis for it, I'm guessing that's all the Autumn-aton shows too?). The location name having brackets seemed ridiculous enough that I didn't want to match it. I'm pretty...
My vague recollection, from reading stuff from before I started even using KoLmafia...
The reason for two instances being the limit, instead of one, is that sometimes the session lock files weren't cleaned up properly, for whatever reason. So there wasn't actually an expectation that two...
I would want the default behavior of print_html() to stay as is, rather than having to go back and change scripts that I wrote a decade ago with the explicit goal of not spamming up session logs with output that is only useful for the user to look at in the moment.
I think those players would mostly find choiceAdventure40 = 1,3,4 confusing also, and will simply copy-paste what someone posts in a chat conversation, so it may as well be a script installation command.
My first guess (not looking at any code, not having touched the new path, not having automated any adventuring at all this year at least) is that the dinosaur adjectives you are using aren't considered to be part of the monster's name according to KoLmafia, so those sections aren't matching.
Well, the bug report is actually describing a feature. Anything starting with "mus" that doesn't exactly match some other modifier is treated as "muscle". That includes "muslsdfjkskdlflkdsf", for example.
I expect someone would be disappointed if that changed.
Also, editing your post instead...
I added familiarScript a long while back, for people that disagree with the ordering of generic familiar equipment, particularly equipment that all gives the same weight bonus.
And there will need to be another symbol for adventure.php locations that don't yet have an environment type (new content that isn't in the data files yet).
I know that pulling everything from storage (using KoL's built-in button equivalent) takes a while. Long enough that the request times out, in my experience. So internally, there's built-in detection that the request has timed out, and then a delay of 20(?) more seconds (I arbitrarily chose...