-and item types, can be edited in config/defs. Here the first value is a
-numerical ID that represents the object type, the second one describes what type
-this object decomposes to when it gets destroyed/killed, the third value is the
-character used to represent the object visually on the map, the fourth value is
-the number of hitpoints the object starts with (items are dead and start with
-zero hitpoints, anything else moves), the fifth is the string that names the
-object in the game log.
+and item types, can be edited in ./confserver/map_objects. Here the first value
+is a numerical ID that represents the object type, the second one describes what
+type this object decomposes to when it gets destroyed/killed, the third value is
+the ASCII character used to represent the object visually on the map, the fourth
+value is the number of hitpoints the object starts with (items are dead and
+start with zero hitpoints, anything else moves), the fifth is the string that
+names the object in the game log, the sixth defines if the object is consumable
+(it is if it is non-zero) and how many hitpoints are gained if it is. Finally,
+the same delimiter as for the map object action definitions file follows.
+
+All source files are thoroughly documented to explain more details of
+plomrogue's internals. The ./roguelike-server executable can be run with a -v
+option for helpful debugging info (mostly: what messages the client sends to the
+server). Server and client communicate via files in the ./server/ directory
+(generated when the server is first run). The ./server/in file is read by the
+server for newline-delimited commands. The ./server/out file contains server
+messages to be read by clients. The ./server/worldstate file contains a
+serialized representation of the game world's data as it is to be visible to
+the player / the player's client.