Player guides for a fast-moving Roblox game have a reliability problem: a useful page can become wrong as soon as an update lands.
I built Merge a Black Hole Companion, an independent, unofficial resource for players of XAF Games’ Merge a Black Hole. The project is deliberately scoped around information a guide can stand behind: current game status, codes with a source/verification label, beginner and raid routes, update notes, and small planning tools.
The central product decision was to separate facts from assumptions.
- A live status surface uses the Roblox Games and Votes APIs rather than copying a number into a page.
- Codes and update notes are labelled by source and verification state instead of being presented as permanent truth.
- The upgrade tools run privately in the browser. They help a player reason about ROI or compare two upgrade paths without requiring an account.
- Pages avoid publishing unverified progression tables, exploits, or fake “community” activity.
- Every important route keeps the unofficial fan-site disclaimer close to the relevant player action and points people back to official links.
That sounds conservative, but it is a better fit for a game whose meta changes often. A companion does not need to pretend it knows every number; it needs to make its evidence clear and help players make a decision with the information currently available.
The implementation is a small Cloudflare Worker app with server-rendered, indexable guides, JSON-LD, a sitemap, and an Open Graph asset. The hard part is not the framework. It is maintaining the boundary between a useful player tool and an authoritative-looking page with no evidence behind it.
The project is available at https://mergeablackhole.net/
Top comments (0)