We will define Rooms with a passage with the [room] tag:

:: Your House | Kitchen [room]

/* areaName and roomName are parsed out of the passage name and placed in _areaName and _roomName.
    In this example, _areaName=="Your House" and _roomName=="Kitchen". */

<<RoomImage "Some_Image_File_Basename" offsetX offsetY>>

<<if !Room.visited()>>
  <<RoomDesc>>
    The room description on the initial visit.
  <</RoomDesc>>
<<else>>
  <<RoomDesc>>
    The room description on return visits.
  <</RoomDesc>>
<</if>>

<<RoomFeature "door" offsetX offsetY "Exit through the door to the hallway.">
  <<MoveToRoom "Hallway">>
<</RoomExit>>

<<RoomFeature "window" offsetX offsetY "Jump out the window to the street.">
  <<MoveToArea "Steet" "Outside Your House">>
<</RoomExit>>

<<RoomInit>>
  <<script>>
    Room.addObject(
      SmutBook.API.defineObj( "pistol", SmutBook.Persistence.PersistentObject, {
        "name" : "battered old Smith & Wesson M28 revolver",
    	  "image" : "pistol",
    	  "description" : "A late-1950s S&W \"Highway Patrolman\", which has seen better days.  It is chambered in .357 Magnum."
        "interactions" : [
          { "InRoom", "Pick up the pistol.", function() { /* Move the pistol from the room to the viewpoint character's inventory, although this should be default for gettable items. */ } },
          { "InInventory", "Examine", "Some TwineScript to evaluate at the bottom of the inventory examine popup, giving the player links through which to manipulate the object." }
        ]
      }),
      offsetX, offsetY /* These are optional; if not specified, the red ring will be rendered in the center of the room. This is cleared the first time an object is moved. */
    );
    Room.addObject(
      SmutBook.API.defineObj( "award", SmutBook.Persistence.PersistentObject, {
    	   "name" : "honorable mention award",
    	   "nameIrregularArticle" : "an",
    	   "image" : "award",
    	   "description" : "Well, now nobody can say that you've never won anything!"
      })
    );
    Room.addObject(
      SmutBook.API.defineObj( "novel", SmutBook.Persistence.PersistentObject, {
    	   "name" : "\"Atlas Shrugged\" (a novel by Ayn Rand)",
    	   "nameIsProper" : true,
    	   "image" : "novel",
    	   "description" : "Just who <i>is</i> John Galt, anyway?"
      })
    );
    Room.addObject(
      SmutBook.API.defineObj( "typewriter", SmutBook.Persistence.PersistentObject, {
    	   "name" : "magical typewriter",
    	   "nameIrregularArticle" : "the",
    	   "image" : "typewriter",
    	   "description" : "It smells like hipster."
      })
    );
    Room.addObject(
      SmutBook.API.defineObj( "refrigerator", SmutBook.Inventory.GeneralInventory, {
        "name" : "magical typewriter",
    	  "nameIrregularArticle" : "the",
    	  "image" : "typewriter",
    	  "description" : "It smells like hipster."
        "interactions" : [
          { "InRoom", "Look in the fridge.", function() { /* Open the fridge inventory popup. */ } },
        ]
      }),
      offsetX, offsetY
    );
    Room.addObject( "computerTerminal", offsetX, offsetY ); /* Add an object defined elsewhere.  If it has already been defined, you can pass a PersistentObject as the first arg, but the object id like this is ok too. */
  <</script>>
<</RoomInit>>

These Location passages are not meant to be visited directly.  Instead, they are evaluated by the main Location-Based-Adventure passage.

Since the passage is re-evaluated each iteration during play, TwineScript flow control may be used to gate off, enable, or disable various portions of the room passage.

During game initialization, all [room] passages are looped through and evaluated, with the current room set to whatever room is being evaluated (so that Room.addObject() will work).  All sections other than <<RoomInit>> are ignored.  This is used to initially populate the room inventories.

Every room has a GeneralInventory.  They are initialized into the Game.RoomInventory object, keyed by "areaName|roomName".

In the location-based adventure mode, the passage for the current room is evaluated in a loop:
  - <<RoomImage>> selects the image shown for the room on the map and renders the map.  If no <<RoomImage>> is specified, it is set automagically after the passage is evaluated, to "Areas/<_areaName>/<_roomName>".
  - <<RoomDesc>> Clears the room description area to the left of the map, evaluates the twinescript in the macro payload, and renders it into that room description area.
  - <<RoomInventory>> - Loops through the room's inventory and...
    - The descriptions of the objects in the room are rendered infocom-style into the room description area, appended beneath the room description.
    - Those objects' InRoom interaction links are appended to a div at the bottom of the scrolling text area below the map/room_desc area.
      - FIXME: Should the list of things in the room instead be in the interact area, with each obj desc being a link that pops up a context menu for that object?  I think so.  Maybe we can just use a popup for the context menu, that might be easier than a jquery floating context menu.  We can just pop up the whole examine window with all the manipulation options that we already implemented for the inventories and stuff.
      - How should we implement the way that Inform has a long description that is displayed before the item has been picked up and dropped again?  How do we put links into that desc that do stuff?  This would also be useful for scenery, etc.
      - We can just list the exits the same way.  Clicking on an open exit will move you through it.  Clicking a closed exit will pop up an interact popup.
  - <<RoomFeature>> appends an exit/feature link to the same div that the object/interaction links were.
  - <<RoomInit>> sections are ignored at this time.

  - When the player clicks an option in the div full of interaction links, the whole div is replaced with a greyed out version of the selected option, the same way the <<choose>> macro works.  FIXME: How does this interact with the object popups in the above FIXME?
    - Whatever action is associated with that link is evaluated. and the results appended to the scrolling text area.
      - Moving to a different room is accomplished with a macro that:
        - Creates a checkpoint for the back/fwd/replay passage buttons.
        - Changes variables that contain the current room/area.
        - Then when the loop repeats, the new area/room info is rendered into the appropriate places.
    - The process repeats, re-evaluating the passage, re-rendering the map (in case player actions changed something), re-rendering the room description (ditto), and redisplaying the available options.
  - Branching away from location-based adventure mode and into a narrative scene is accomplished by Playing some other passage.  Returning to location-based adventure mode is accomplished by Playing the Location-Based-Adventure passage again.