Update planner

What it does, in short

• Shows how the game is doing. Players, retention, session length, crashes and revenue this week against last week. What got better, what slipped.
• Plans the next update. Fixes for what hurts players, quality of life, settings players ask for, new content or features that fit your game, codes, and balance changes worth testing first.
• Builds hype before it ships. It can add a short lead-up event: a countdown, a teaser, or “join the group for the code”, so players come back on update day.
• Picks a time to ship. From when your players are actually on: busiest day, busiest hour, their main countries and platforms.

Example

Your day 1 retention slipped, players keep asking for a sprint toggle, and most of your players are in the United States and play on Saturday evenings. The planner proposes “Update 4”: fix the crash in the shop, add a sprint toggle in settings, a new map that fits your progression, a MAP4 code, and a two-day countdown event. It suggests going live Saturday 2 PM New York time, two hours before your busiest hour. You untick what you don’t want and accept. shipLua creates the update, the tasks and the event.

Where the timing comes from

• Hours of the day come from the shipLua SDK (last 14 days). Roblox analytics are daily, so without the SDK shipLua can pick a day but not an hour, and says the hour is a general default.
• Countries and platforms also come from the SDK.
• Roblox and the SDK do not tell anyone how old players are. shipLua never guesses ages.

Plan from inside Studio

Connect Roblox’s official Studio MCP and the shipLua MCP to the same coding agent (Claude Code, Cursor, Codex or VS Code). Then run the plan_next_update prompt. The agent reads the place you have open (what systems it has: codes, shops, quests, settings), reads your numbers from shipLua, and sends the plan to shipLua for you to accept. It only reads the place unless you ask it to change something. Two more prompts: improve_game (the few changes most likely to keep players longer) and fix_from_feedback (finds the scripts behind what players complain about).

No agent? The shipLua Studio plugin’s “Check this place” tells shipLua what the place contains, and the planner uses that instead.

Steps

1. Open your game, then Update planner.
2. Press Plan the next update. The AI reads your numbers and proposes a plan.
3. Review it on the same page or in Approvals. Untick steps you don’t want, accept.
4. Want it every week? Make a scheduled agent on Agents and approvals that can read “Update timing” and propose plans.