Example gameGet my report

Sword Simulator Tycoon

Target audience: Male · 9–12 · Phone · Casual

Who is your game really for?

Sign up to run this

AI test players vs your real players

10-year-old boy on a phone 15-year-old on PC 20-year-old on PC American teenager

Audience Report from Nov 11, 2026, 6:30 PM · 15 runs

Best audience

Written by PlaySight AI from the facts and predictions below

Right now the game suits teens on PC best. Your target, boys 9–12 on phones, quits at the first shop. Fix the starting coins and the shop button, then advertise to them.

  1. 1
    Teens 13–17 on PCVery sure
    • Back next day: 40% for ages 13–17 and 45% on PC, vs 30% for everyone.
    • They play the longest: 28 min a day on PC.
    • Test players on PC found the shop in 9 of 9 runs.
    Age 13–17 Device PC 15-year-old on PC American teenager
  2. 2
    Boys 9–12 on phones, once the first shop worksFairly sure
    • Your biggest group: 46% of players are 9–12, and 54% are boys.
    • Today only 14% of them come back next day. They quit at the first shop.
    • The 10-year-old test player quit by 2:40 in 3 of 3 runs, with no reward.
    Age 9–12 Gender Male 10-year-old boy on a phone
  3. 3
    Players 18+ on PCA hunch
    • Back next day: 46%, the best of any age.
    • They spend the most: R$ 1.90 per player.
    • Only 12% of your players, so they cost more to reach.
    Age 18+ 20-year-old on PC
Don't spend ads on
  • Phone players, until the shop button is fixed: In 4 of 6 phone runs, test players never found the shop. Back next day: 25% on phones vs 45% on PC. Device Phone 10-year-old boy on a phone
  • Kids under 9: The shortest playtime (12 min), and the tutorial needs reading. Age Under 9

How each persona played

Prediction

AI test players in Studio, not real players. Numbers are the middle run (and the range). Only problems seen in most repeats are shown.

10-year-old boy on a phone Phone · First 5 min · 15-year-old on PC PC · First 5 min · 20-year-old on PC PC · First 5 min · American teenager Phone · First 5 min · American teenager PC · First 5 min ·
Outcome Likely leavesQuits at the first shop Hits problemsStuck at Buy, then finds coins in area 2 Keeps playingEarns coins in area 2, then buys a sword Likely leavesCan't find the shop, quits by 3 min Hits problemsFinds the shop, stuck at Buy
How far they got1 (1–2) place2 (2–3) places3 (3–4) places1 (1–2) place2 (2–3) places
First rewardNone in 3/3 runs142s (118s–171s)96s (81s–120s)210s150s (128s–176s)
Found the shop1/3 runs, opened 1/33/3 runs, opened 3/33/3 runs, opened 3/31/3 runs, opened 1/33/3 runs, opened 3/3
Would likely quit1:58 (1:12–2:40) in 3/3 runs3:05 in 1/3 runsKept playing2:50 (2:20–3:20) in 2/3 runs3:40 in 1/3 runs
Got stuck–Pressed Buy with 25 coins: nothing happened (3/3)Pressed Buy with 25 coins: nothing happened (3/3)–Pressed Buy with 25 coins: nothing happened (2/3)
Never foundNever found the shop button (2/3)––Never found the shop button (2/3)–
GlitchesShop button under the jump button (3/3); Coin counter cut off (2/3)–Sword floats off the hand (2/3)Shop button under the jump button (3/3); Coin counter cut off (2/3)–
OtherNo coin or item in 5 minutes (3/3); Script error in CoinSpawner (3/3)Script error in CoinSpawner (3/3)Script error in CoinSpawner (3/3); Read 64 words of tutorial before moving (3/3)No coin or item in 5 minutes (2/3); Script error in CoinSpawner (3/3)Script error in CoinSpawner (3/3)
Runs3 · 1 one-off problem left out3 · 2 one-off problems left out33 · 1 one-off problem left out3 · 1 one-off problem left out
Notes about these runs (4)
  • Phone runs use a 667×375 screen, a small phone.
  • Every run starts as a new player with 25 coins.
  • The explorer bought the first sword after earning 30 coins in area 2.
  • Test servers had 1 player, so social players found no one to play with.

