About this site

What this site is

FollowersGame.wiki is a fan-made, unofficial player wiki covering exactly one game: Followers game by Molten studios :D (Roblox place 102422301065716, universe 10766239678). It is not affiliated with Roblox Corporation or Molten studios :D, and it does not cover the same-named game by -The Moon Lanterns- or the “+1 followers” incremental family (see the homepage disambiguation).

The site exists because this game is genuinely hard to research: it is new (created September 13, 2026), its official description is the single word “simulator”, it shares a near-identical name and description with a different game that launched eleven days earlier, and its listing has been in a private state since September 24, 2026. Most of what can honestly be known about it lives in primary records — Roblox’s own APIs and the developer’s group history — and this site’s job is to read those records carefully, date them, and explain what they do and do not show.

Who maintains it

The site is maintained by an independent Roblox player-editor who tracks the game through its official Roblox surfaces, the developer group’s public record (group 17356272, 57,265 members at the November 11, 2026 check), Roblox’s public APIs, the DevForum discussion, and named third-party coverage. There is no advertising relationship with the developer, no affiliate links, and no bot tools or follower services promoted anywhere on the site — by policy, not by accident.

Editorial policy

Followers game is a small, new game whose systems have no public documentation, so this site builds on primary records instead: Roblox's own public APIs, the developer's group history, the DevForum discussion, and named third-party coverage. Every table names its source and carries a checked date. We do not invent steps, numbers, codes or quotes; where sources disagree (as code trackers do across same-named games), we show both sides; and where a fact genuinely has no source, the pages say what was checked, how, and when — one dated sentence — rather than filling space with guesses.

• Primary records first. Listing state, group record, badge counts and the developer portfolio come straight from Roblox’s public API endpoints, queried directly and stamped with the check date.
• Attribution or silence. Community claims (ban-risk answers, genre history) appear only with a named author, video, or thread and the date we read them.
• No padding. Where the game lacks public documentation, pages say what was checked, how, and when — one dated sentence — instead of manufacturing filler.
• Safety claims need sources. The safety page quotes only named DevForum replies and describes documented scam patterns; it makes no unsourced safety claims.

Source register

Every table on this site traces back to this register. The site-wide reference check is dated 2026-11-11; individual sources carry their own dates where they were read earlier.

Roblox API endpoints above are the same URLs this site queries on every refresh; “checked” is the date of our most recent direct read of each source.

How pages are updated

The game’s availability is re-checked through Roblox’s games API on every site refresh, and each check is appended to the status page’s dated history. Codes and official links are re-checked whenever the listing state changes, when the developer posts a group shout, or when a third-party tracker adds coverage — the codes page and links page each keep a per-source checklist with its own date. Safety content is re-verified against the DevForum thread rather than paraphrased from memory. Older observations are kept when they help players (the availability history is exactly that), and dropped when they stop being true.

What we deliberately leave out

Three things never appear on this site, regardless of demand: bot tools or scripts (they automate fake followers against Roblox’s intended account behavior — see the safety page for the sourced discussion), republished code lists for other same-named games (the documented mixups are on the codes page), and invented gameplay details. The last one is the site’s founding rule: with a game this thinly documented, a wiki can fill pages with plausible-sounding steps, and every one of them would be fiction. Where a rival site guesses, this one shows the check log instead — shorter, but true.

Corrections

If a page shows a number that no longer matches the game, a quote that reads differently in context, or a missing credit, open an issue on the site’s GitHub repository with the page URL, the claim, and a reference that supports the correction. Corrections that check out are applied with a new checked date — the old value is replaced, not silently edited into history.

Search-engine submission

Updates are pushed to search engines that support the IndexNow protocol; our verification key file is /00af8396dfe45e599539c2a2ab9c1850.txt.

Explore

Guide · Is it safe? · Codes · Links · Status