Alabaster — 60 of 123

John Cater, Rob Dubbin, Eric Eve, Elizabeth Heller, Jayzee, Kazuki Mishima, Sarah Morayati, Mark Musante, Emily Short, Adam Thornton, and Ziv Wities

Release 1

Chapter 9 - General Parsing Improvements

[As much as I like the concept of Smarter Parser, it proved to be throwing Glk errors for reasons I couldn't work out; it also made for a longer response time for negative results on commands, which I didn't like in the context of the already slow runtime here.]

[Test parse-broken with "test hart-chat / ask why / yes / no / a snow white / smile / a terms / yes / yes / yes / yes / a where / say I'm sorry". [testing for a specific bug that turned up with the inclusion of these extensions -- now solved by stopping the apostrophe stripping.]

Include Smarter Parser by Aaron Reed.

Include Poor Man's Mistype by Aaron Reed.

When play begins:

choose a row with a therule of signs of confusion rule in the Table of Smarter Parser Messages;

change the message entry to "Try typing ASK ABOUT (something) or TELL ABOUT (something) to direct the conversation, and YES, NO, and MAYBE to answer questions. To interact with your surroundings you can LOOK and EXAMINE specific objects. You may also HIT, CUT, or BURN objects, or PUT things IN other things.";

choose a row with a therule of asking who are you rule in the Table of Smarter Parser Messages;

change the message entry to "Alabaster responds to your instructions by telling you more of the story you're inside. Try typing HELP for more information.";

choose a row with a therule of unnecessary movement rule in the Table of Smarter Parser Messages;

change the message entry to "You needn't move within a single location, but if you want to go to a new place, try GO TO (wherever).";

choose a row with a therule of stripping body parts rule in the Table of Smarter Parser Messages;

change the message entry to "You do not have to specify the use of body parts in that much detail.";

choose a row with a therule of signs of frustration rule in the Table of Smarter Parser Messages;

change the message entry to "I'm sorry you're feeling frustrated. If you like, you can type SAVE to store your progress to a file, then RESTORE to come back to it later.";

choose a row with a therule of the asking random questions rule in the Table of Smarter Parser Messages;

change the message entry to "No such question is currently available. Try TOPICS if you are at a loss for things to say.";

A first smarter parser rule:

say "[second custom style][run paragraph on]".

Before printing a parser error:

say "[second custom style][run paragraph on]".

After printing a parser error:

say "[roman type]".

A last smarter parser rule:

say "[roman type]".

The too many words rule is not listed in any rulebook.

The standardize apostrophes rule is not listed in any rulebook.

The Smarter Parser simplify punctuation rule is not listed in any rulebook.

After reading a command (this is the new Smarter Parser simplify punctuation rule):

let tmpcmd be indexed text;

now tmpcmd is the player's command;

replace the regular expression "<;:>" in tmpcmd with ". "; [new players have sometimes tried to seperate commands using these punctuation marks.]

replace the regular expression "<!?\/()\{\}[quotation mark]>" in tmpcmd with "";

change the text of the player's command to tmpcmd. ]