Glitches found

Fact

Measured in these runs in Studio (picture checks say Guess). Each one, with how to fix it.

  • SeriousShop button is under the jump button6 of 6 runsOn a small phone (667×375) the 28×28 shop button sits under Roblox's jump button. Taps make the player jump instead. Fix: Move OpenButton above the jump button and set a UISizeConstraint with MinSize 44×44.
  • Worth fixingCoin counter is cut off on phones4 of 6 runsThe number runs past the screen edge, so players see "2" instead of "25". They can't tell how many coins they have. Fix: Size StarterGui.HUD.Coins with Scale, not Offset, and turn on TextScaled.
  • MinorGuessSword floats off the hand when swinging2 of 3 runsIn screenshots of the swing, the sword is about a stud away from the hand. Fix: Check the Tool's Grip on ReplicatedStorage.Items.Sword, and that the Handle is the part the hand holds.

Your real players

Fact

2026-10-13 to 2026-11-10. All players: back next day 30%, back in a week 12%, playtime 20 min.

Age
GroupPlayersBack next dayBack in a weekPlaytimeR$ per player
9–1246%20%8%16.4 min0.55
13–1731%40%16%23.8 min1.2
18+12%46%19%26.5 min1.9
Under 911%22%7%12.4 min0.2
Gender
GroupPlayersBack next dayBack in a weekPlaytimeR$ per player
Male54%25%10%17.6 min0.7
Female41%37%15%23.1 min1.2
Unknown5%30%11%19 min0.8
Device
GroupPlayersBack next dayBack in a weekPlaytimeR$ per player
Phone68%25%9%17.2 min0.65
PC22%45%20%28 min1.7
Tablet8%30%12%19 min0.9
Console2%35%14%22 min0.8
Country
GroupPlayersBack next dayBack in a weekPlaytimeR$ per player
United States36%33%14%21.5 min1.3
Brazil13%27%10%18.2 min0.4
Philippines10%26%9%17.9 min0.3
United Kingdom8%32%13%21 min1.1
What this report couldn't see
  • No test player was on a tablet or console.
  • 3 runs per persona: one-off problems are left out.
  • Roblox doesn't split quit points by age, so the quit times are predictions.

Bug test

Every button and buy · phone and PC · 3 players · ~7 min

6bugs found
2serious
121button presses

Ran Nov 11, 2026, 7:10 PM on version 47 · phone · PC × 3 players

  • Serious"Shop" can't be tapped on a phoneCovered by the jump button on a phone; it works on PC.StarterGui.ShopGui.OpenButton Seen on: phone
  • SeriousBreaks with several playersServerScriptService.ShopHandler:41: attempt to index nil with 'Handle'. Happens when two players buy a sword at the same time.ServerScriptService.ShopHandler Seen on: several players
  • Worth fixingScript error during playServerScriptService.CoinSpawner:27: CoinSpawners is not a valid member of Folder "Workspace.Areas.Spawn"ServerScriptService.CoinSpawner Seen on: phone, several players
  • Worth fixingCoin counter is cut off on phonesThe number runs past the screen edge, so players see "2" instead of "25". Fix: Size StarterGui.HUD.Coins with Scale, not Offset, and turn on TextScaled.StarterGui.HUD.Coins Seen on: phone
  • Minor2 buttons seem to do nothingPressed on every device with no visible change: "Codes", "Settings". Fine if they work in the background; otherwise they're broken.StarterGui.MenuGui.CodesButton Seen on: phone, several players
  • MinorGuessSword floats off the hand when swingingIn a screenshot of the swing, the sword is about a stud away from the hand. Fix: Check the Tool's Grip on ReplicatedStorage.Items.Sword, and that the Handle is the part the hand holds.ReplicatedStorage.Items.Sword Seen on: several players
Purchase buttons (3)
  • VIP: Opened the purchase prompt
  • 2x Coins: Opened the purchase prompt
  • 100 Coins: Opened the purchase prompt
3 purchase buttons opened a purchase prompt. Developer products (1) have a ProcessReceipt handler. Game passes (2) are checked in code. No falls out of the map, flings or stuck spots.
  • The phone test used a 667×375 screen, a small phone.