Current baseline: September 12, 2026
This Followers Game updates tracker starts with a September 12, 2026 baseline. The official Roblox record identifies Followers Game by -The Moon Lanterns-, Place ID 97607545197126, Universe ID 10764892644, Social genre, maximum server size of 50, and creation date of September 2, 2026.
At this baseline, exact-game recordings show the Control Panel, Followers task, Check Status and Data Viewer, AFK and Hide GUIs controls, engagement rate conditions, task-tab labels, Store, Crates, SocialStore, and the Top Time Played Leaderboard. Every future entry should say what changed and when it was checked.
Baseline interface checklist
| Surface | September 12, 2026 baseline |
|---|---|
| Followers task | Username or user ID field, Start Task, pre-start Ready state |
| Progress check | Check Status opens a Data Viewer with query and count |
| Visible boost conditions | Like, favorite, and creator-group membership |
| Controls | AFK: ON/OFF and Hide GUIs |
| Other task labels | Twitch, Group, asset, look, bundle, game favorite, friend request, group like |
| Redeem | Secret reward code field visible |
| Shops | Store, Crates, and SocialStore buttons visible |
| Retention | Top Time Played Leaderboard shows days, hours, minutes |
The table is a dated snapshot. Recheck it after any visible game change.
Recheck rates as session samples
September 2026 recordings showed follower counts changing after waits, including one profile moving from 385 to 394 and later 402, and another gaining 53 after roughly six minutes before a later count of 1,002. These are dated samples, not a rate table.
For a current rate check, record the target, starting count, engagement conditions, task start time, server, status-check time, and final count. Do not carry an old followers-per-minute estimate into a new version.
Recheck codes through Redeem
A recording typed WELLCOME100 into Redeem but did not submit it. The baseline therefore confirms only that the string appeared in a September 2026 test. It does not confirm active status or a reward.
A future code entry must include the test date, exact spelling, current in-game response, and displayed reward after a successful redemption. Remove active wording when the current response shows an expiration or rejection.
Recheck every label-only task
The Followers tab has the strongest documented procedure. Other tabs need a new verification before instructions change. For each one, capture the exact label, target prompt, eligibility, button state, result, elapsed time, and reliability across more than one check.
Do not assume that similar labels share a target format. Keep the creator-group rate condition, Group task tab, and group-like category separate.
Recheck controls and shops
AFK and Hide GUIs are visible controls, but the baseline does not establish a rate, session-protection, or task-processing effect for either one. Update their pages only when the current interface or a controlled check gives a concrete result.
Store shows colored purchase rows, while Crates and SocialStore are confirmed navigation surfaces. Before adding commercial details, read the product or item name, price, currency, effect, duration, odds, reward pool, unlock condition, and confirmation shown in the current build.
Write a useful update entry
Log each update in this format:
- Checked: full date and timezone
- Surface: exact menu, tab, control, sign, or board
- Before: prior visible text or behavior
- After: current visible text or behavior
- Player impact: the action a player should change
- Verification: exact in-game state that confirms the change
If nothing changed, keep the baseline instead of inventing patch notes. Roblox live totals such as playing, visits, and favorites are time-sensitive platform metrics and should be timestamped separately from gameplay changes.
Separate platform facts from gameplay behavior
The official game page can confirm the creator, Place ID, experience name, genre, server capacity, creation date, and changing public totals. It does not explain the Control Panel’s hidden processing. Record platform-field changes in one part of the log and in-game behavior in another.
For interface behavior, use the exact current label and a reproducible action. For external profile results, use before-and-after counts with times. For a shop, copy the product description and confirmation. This keeps a changed favorite total from being presented as a patch and keeps one player’s session result from becoming an official promise.
Retire stale instructions clearly
When a button, tab, or field disappears, mark the older instruction with the date it stopped matching the live game. Replace the affected step with the new label and path. Do not leave both versions active without explaining which build or date each belongs to.
When a code expires, move it out of the active list and preserve the last successful or rejected check date. When a product changes price or effect, update both fields together. When a task’s result changes, repeat the same target and timing method before publishing the new behavior.
FAQ
When was this Followers Game updates page checked?
The current baseline is dated September 12, 2026.
Is WELLCOME100 an active code?
The string was typed but not redeemed in a recording. A current successful in-game check is required before calling it active.
Are old follower-rate examples still valid?
They remain dated examples only. Measure the current target and server before reporting a rate.
What should a new update record?
Record the date, exact surface, before and after states, player impact, and the current verification step.
Do live visit and favorite totals count as gameplay updates?
They are changing platform metrics. Timestamp them separately and do not treat them as mechanic changes.