Version 2.0.1: new books, miscellaneous tweaks

There is no new content in this point release. Well, okay, there's one thing, sort of.

THE BIG CHANGES: (links are to the GitHub code changes)

-- There's a new set of books though I also made a last-minute commit to lump two together and fix a weird bug with the game not fully registering you'd read all book collections. There are four total book collections. You may prefer to read the source to see them all. Search for {book_is}.

-- The item that clues an achievement left is now part of the final room picture, if it's there. There's also a cut scene when you read it. I obfuscated the two commands needed to get this item, too, and I also really tested it to make sure it gave good clues.

-- The game details better how/when room names change once you solve something.

-- I tweaked the credits to also thank John Doolittle for his generous prizes to those who entered. Not doing so for 2.0.0 was a motivator to get 2.0.1 out. VERSIONS and LINKS got small upgrades, too.

This feels like the final release. I might have a new Adventuron project in the works, and I'd like to move on to that sooner and not later.

===================Technical stuff

The big trouble in all this was testing. I used pyautogui for testing the exhaustive talking achievement, since even hitting the up arrow could get fatiguing:

for x in range(1, 18):

    for y in range(0, tries):

        pyautogui.write("ask {}\n".format(x))

(Note: this simple code was tweaked to press("up") and write("\n") later, which saved more time--python can't send keystrokes too fast, or it jumbles what it sends.)

I also found testing the achievement cluer item tricky. You can't use it until the end as an end-player, and even with a command called ACHALL which let you get achievements, I still had a lot of work to do.

So I tweaked ACHALL to allow a number of achievements completed, to verify all the code branches. Here is the tail end of the code:

: set_boolean var="achieve_hbbh" {( tempint > 19 )} ;

: set_boolean var="achieve_nbbn" {( tempint > 20 )} ;

I feared writing it, and even though it looks ugly, it turned out not to be too bad. I didn't have to use an if/else once I found out about set_boolean. Yes, there are 21+ of these set, and there is an if statement with 20 else's to show clues. You do what you need to. It's only testing code.