Use the three conditions shown at spawn
The visible Followers Game rate boosts are tied to three engagement actions: like the experience, favorite it, and join the creator’s group. A sign beside the spawn hub says these actions give more per minute. The sign stops there. It does not show numbers or a formula.
Treat each action as a condition you can check, not as a known multiplier. There is no documented individual bonus, stacking order, detection delay, stable base rate, or maximum boosted rate.
Confirm the correct experience and group
Before changing anything, confirm you are in Followers Game by -The Moon Lanterns-, with Place ID 97607545197126. This prevents a like, favorite, or group join on a similarly named page from becoming part of your test.
Then inspect each condition separately:
| Condition | Visible claim | What remains unknown |
|---|---|---|
| Like the experience | Associated with more per minute | Individual value and detection timing |
| Favorite the experience | Associated with more per minute | Individual value and detection timing |
| Join the creator’s group | Associated with more per minute | Individual value, eligibility details, and detection timing |
| All three together | The sign lists all three | Whether bonuses add, multiply, cap, or change by server |
The creator-group condition refers to membership in the group behind the experience. It is separate from the Control Panel’s Group task tab and separate again from the group-like category visible in localized footage.
Build a useful before-and-after check
If you want to understand the current effect, keep a simple session record:
- Write down the target and starting count.
- Note which of the three engagement conditions already apply.
- Start the Followers task once.
- Remain in the server for a recorded interval.
- Use Check Status and record the new count.
- Change one engagement condition.
- Allow time for the live experience to detect it.
- Repeat the same interval and compare.
A changing server, target, wait length, and boost condition all at once cannot tell you which factor mattered. Keep the comparison narrow. Even then, treat the result as a dated session sample rather than a universal rate.
Do not publish a made-up formula
Do not assign each condition a percentage and add them together. The current interface gives you no basis for those numbers. It also does not state whether the base output stays constant across targets or servers.
Use wording that matches the screen: the actions are associated with more per minute. Avoid claims such as “double rate,” “three times faster,” “permanent boost,” or “instant activation” unless the current game displays and demonstrates those exact rules.
Store rows are also visible, but their names and effects are unreadable in the current recordings. Do not add purchases to a boost formula or recommend spending Robux to fix slow progress.
Diagnose a boost that looks inactive
Check the basics in order:
- verify the engagement action applies to the correct experience or creator group;
- confirm the Followers task was started for the intended target;
- note the elapsed time before checking;
- use the same target and Data Viewer method;
- distinguish a delayed detection from a task that never started;
- record the current server state.
Do not repeatedly leave and rejoin as proof of activation. Server switching, AFK toggling, and purchases are not documented boost refresh methods.
Decide whether a boost is worth testing
Likes and favorites are account actions on the experience page, while group membership changes your relationship to the creator group. Choose based on what you are comfortable doing, then verify the current result. The interface claim does not require you to accept a specific numerical promise.
Activate only the condition you want to test, keep everything else steady, and judge the count through Check Status.
Compare rates without overstating the result
Use equal wait windows when comparing two sessions. Record the starting and ending count for each window, subtract to get the displayed change, and label the date and server. If one session lasts twice as long, compare change per minute only as a session calculation, not as the game’s permanent rate.
Your table only needs the target, active conditions, start count, end count, elapsed minutes, and observed change. Leave the formula column empty because the interface does not provide one. Several consistent sessions can help with a personal decision, but they still do not prove global values for every target or server.
FAQ
What are the Followers Game rate boosts?
The spawn sign connects more output per minute with liking the experience, favoriting it, and joining the creator’s group.
How much does each boost add?
The individual values are not documented in the current interface. Check current in-game wording before quoting a number.
Do the three boosts stack?
No stacking method is shown. Do not describe the bonuses as additive or multiplicative.
How quickly does a like, favorite, or group join register?
No detection delay is documented. Record the action time and allow a measured interval before comparing status.
Is the Group task tab the same as the group boost?
No. The task tab is a separate visible category; the boost condition concerns creator-group membership.