How jeffrey-p-mcateer/house works
Project type and purpose
• This is a single‐binary, text‐based adventure server (monolithic game engine) written in Java (with one C module), delivering an interactive house exploration game via TCP on port 8888. Clients connect with a generic TCP client (e.g. socat or telnet).
Analysis of the file structure
• Top‐level code files:
• Action.java, Item.java, InventoryItem.java – basic domain model for commands and items
• Guest.java – represents a connected player
• House.java, Room.java, *.room – in‐memory model and room definitions (plain text maps)
• Data.java, Util.java, E.java – persistence helpers, utilities, error handling
• Room.c – low‐level helper (e.g. performance‐critical room parser)
• build.sh – compiles Java & C, outputs .class files into the classes/ directory
• .room files (basement.room, kitchen.room, etc.) – static resources defining room layout
• readme.md – explains installation, runtime, and where persistent data lives (~/housemem)
Insights from the README
• The server is launched by build.sh
• Listens on TCP port 8888; clients connect via socat
• Game state is persisted under the user’s home directory in ~/housemem
Elements
• Annotation of ports (8888) and file paths (~/housemem, /path/to/*.room)