The following is an abbreviated version of the Subversion commit message logs. Please keep in mind that these messages are intended for other developers and they take the files which were modified into context in order to limit the amount of verbage. In general, they are not intended for general audiences and should not be treated as "official" documentation -- they are informal and abbreviated, at best.
If you do not understand what something says, try looking at the full version of the revision by following the accompanying link for the revision. The only difference is that the files which were modified will be listed, and sometimes, you can guess what happened from file names (though not always). If you still have no idea what happened, that's okay -- it probably doesn't relate to what you're doing with KoLmafia. ^_~
Furthermore, not everything marked as "fixed" is guaranteed to be fixed, not all changes are guaranteed to have a change. This is due the fact that both time and turns are finite and only a limited number of things can be tested. Some changes go in untested, assuming they would work, when they actually don't due to erroneous assumptions; alpha testers occasionally will be able to give feedback, but it's not always possible.
For example, if you read the revision logs for what changed between 10.2 and 10.3, the plus sign choice adventure was meant to get a use link. Something as seemingly insignificant as KoL using two spaces instead of one space in the sentence "It's actually a book. Read it." would mean the change didn't actually work -- anyone can verify that, in fact, the change didn't work for this very reason. If you ever encounter something like that, a non-accusatory mention of it (non-accusatory meaning anything that neither implies "ZOMG FALSE ADVERTISING" nor "You guys said this was fixed, but...") somewhere will usually result in the problem getting addressed.
Finally, if you've got a bug to report, make sure you read up on how to post a detailed bug report. While the rules outlined apply specifically to bugs related to scripting, many of them are applicable to KoLmafia bug reports in general. Most importantly, I hate the words "annoying" and "frustrating". Never use them when describing a bug/feature. Ever. Thanks. The abridged revision logs follow.
Item descriptions can contain references to other items. If both are unknown,
this leads to recursive item registration. Therefore, cannot use a single
static instance variable to hold "the" request to fetch item descriptions.
This showed up with the new IOTM, so, include item info for that item and
the item you get when you use it.
Pill Keeper support
Only do stuff in the Pill Keeper choice if it is successful
Sunday pill lets you get the same semirare twice in a row
Automatically recognize when KoL changes an effect name. GRevision 8tness -> GRevision 8ness.
Generate decorated response text when visiting a choice AFTER special classes
(like WumpusManager) have a chance to look at the response text and update state
Recognize new HTML for losing Ancient Annoying Serpent Poison for the last time.
More tweaks to intrinsics parsing
Fix enchantment parsing for items with embedded blue-tagged sets of enchantments,
like the Kremlin's Greatest Briefcase.
IN Actually Ed the Undying run, when we call liberateKing, we have already
chosen a new class and are no longer in a choice adventure. Therefore, do
not short circuit processing before calling the kingLiberated script.
Add a comment to BeachManager saving the HTML for the bottle message.
Perhaps we should log receipt or otherwise save in properties.
Undo that last submit, since ChoiceManager.afterAvatar calls KoLmafia.resetAfterAvatar
Remove duplicate line for a SEMIRARE in encounters.txt
Bastille Battalion control rig is reusable
When we visit a choice, clear UseItemRequest.lastItemUsed, so that it doesn't try to
process that item usage next time we visit the inventory (in case the choice was the
result of item usage).
When looking up special encounters, make sure they are in the expected adventure
area, since at least one semirare encounter has the identical name as a non
semirare encounter in a different zone
Monsters created by Lecture on Relativity do not count as semirare encounters
A lecture on relativity only gives you a copied monster if you win the fight.
Set appropriate property indicating it is coming if detect tell-tale link text.
Print consumption helper messages to session log as well as gCLI
Make [glitvh season reward name] a "message display" usable item.
In Kingdom of Exploathing, mark the Palindome quest as started as soon as you make
the Talisman o' Namsilat.
Add pillkeeper command from PeKaJe
'red hot' is now 'red-hot'
Decorate the response text to be sent back to the browser for a choice
AFTER onAscension script has run. Otherwise it will be overwritten is
such a script calls other choices.
Don't refresh concoctions after processing a chat request.
Check for Lecture About Relativity whenver we categorize encounters, not just when it looks like a semirare monster
Ignore "special" monsters (i.e., copies, etc.) when checking whether a particular monster needs
special tracking variables to be updated.
Witchess pieces have a unique choice URL in the page text
Unopened Eight Days a Week Pill Keeper is a Free Pull.
Bump version to 19.11