Round and Minigame System
This job hires a scripter to build the engine round based games run on: the lobby that gathers players, the countdown, the round itself with its timer and win checks, scoring, rewards and the rotation that picks the next map or mode. The flow is written into the scope before payment; escrow holds the money until a full round plays end to end.
BLOXWORK, the most trusted Roblox developer marketplace in the world.
Your money stays held until you approve the finished work. Only then does the dev get paid.
How escrow worksEvery dev shows ID to earn the Verified badge. The document stays private. Only the badge is public.
About the badge10% of the job, never more than $1,000. No buyer fees. Nothing stacked on top.
The fee ruleWhat this job involves
The scripter builds the state machine your whole game hangs from: intermission, voting or rotation, teleport and setup, live round, resolution, rewards, reset. Each state has entry rules, exit conditions and failure handling, because rounds meet every edge case multiplayer owns: players leaving mid round, joining late, a server emptying at the worst moment, a win condition met by a player who just disconnected. The engine’s real quality is measured in those moments, not in the happy path demo.
Around the machine sit the systems players actually see: map and mode rotation with voting where scoped, timers that stay honest, scoring and placement, round rewards saved properly, spectator handling for the eliminated, and an intermission worth spending, shops, results, the next round’s promise. A round game is a rhythm; this system is the drummer.
What a good delivery looks like
A full session played in your game: lobby fills, round runs, every win and loss path resolves, rewards land, the next round starts without a hitch, and the rude tests pass, a player leaves mid round, the server drops to one player, the timer expires on a tie. Your approval pass is a play session, not a code read, because this system’s promises are all behavioural.
Growth seams belong in the delivery: new maps enter the rotation by configuration, new modes plug into the round states without surgery. Round games live on fresh rotation content; an engine that needs a rebuild per map is a tax on your game’s whole future, and the scope should say the rotation must extend.
What a round system costs in the open market
Scripters here set their own prices. Engine work prices in the scripting band, Innovecs’ 2026 guide puts Luau scripters at roughly $25 to $90 per hour, and a complete round engine with rotation, scoring and rewards typically lands in the low to mid hundreds of dollars, more with voting, spectators and many modes at launch. It is the core system of its genre, and it prices like one.
The comparison that matters is against building your game on a weak engine: every mode, event and update you ever ship stands on this machine, and its edge case failures become your game’s review section. A scoped engine, tested through full sessions under escrow, is the foundation purchase of the whole title.
Why escrow fits a round engine
Round engines are too behaviour heavy to buy on promises and too large to buy on screenshots, which is precisely escrow’s home ground: the state flow written into the scope as the test script, the payment held while the build runs, and approval following a played session that walks the states and the edge cases in your own game. Done has a definition both sides signed before the money moved.
Scripters gain the fixed target professionals prefer: the flow they priced is the flow they are judged by, mode requests beyond it are new scope with new quotes, and a running engine in a live round game is the strongest systems portfolio there is.
Intermission is a feature
The minutes between rounds decide whether a session becomes an evening: results worth reading, a shop that tempts without trapping, friends gathering in a lobby that feels like a place rather than a waiting room. When you scope the engine, scope the intermission’s contents with the same care as the rounds, because players spend a startling share of their lives there, and games that treat it as dead time leak players at every single break.
Design the break’s rhythm honestly: long enough to breathe, buy and regroup, short enough that the next round always feels imminent. Timers players can see, a ready state that respects the eager, and results that celebrate the round’s stories, closest finish, biggest comeback, are the difference between a lobby and a loading screen with furniture.
The engine should surface the intermission’s data too: how long players stay between rounds, where they drift away. That quiet metric predicts a round game’s health better than round completions do, because players rarely quit mid round; they evaporate in the gaps, and the gaps are yours to design.
Taking jobs now
1 verified scripters is listed in this category on BLOXWORK right now:
How hiring works here
The scope is in writing before you pay. BLOXWORK holds your money. It does not go to the dev yet.
Work runs against the agreed scope and delivery time. Revisions in the package are tracked on the order.
Check the work. Only your approval releases the pay, minus the 10% fee capped at $1,000.
The fee, in plain words
BLOXWORK takes one fee: 10% of the order, and never more than $1,000 on any job, however big the job gets. A $100 job pays a $10 fee and the developer receives $90. A $10,000 job pays $1,000. A $25,000 job still pays $1,000, and the developer receives $24,000. Buyers pay nothing on top of the price they see. The full fee rule.
Are you a Roblox scripter?
Keep 90% of every job. The fee never takes more than $1,000, even on a $25,000 job where a 20% platform takes $5,000. Your pay sits in escrow before you start and lands in USD when the client approves. Show your ID once, wear the Verified badge, and let clients trust you on sight.
Questions, answered
What should the flow description include?
Every state in order, what starts it, what ends it, and what players see and can do inside it. Then the edge cases: leaving and joining mid round, emptying servers, ties, and what happens to rewards in each. If a moment can occur in your game, its handling belongs on this list.
Voting or fixed rotation?
Voting gives players agency and keeps favourite maps in heavy rotation; fixed rotation guarantees variety and simpler pacing. Many games hybrid: vote among three. Decide by your game’s community shape and name it in the scope; the engine supports either, but switching later is real work.
Can new maps be added without the scripter?
They should be: the delivery standard to name in the scope is configuration driven rotation, your maps registered with their settings in one place. Adding content is your weekly job as an owner; an engine that makes it a scripting invoice has failed its main purpose.
How are round rewards handled?
Placement based payouts saved through your data system, validated server side like every earning in a serious game. If rewards feed shops, currencies or leaderboards, name those connections in the scope so the engine ships wired to them, not adjacent to them.
What does the approval session need?
Enough players to fill a round honestly, friends or testers, and the edge case script: a mid round leave, a late join, a tie at the timer. One full rotation through every map and mode in the launch set. An hour of real play is the test; anything less is a demo.
Keep going
Ready when you are
Browse the marketplace with escrow on every order, or put your own work in front of the clients arriving here.



Devs verified with real ID
One fair fee