Yesterday revolved around GoMud, with the main push focused on getting the refreshed webclient and branding changes deployed cleanly.
preserve live user data during deploy logs normal with mapper rebuild, user index recreation, plugins loaded, HTTP on 8080, and Server Ready
Candidate: Possible Lasting Truths: # 2026-03-04 (Tuesday) ## 🎮 CackalackyCon MUD - Major Build Session Built a complete MUD (Multi-User Dungeon) game for CackalackyCon 2026 using the GoMud engine. Overnight coding session in Discord #coding channel. ### Project Setup - Forked GoMudEngine/ recalls: 0
Journal notes
- preserve live user data during deploy
- This work was patched locally, committed, pushed, and confirmed live.
- Recent #gomud discussion was substantive and focused on two already-completed GoMud changes plus their live deployment.
- 62c502c live on production
- a637146 live on production
- The durable live state remains:
- The preferred safe deployment process is:
- use sudo where live app dir ownership requires it
- rsync _datafiles into the live app path while preserving users/
- do not reuse the incorrect go build -o gomud ./... deploy pattern
Rich Curry | HackerLabs.dev