Tutorial · 11 min read · Updated November 2026
How to make a Roblox hero shooter with AI, step by step
A hero shooter is a round game with guns and abilities, and every one of those three parts has a well-known way to go wrong: rounds that stall, hits decided by the client, abilities with cooldowns the client controls. This sequence builds an original hero shooter inside your own Studio with the server deciding every hit, cooldown and reward. Written for Forge; the prompts work with any agent that can act in Studio.
Before you start
- Roblox Studio on a new Baseplate, saved once. Studio ▸ Assistant ▸ ⋯ ▸ Manage MCP Servers ▸ Enable Studio as MCP server.
- Forge Bridge running and paired. Windows only today; Mac is planned.
- Sonnet 5.5 for the build. The weapons step benefits most from a careful read of the summary Forge writes.
Message 1: weapons the server decides
Build two weapon Tools: a raycast Rifle (fire rate 0.12 s, 30 rounds, 12 damage, 25 on a
head hit) and a projectile Launcher (server-simulated with Heartbeat and raycasts between
steps, 60 damage in a 6-stud radius, 1 shot per 1.5 s). The client sends origin and aim on a
Fire remote; the server checks the origin is within 10 studs of the head, the fire rate and
ammo in PlayerData, raycasts or steps the projectile itself, applies damage and tags the
attacker for kill credit, then FireAllClients a tracer and impact effect drawn with ForgeFX.
Reload on R and a mobile button. Ammo and crosshair on the HUD. Playtest on a dummy.
What to check: shoot a wall and confirm the server's impact is where you aimed; fire faster than the rate and confirm extra shots are dropped. Prompt page: Raycast gun with server validation.
Message 2: heroes and abilities
Add 3 original heroes in Config.Heroes (name, weapon, passive, two abilities with damage,
range and cooldown, colour, model). Abilities on E and Q (and mobile buttons): a dash, a
heal zone, a grenade, a shield, a speed boost, a turret, picked per hero. The server validates
cooldown and origin on a Cast remote and broadcasts the effect. A Hero select screen from
the ForgeUI library in the combat style, validated on the server (not mid-round). HUD icons
with cooldown wipes. Playtest each hero, screenshot the select.
Keep the roster in one table so a fourth hero is a table entry and a model. Forge's platforms playbook adds the touch buttons through ContextActionService so they appear on phones only.
Message 3: team rounds and map voting
Add a RoundManager: Lobby (2 players, 1 in Studio), Intermission 15 s with map voting
(3 random maps from ServerStorage.Maps, never the last one, one changeable vote per player,
tie at random), Round 180 s or first team to 30 eliminations, Results 10 s. Teams with
AutoAssignable off and balance within 1; late joiners to the smaller team and spectate until
the next round. Maps cloned into workspace.CurrentMap and destroyed after. Phase, TimeLeft,
scores in RoundState. Playtest alone, screenshot the voting cards.
The loop survives zero players, a leaver and a mid-round joiner, which is the whole point of one script owning it. Prompt pages: Round system and Map voting.
Message 4: kill feed, scoreboard and stats
Add a kill feed (top-right, last 5 entries, attacker, weapon icon, victim, team colours)
from humanoid.Died and the attacker tag on the server. Add a Tab scoreboard (hold Tab or a
mobile button) with kills, deaths, assists and ping per player, built from the ForgeUI
library. Save Kills, Deaths, Wins and Level in PlayerData with XP per kill and win. Show a
level-up moment with ForgeFX. Playtest and screenshot the scoreboard.
Message 5: the combat look and the HUD
Apply the combat lighting look (neutral sun, crisp shadows, light bloom, no haze), one
map at a time. Make the HUD scale-based with CoreUISafeInsets: health bar, ammo, ability
icons, the round timer and team scores from RoundState, a hit marker and a damage direction
indicator on the client. Layer the weapon and ability effects (flash, body, scatter, residue)
and cap them. Check the phone and console presets and screenshot both.
Message 6: skins, saving and the security pass
Add ProfileStore saving (session locked; template with Coins, Kills, Deaths, Wins, Level,
Skins, PurchaseIdCache). Sell weapon skins (recolours and material swaps of the same model)
for coins and as game passes checked on join; a VIP pass with 1.5x XP and a chat tag. Then
review every RemoteEvent handler: Fire, Cast, Choose, Vote, with type checks, whitelists,
distance, rate limits and no trusted amounts from the client. Summarise the changes.
Skins are recolours, not new models, so the catalog grows cheaply. The security pass is where exploit-prone games are saved or lost; Forge's remotes playbook is the checklist it applies.
What it costs
About 3,000 to 6,000 credits ($30 to $60) on Sonnet 5.5 for the six messages. The $60 pack covers a careful run with a second map. Per-step ranges and the optional membership are on the pricing page.
Publishing checklist
- Upload your animations and create the skin passes on the Creator Dashboard; paste the ids.
- Play a round with two clients and confirm hits, kills and scores agree on both.
- Name heroes and abilities yourself; nothing from another game.
- Set the genre to Shooter, publish private, play a round on your phone, then publish public.
Questions
How does the server validate a shot?
The client sends where it aimed. The server checks the origin is near the player's head, checks the fire rate and ammo from its own data, raycasts itself and applies the damage. Tracers and hit sparks are drawn by each client from a broadcast. A client that lies about a hit changes nothing.
Can I test rounds alone?
Yes. Forge sets the minimum players to 1 in Studio and 2 in a live server, and adds a training dummy per map so you can shoot something.
Where do hero models come from?
Forge generates original meshes in one style or uses Creator Store rigs from verified creators, and recolours skins rather than generating a model per skin. Animations must be uploaded by your account or group; Forge asks for the ids.
What does it cost to build?
About 3,000 to 6,000 credits ($30 to $60) on Sonnet 5.5 for the six messages. Weapons and heroes are the system-sized steps; the kill feed and lighting are single steps.
Related guides
- How to make a Roblox anime battlegrounds game with AI: melee combos and abilities with the same server rules.
- How to make a Roblox tower defense game with AI: waves, placement and targeting.
- RemoteEvent security with AI: the validation checklist behind Message 6.
- Round system prompts: lobby, intermission and map voting as one-click pages.