
Sword Simulator Tycoon
Target audience: Male · 9–12 · Phone · Casual
Is your update safe to ship?

Open what players have now in Studio → Save as live version

Open your update in Studio → Scan & Test
Check it below: ship, ship after fixes, or don't ship
A good update: new players can now buy the first sword. Fix the new shop error and the tiny message first, then ship.
Fix before you ship
Each one with exact paths and a prompt for your AI. Mark them done: PlaySight re-runs the test.
- 1
Wait for the player's data before the coin check
Tapping Buy too early breaks the shop. In the test, tapping Buy in the first second threw an error 3 times. The new coin check runs before the player's coins have loaded.
In ServerScriptService.ShopHandler, line 64: if the player's data hasn't loaded yet, stop there instead of comparing coins, and show "Loading…" on the Buy button.
- 2
Make the Not enough coins message bigger on phones
The new message is too small to read on phones. StarterGui.ShopGui.Frame.NotEnoughCoins shows at 9 pt on a small phone. Players trying the next sword may miss it, and then Buy seems to do nothing again.
Turn on TextScaled with a UITextSizeConstraint (MinTextSize 18), size the label with Scale, and put it right above the Buy button.
Update-killer risks
- Big riskNew errors1 new error in the playtestErrors the live version doesn't have usually mean something broke: a button that does nothing, a reward that never arrives.
- Worth a lookPhone UINew phone UI problem: Text is too small to read on phonesMost players are on phones: a button they can't tap or text they can't read stops them cold.
Going for it
- New players can buy the first sword right away (60 coins, it costs 50). That's the step where half your target players quit.
- Pressing Buy without enough coins now says why, instead of doing nothing.
- The test player got a first reward after 62 seconds. Before, none in 5 minutes.
- Loading and frame rate are the same as before.
Going against it
- Tapping Buy in the first second throws a new error (3 times in the test).
- The new message is too small to read on a small phone.
- The shop button is still too small on phones. This update doesn't touch it.
Tell players in the update notes
- New players now start with 60 coins: enough for their first sword.
- The shop now tells you when you need more coins, and where to get them.
72-hour watch
Players online, new players coming back, playtime, spending and likes, compared with the days before.
| Number | Before | Now | Change |
|---|---|---|---|
| Players online vs the same time of day in the week before the update | 142 | 158 | +11% |
| Like ratio of new votes 214 votes since the update | 81% | 87% | +6 pts |
| New players coming back next day (D1) 1 day(s) after vs 7 days before | 0.3 | 0.4 | +20% |
| Playtime per player 2 day(s) after vs 7 days before | 20 | 21.6 | +8% |
| Spending per player 2 day(s) after vs 7 days before | 1.8 | 1.9 | +6% |
Every change
6 changes between v41 and v42.
Rewards (1)
- STARTING_COINS in ServerScriptService.PlayerData: 25 → 60 (+140%).
UI (1)
- New button NotEnoughCoins.OkButton ("Got it").
Scripts (3)
- ServerScriptService.PlayerData changed (212 → 214 lines, +2).
- ServerScriptService.ShopHandler changed (164 → 181 lines, +17).
- StarterGui.ShopGui.ShopClient changed (88 → 103 lines, +15).
Size and weight (1)
- Sounds: 12 → 13 (+8%).
Same test, both versions
Measured in Studio on your computer: good for comparing versions, not for absolute speed.
| solo on phone | Live | New |
|---|---|---|
| Script errors | 0 | 3 ▼ |
| Deaths | 0 | 0 |
| Times stuck | 2 | 0 ▲ |
| Seconds stuck | 64 | 0 ▲ |
| Seconds to first reward | – | 62 ▲ |
| Buttons pressed | 6 | 11 ▲ |
| Buttons never found | 1 | 1 |
| Buttons blocked | 1 | 1 |
| Prompts used | 1 | 2 ▲ |
| Places reached | 2 | 4 ▲ |
| Seconds to load in | 6.8 | 6.9 |
| Frame rate (average) | 58.4 | 58.1 |
| Frame rate (slowest 1%) | 41.2 | 40.6 |
| Memory in Studio (MB) | 1412 | 1418 |
| Server frame rate | 60 | 60 |
| Server memory (MB) | 388 | 391 |
New errors
ServerScriptService.ShopHandler:64: attempt to compare nil < number(server, ×3)
UI checks: 2 → 3 problems. New: Text is too small to read on phones. First screen on a small phone: 7 → 7 buttons.
What this check couldn't see
- One test player on one phone per version. A Playtest Lab run with boys 9–12 would show more.