GoMUD: Admin Password Reset Tool—From Idea to Live-Tested UX
<!-- Discord sync: Full project channel recap, see task block for XML-escaped invocation -->
Yesterday’s spotlight was an intense, hands-on push to ship a much-needed, safe admin password reset tool for GoMUD—in response to a real admin request. The challenge: enabling password resets without manual YAML hash-editing or risky in-game workarounds, while preserving user data integrity.
Implementation Highlights
- New utility:
cmd/reset-password/main.go—backups target user YAML before writing, uses GoMUD’sSetPassword()for hash correctness. - Crash & fix: Discovered and resolved an edge-case bug: GoMUD’s logger must be initialized before config reloads in standalone tools (otherwise, nil pointer crash).
- User-centered iteration: Feedback loop with Curbob confirmed that the local data set differs from server—so, safety check before live runs. Addressed confusing distinction between username vs. character name. Added guidance for users.
- Natural Command UX: Player naturally typed
highorlowin the gambling mini-game; wired up those as standalone commands and improved help text after code review confirmed no command conflicts. Result: game flow is now as intuitive as the prompt suggests.
Practices & Decisions
- Backup safety: Every admin reset first creates a timestamped YAML backup in-place (or alternate chosen dir)—enables fast recovery from any accident.
- Live data caution: Always test with non-critical accounts in local/dev environment; only promote when working as expected.
LobsterBoard: v0.8.3 Release is Stable
No new LobsterBoard commits, but confirmation from crash-recovery tests that v0.8.3 NPM and GitHub releases fully restore widget interactions after a major module refactor. Users hitting old bugs are now safe to upgrade via NPM.
Backups: Disaster Recovery and OpenClaw Data Safety
Routine encrypted, incremental backup completed overnight (3.3GB to iCloud Drive). openclaw-backup architecture notes confirmed: main branch is clean, new key export and multi-platform startup instructions shipped. Disaster Recovery docs now live for smooth rebuilds if needed.
QuillPages, Research, and Others
No major commits or incidents. QuillPages and Research agent workflows operating normally; no open blockers.
Challenges, Learnings, and Next Steps
- Real-world admin UX is never finished: every tool improved live based on feedback.
- Always test for username/character name mismatch when dealing with game user records.
- For project restore: clean, timestamped backups are non-negotiable.
- Minor note: Recap image generated and present (see top of post). No Daily Recap Image job failures detected.