UI Designer

Extras: saving, Robux, passes and more

Extras are ready-made game systems that come inside your UI's export, already wired to it: data saving, Robux products, game passes, daily rewards, codes, admin tools and more. You switch them on for a design and fill in a short form. The code is written for you, in plain Luau with a comment on every setting.

Making a simulator or tycoon? The Simulator and tycoon kit walks through the systems behind its HUD, one page each.

What they cost#

• Studio, Studio Max plan: every Extra is included.
• Other plans: an Extra costs 1 export on the design you switch it on for, from the same exports maps and UIs use (then export credits). You pay once: exporting, downloading or sending that design again never charges for it again, and switching it off and on again is free. On another design it counts again.
• Extras that need other Extras switch those on too (most need Data Saving). Each one counts as an Extra.
• Already exported the design? Adding Extras later only costs the new ones: the export box shows an Add Extras button with the price.

See Plans, credits and exports for the plans themselves.

Switch them on#

1. Open your design on the UI Designer and sign in.
2. Open the Extras panel and switch on the ones you want. The toast tells you what it costs and which other Extras came on with it.
3. Fill in the settings that appear under it, then press Save settings. They start from sensible defaults and from your design: for example, every Robux item in your shop gets its own row in Robux Products, and currency pickers list your UI's currencies.
4. Export the design (or press Add Extras if it is exported already).
5. Install it like any export (Getting started): Send to Studio, the .rbxmx, or the starter place. Press Play: the Extras run with your settings.

Where the files land#

ServerScriptService
└── BloxGame
    ├── Main              Script: starts every Extra, in order (you don't need to change it)
    ├── GameData          ModuleScript: settings, Robux ids and prices (safe to edit)
    ├── Core              ModuleScripts: the shared toolbox (saving, purchases, remotes)
    └── Services          one ModuleScript per Extra (RebirthsService...)
StarterPlayer
└── StarterPlayerScripts
    └── BloxGame
        ├── ClientMain    LocalScript: starts the parts that run on the player's device
        └── Controllers   the device half of the Extras that have one
ReplicatedStorage
└── BloxGame              shared modules, and the remotes made while the game runs

• Every file is tagged with your UI's name, like the hook scripts. Send to Studio adds and updates them in the same undo step as the UI, keeps any file you've edited, and removes the files of Extras you switched off (unless you edited them).
• From the .rbxmx, BloxUI_Setup moves them into place when the game runs, folder by folder, and never replaces what is already there.
• Extras share the UI's saving: their data goes in the same save as the UI's currencies, one server at a time, so a game never runs two save systems.

Change the settings later#

Two ways, pick one:

On the website#

Change the settings in the design's Extras panel and press Save settings, then download or send the design again. That's free: only switching on a new Extra costs anything. With Send to Studio, GameData is replaced with the new values, unless you have edited it in Studio (then yours is kept).

In Studio (GameData)#

Open ServerScriptService > BloxGame > GameData. It's the one file you edit: your currencies, items, Robux products and passes, and every Extra's settings, each with a comment saying what it does. Change a number or a word, press Play, and the game uses it. No website needed.

GameData.Features.daily_rewards = {
	Enabled = true, -- false = this system is off

	-- New day starts at (UTC hour): When the next reward unlocks. 0 = midnight UTC. (a whole
	-- number from 0 up to 23)
	resetHourUtc = 0,
}

Each Extra has its own table in GameData.Features, with Enabled first and then one line per setting from the website's form. Enabled = false switches it off (it stops running; its saved data is kept).

• Keep the commas and the curly brackets { } where they are. Text goes "in quotes"; numbers and true / false don't.
• Robux ids go in GameData.Products (developer products) and GameData.Passes (game passes): the long numbers from the Creator Hub, pasted instead of the 0. When the server starts, they're written into your UI's buttons too.
• GameData only runs on the server, so secrets like codes are safe there. Players only get the parts they need.
• Once you've edited it, sending the design again keeps your copy. To go back to the website's values, delete your GameData and send the design again.
• Exported before GameData existed? Your place has a GameSettings file instead. Export the design again to get GameData.

Extras and your own code#

• Robux purchases: an Extra that sells a developer product (like Robux Products) delivers it itself, saving the gift and the purchase id together before Roblox hears it worked. A UI.Server.onReceipt stub for the same product in <Name>_ServerHooks is ignored, and Output says so. Never set MarketplaceService.ProcessReceipt yourself: UI.Server owns it.
• Product and pass ids: paste each id once, in GameData.Products or GameData.Passes. When the server starts, GameData writes the ids into your UI's buttons, so a button and the Extra that sells it always use the same product. How to make the ids: Robux ids.
• Don't rebuild what an Extra does. If you ask an AI for help, the Copy AI prompt text lists the Extras already in the game so it doesn't write them again (Vibe-code it with AI).
• Problems: each Extra prints to Output with a [BloxGame] prefix, and if one fails the others keep going. If Output says This game's BloxUI is too old for the game systems, install the UI again from the website so the place gets the newest runtime.

Every Extra#

148 Extras, by kind. Each one lists the settings the website's form shows, with their starting values.

• Core: Data Saving, Game Feel (Juice), HUD Bindings, Main Menu & Loading Flow, Rebindable Controls, Settings That Really Work
• Gameplay: Base Builder, Battle Royale Zone, Block Building, Board Grid, Boss Fights, Campfire Nights, Cash Bank, Challenges & Time Trials, Checkpoint Race, Click to Earn, Colony Empire, Combiner (fuse / forge with odds), Converter, Creatures & Wildlife, Deathrun, Descent Run, Detection, Dialogue, Display Shop, Door Run, Emotes, Fashion Show: Dress-Up Runway, Fighter Roster, Flashlight & Battery, Game Music, Gathering, Grow & Steal, Health, Stamina & Ammo HUD, Horror Director, Horror Soundtrack, Infection, Interactables, Keys & Doors, Kill Feed & Scoreboard, Land Grid, Live Minimap, Lives, Maps & Voting, Melee Combat, Minigames, Mobs & Enemies, Movement Gear, Murder Mystery, Obby Stages, Order Queue, Phase Machine, Predator Pack, Quiz Show, RNG Rolls, Racing Kit, Raid Base, Roleplay: Jobs & Homes, Roll Station, Round Mutators, Round Series, Rounds & Match Flow, Rule Runner, Secret Roles, Security Office, Shared Supplies, Simulator Core, Slot Grid, Spawner, Sports Match, Squad Status, Status Effects, Storm Weather, Story Run, Story Runs, Survival Gear, Survival Needs, Survivor Vitals, Switches, Team Select, Teleports & Zones, Throwables, Timed Market, Timing Window, Tower Defense Waves, Tycoon Plots, Unit Roster & Traits, Vehicles, Walk to Earn, Wave Run, Weapon System, Worker Route
• Monetization: Battle Pass, Dev Products Helper, Eggs & Crates, Game Passes, Gifting, Premium Benefits, Robux Products, Rotating Shop, Server Boost, Smart Offers, Spin Wheel, Starter Pack, Timed Boosts, VIP Pass, Weapon Skins
• Progression: Achievements, Collectibles & Journal, Collection Index, Cosmetics In The World, Crafting, Daily Rewards, Inventory & Backpack, Levels & XP, Loadout, Offline Earnings, Pets, Playtime Rewards, Prestige, Quest Tracker HUD, Quests, Rebirths, Stat Points, Stat Tracker, Upgrade Boards, Upgrades, Zone Progress
• Social: Champion Statues, Chat Tags, Departure Board, Global Leaderboards, Group Rewards, Invite Rewards, Lobby & Queue, Parties & Matchmaking, Rare Drop Shout-outs, Trading
• Live ops: Community Goal, Event Rotation, Live Events, Redeem Codes
• Admin & safety: Admin Panel, Anti-Exploit, Bans, Data Tools, Economy Analytics, Soft Shutdown

Core Extras#

Data Saving#

Every player's coins, items, upgrades and settings come back when they rejoin.

• Saves the UI's currencies, upgrades and settings, plus every game system's data
• Locks each player's data to one server, so hopping servers never loses progress
• Saves every minute, when a player leaves and when the server shuts down
• Tries again when Roblox is busy, and tells you in Studio if saving is switched off
• Includes the delete-my-data tool Roblox asks for (Right to Erasure)

Settings in GameData: GameData.Features.saving.

Game Feel (Juice)#

Every important moment gets its own sound, effects and motion: checkpoints light up and chime, coins pop and fly to the wallet, a level up gets a fanfare, 1st place gets everything.

• Its own voice for each moment, sized to it: a coin is a tiny tick that climbs on a streak, a rebirth shakes the screen
• The world reacts to the player: race gates flash and chime higher towards the finish, obby checkpoints light up, buy pads press, gates slide open
• Banners, confetti, rings and number pops for level ups, laps, waves, goals, boss kills, codes and achievements
• Listens to your other systems' events: nothing to wire, nothing doubled where the UI already celebrates
• Light on phones: pooled effects, caps and cooldowns, a reduced-effects setting, follows Reduced Motion and Low Detail

Has a part on the player's device. Settings in GameData: GameData.Features.juice.

HUD Bindings#

One line of code drives any HUD widget: player:SetAttribute("Hud_Objective", "Find the key").

• Every Objective, Counter, Meter, Timer, Compass and Stats row of your design listens to one attribute
• Set it from any script (server or client) and the design updates on that player's screen
• Set it on workspace instead and every player sees it (a round timer, a server goal)
• Or bind a widget to a leaderstat, attribute or stat right here, with no code at all
• The Output lists every widget of your design and the attribute that drives it
• Map NPCs open their window: E (or a tap) at a shopkeeper opens the Shop, an egg seller the Eggs, a quest giver the Quests

Has a part on the player's device. Settings in GameData: GameData.Features.hud_bindings. Setup guide.

Main Menu & Loading Flow#

Players wait behind your main menu with a cinematic camera and spawn when they press Play; the loading bar shows real loading.

• The character spawns when the player presses Play, not behind the menu
• A slow camera fly-over of your map behind the menu (or your own camera spots)
• The loading screen waits until your UI's images and sounds have really loaded, with a real progress bar
• Settings and every other menu button open their windows on top of the menu
• Respawns keep working, and players whose device never shows the menu still spawn

Has a part on the player's device. Settings in GameData: GameData.Features.menu_flow.

Rebindable Controls#

Your Controls screen really rebinds keys and controller buttons, saved per player, with the right keys shown in the HUD.

• Every action in the design's Controls screen and key hints works on keyboard, mouse and controller
• Players rebind a key by clicking it; the new key is saved and comes back next time they play
• Two actions on one key? They swap, so nothing gets lost (or block it, your choice)
• The HUD's key hints show each player's own keys
• Other game systems (weapons, sprint, abilities) add their actions by name in one line

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.keybinds.

Settings That Really Work#

Every switch on your Settings screen changes the real game: hide players and pets, trades, aim assist, speed units, sound, graphics, motion blur and camera smoothing.

• Hide Other Players and Show Other Pets hide them on that player's screen only
• Aim assist for controller and touch players, speed units on the HUD speedometer
• Music, sound effect and ambience sliders turn your game's own sounds up and down
• Low Detail also dims shadows, glow and particles for weak phones (and turns motion blur and smoothing off)
• Trade Requests and Auto-equip Best tell your other game systems what each player wants

Has a part on the player's device. Settings in GameData: GameData.Features.game_toggles.

Gameplay Extras#

Base Builder#

Players build their own base from snap-together pieces (dungeon rooms, treehouse platforms, base modules) as big as you allow.

• Pick a piece, it snaps to a free doorway / edge of your build; green = fits, red = it doesn't
• The server checks every piece: it must join a free socket, not overlap, stay in bounds
• Kits from your own models (sockets are Attachments) or simple boxes; any size of build is saved
• Construction time per piece, and harvesters that grow fruit you pick and sell (or that just pay)
• Always a next goal on the HUD with a guide path; on Tycoon Plots' plots or its own build plots

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.base_builder.

Battle Royale Zone#

The battle royale loop: drop in from the sky, outrun a shrinking storm, be the last one standing, then spectate the rest.

• A storm circle that shrinks in phases you set, with a glowing wall and damage outside it
• The drop: everyone rides the drop aircraft across the island, jumps over land (SPACE, a tap, A on a gamepad), skydives and lands under a parachute
• Players pick a drop zone on the design's Drop Zones screen and are dropped there by themselves
• The design's storm timer and players-left counter run live; eliminations reach the kill feed
• Last one standing wins: results, rewards, wins and eliminations saved for leaderboards
• Eliminated players spectate the survivors until the next match

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.battle_royale.

Block Building#

Skywars / bedwars building: place blocks on a grid to bridge and wall up, mine them back with a pickaxe, all checked by the server and cleared every round.

• Blocks snap to a grid that meets the map's ground; a see-through block always shows where the next one goes, red with the reason where it can't; the server checks it all again
• Look past the edge of the block you stand on and the next one goes outward: a bridge laid by walking; mouse, phone and gamepad, holding keeps building
• A pickaxe mines blocks back (and map blocks tagged MineableBlock, with ore rewards); players start each round with a stack, mining refills it up to a cap
• The map's chests are loot chests: blocks, a better sword, apples and potions (the middle's are richer)
• Every block is cleared when a round ends; sandbox mode keeps and saves each player's build instead

Has a part on the player's device. Settings in GameData: GameData.Features.block_building.

Board Grid#

A board game table: pieces with their own moves, turns, captures, a win and a bot opponent when you play alone.

• Any grid from 3x3 to 12x12 with pieces that step, slide or leap
• The server checks every move: whose turn, the piece's pattern, a clear path
• Take the enemy king (or leave them no move) to win the game's prize
• A bot takes the empty seat, so one player can always play
• Click a piece, then click where it goes

Settings in GameData: GameData.Features.board_grid.

Boss Fights#

A real boss with phases and a slam attack drives the design's BossBar live, shares its rewards by damage dealt, and comes back on a timer.

• Spawns your boss model (or a ready-made placeholder) that chases and hits players
• Gets angrier at low health: faster, stronger, with a telegraphed ground slam
• The design's BossBar shows its real name and health to everyone nearby
• Rewards are split by how much damage each player did, plus an item for the top damager
• Counts 'Bosses Slain' for leaderboards, quests, achievements and the profile screen

Has a part on the player's device. Settings in GameData: GameData.Features.boss_fights.

Campfire Nights#

A co-op night-survival run round one campfire: gather by day, feed the fire to grow its safe light, survive the nights while creatures hunt outside it.

• The campfire's fuel sets a safe ring of light: creatures never hunt inside it, and it shrinks as the fire burns down
• Day and night with a night counter: chop wood, search scrap and pick food by day, keep the fire alive through the night
• Feeding the fire levels it up: a wider light and new rings of the forest to gather in
• A crafting bench with real items (a sharper axe, a bigger sack, a lantern, camp upgrades) and lost campers to bring home
• The run ends when everyone is down or the last night is survived: a Results screen, rewards, a fresh run

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.campfire_nights.

Cash Bank#

Cash you carry drops when you die and anyone can grab it. Bank it at the vault by the spawn to keep it; no banking while in combat.

• What a player earns is carried until they bank it: dying drops a share of it as a bag anyone can pick up
• A vault by the spawn banks it with one press; the bank turns a player in combat away
• Everyone sees how much a player carries over their head: who is worth chasing
• Banking never moves the currency, so it can't be used to farm quests, levels or achievements
• The carried amount is saved: leaving the game doesn't make it safe

Needs: Data Saving. Settings in GameData: GameData.Features.cash_bank.

Challenges & Time Trials#

Time trials from a start line to a finish line, timed by the server, with medals, best times and a global leaderboard.

• A start part and a finish part (or your BloxMaps obby) make a time trial; the server keeps the time
• Gold, silver and bronze par times with rewards, and every player's personal best is saved
• A global leaderboard of the fastest times
• A challenge of the day with a twist: no jumping, low gravity, super speed...
• Fills your design's Challenges screen and shows a live stopwatch

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.challenges.

Checkpoint Race#

Race through checkpoints in order, lap after lap, against the clock and your own saved best time.

• Checkpoints count only in order: no cutting corners
• One lap or many, timed from the start line
• A personal best that saves, with pay for every finish and a new best
• On foot or in any vehicle the player sits in
• A map without checkpoints gets a tidy loop of gates round the spawn

Settings in GameData: GameData.Features.checkpoint_race.

Click to Earn#

Makes your design's big CLICK button pay for real: server-checked clicks, boosts, and an auto-clicker pass.

• Every tap on the Clicker pays the currency it shows, saved on the server
• Rebirths, boosts, pets and VIP multiply what a click pays
• Stops click-spam cheats with a speed limit (auto-clickers allowed or not, your choice)
• Sell an Auto Clicker game pass: it clicks for the player, even while they explore
• No Clicker in your design? One in its own look appears so it works right away

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.click_to_earn.

Colony Empire#

Build an empire of little creatures: roll them from the queen, fill a growing nest, they carry food home, sell it when the live price is high.

• Six plots round a hub, a Home button, the next step on the HUD and a guide path for new players
• Made of general blocks: roster, roll station, displays, slot grid, workers, timed market, boards, events, converter
• The format's Robux ladder: Cash x2 -> x30 (always the next one on the HUD), cash packs that scale, a 3 R$ starter pack
• EFF and online leaderboards in the hub

Needs: Data Saving, Unit Roster & Traits, Roll Station, Display Shop, Slot Grid, Worker Route, Timed Market, Upgrade Boards, Event Rotation, Converter. Has a part on the player's device. Settings in GameData: GameData.Features.colony_empire.

Combiner (fuse / forge with odds)#

A fuse machine or forge: N ingredients in, one result out, every possible result and its odds shown live before you commit, a timing bar for better luck.

• Fill the slots (4 pets, 7 ores...): the possible results and their % update live, rarity colours and mutations
• Rarer and more ingredients mean better odds; the odds shown are exactly the odds the server rolls
• A timing bar before the roll: Good x1.4 luck, Perfect x2 (the zone narrows for rarer ingredients)
• A free pity guarantee, an optional Guaranteed Upgrade product, Skip and Fast passes (never for players Roblox restricts)
• Works on any game's items: the pets of a pet game, a forge's ores and gear, or your own lists

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.combiner.

Converter#

A machine in the hub that turns spare units into boosts: fill it, start it, collect after the timer.

• Spare units go in (the Units list's Convert); their worth fills the machine
• Start it: a cycle (5 minutes by default), then collect the reward at the machine
• Rewards by how full it was: speed boosts, a mutation potion at 100%, half its worth in cash
• A Robux skip finishes the cycle at once

Needs: Data Saving, Unit Roster & Traits. Settings in GameData: GameData.Features.converter.

Creatures & Wildlife#

Animals that live in your world: deer and rabbits that wander and bolt when you come close, cows and chickens that graze by the barn, a horse you can ride, a fox that follows you, wolves that hunt. They walk, run, eat and attack on their own legs.

• Herds: say which animal, how many and how it behaves (wander, flee, graze, hunt, follow, mount)
• Every animal moves by code on its own skeleton or parts: it plays in any game, no animation uploads
• Mounts: walk up, press the prompt, ride; jump to get off
• Hunters chase and bite, by night only if you like; prey runs away and comes back when it's calm
• Light on the server: one loop for every animal, the motion is drawn on each device

Has a part on the player's device. Settings in GameData: GameData.Features.creatures.

Deathrun#

Runners race the course while the killer fires the traps: reach the end to win, or be the killer who stops them all.

• Every round one killer (fair: the longest wait is likeliest) at killer speed, everyone else runs
• The killer fires traps from buttons on the map (each once a round), or from a trap bar on any course
• Runners who reach the finish win; the killer wins when no runner makes it
• Coins for finishing, for staying alive, and for the killer per runner stopped
• Works with Rounds and Maps & Voting: a new course every round

Needs: Rounds & Match Flow, Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.deathrun.

Descent Run#

A co-op escape run along a staged route: an opening, areas and checkpoints on the way down or out, a vehicle (or exit) at the end to start and board, and who made it out.

• A short opening (no signal, your friends, the goal far away), then the route: the map's own areas and checkpoints, in order
• Shortcuts: a gated passage and ziplines you switch on from below; a player carried off walks back down the way they came
• The vehicle at the end (a car, a truck, a van...): unlock it, hold to start it (progress is kept), board, leave together or on a countdown
• One fair look at everyone when it leaves: who escaped, who was left behind, who made it out with the whole party
• Escapes, rescues, no-firearm runs and whole-party runs are saved and unlock looks (only worn when chosen)

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.descent_run.

Detection#

Guards and cameras that spot players in a vision cone: a suspicion meter, hiding spots, sneaking and an alarm.

• Any tagged part becomes a watcher that sees players in a cone (walls block its sight)
• A suspicion meter fills while a player is seen and drains when they're not; full = caught
• Hiding spots and sneaking help players stay unseen
• Motion mode: only players who move while watched get caught (freeze when it turns!)
• Other systems hear every spot and catch, and can catch a player themselves

Settings in GameData: GameData.Features.detection.

Dialogue#

NPCs that talk: a dialogue box with the speaker's name, typewriter text you can skip, choices that branch, and hooks for quests.

• Tag a model DialogueNPC: players get a Talk prompt beside it
• Lines type out (tap to skip), choices branch the conversation
• Choices can give items, start a quest step or fire your own event
• Write a whole conversation in one line of settings (see the help text)
• The server walks the conversation: a device can't skip to a reward

Has a part on the player's device. Settings in GameData: GameData.Features.dialogue.

Display Shop#

What a roll gives sits on displays on your plot with its price: buy the one you want; the next roll replaces the rest.

• Each display shows the unit itself (its model), its name, tier colour, stat and cash price
• "New!!" on a unit you've never owned
• Buy with the display's prompt; the unit joins the roster (and a free slot)
• The map's Podium<n> markers, else a tidy row of podiums

Needs: Data Saving, Unit Roster & Traits. Settings in GameData: GameData.Features.display_shop.

Door Run#

A room-by-room horror run: ride the elevator, open numbered doors one by one, hide from what hunts the halls, and make it to the last door.

• Every run is different: hand-built rooms snapped together from a seed, numbered doors, locked rooms with the key inside
• Eight original threats, each with a clear warning and a way to survive it: hide, look, look away, run, crouch
• Drawers full of Brass to spend at the porter's desk halfway, lanterns and flashlights that run out, a pre-run shop in the lobby
• A library puzzle, chases, a dark conservatory and a boiler-room finale; tips after every death, spectating, one revive per run
• Only the rooms near the players are loaded (mobile friendly); elevators in the lobby take groups of up to 4 (Lobby & Queue)

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.door_run.

Emotes#

The design's emote wheel and emote window play real animations, with optional paid emotes through game passes or items.

• Every emote on the design's wheel and in its emote window really plays
• Starts with Roblox's own public emotes (wave, point, three dances, laugh, cheer, salute)
• Paste any animation id to add your own; loops keep going until the player moves
• Sell emotes: lock one behind a game pass (the buy prompt opens) or an item
• Works on phones, R15 and R6 characters

Has a part on the player's device. Settings in GameData: GameData.Features.emotes.

Fashion Show: Dress-Up Runway#

A dress-up runway show every round: a theme, a race to get dressed, a walk down the runway, star votes from the room and the judges, and a podium.

• Every show picks a theme (no repeats until every theme was used) and everyone gets dressed against the clock
• Models walk the runway one by one while everyone else rates the look from 1 to 5 stars
• The judges score how much you wear and how well it fits the theme, so a show played alone still works
• Top 3 stand on the pose stage; coins for taking part, for every star and for the podium
• Saved stars give a rank title and a chat tag; pieces tagged vip need the VIP Closet pass

Needs: Rounds & Match Flow, Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.fashion_show.

Fighter Roster#

Pick a fighter and brawl: a free-for-all battlegrounds with four moves and an ultimate per fighter, or best-of-3 duels.

• The fighters screen really picks your fighter: health, speed, power, defence and a kit of four moves and an ultimate
• Battlegrounds: everyone in the arena at once, a four-hit combo, blocks and parries, knockback, KO streaks, back in seconds
• Or 1v1 duels in an arena: ROUND 1, FIGHT!, K.O., first to 2 round wins
• Punch, kick, block, dash and an ultimate on keys, gamepad and the design's touch buttons
• Every hit, knockout and reward decided on the server; KOs and streaks saved; practice bots so you can test alone

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.fighter_roster.

Flashlight & Battery#

A real flashlight that runs out: the battery drains on the design's battery meter, pickups and spare batteries refill it.

• A flashlight tool that lights the way (F, the design's Flashlight button, or a click)
• The battery drains while it's on and shows on the design's Battery meter, flickering when it's low
• Battery pickups in the world (parts tagged Battery) and spare batteries from your shop
• Night vision and zoom when your design has them
• Saved: the battery level comes back after a rejoin

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.flashlight.

Game Music#

Upbeat background music for any game that isn't horror: a playlist from Roblox's licensed-for-all library, picked by mood and shuffled per game.

• Tracks every account can play (Roblox's licensed APM library, each id checked to load in other people's games)
• Moods: cheerful pop, playful, chill; the game's seed shuffles the order so no two games start the same
• Loops the playlist with a short gap, through your design's Music slider
• Your own uploaded tracks play first in your own games (the tracks setting)

Has a part on the player's device. Settings in GameData: GameData.Features.game_music.

Gathering#

Trees and rocks you gather by hitting them: each hit pays a share of the node, better tools take fewer hits and keep more.

• Hit a tree or a rock with a tool: every hit pays its share of Wood, Stone, Metal or Sulfur at once
• Hit the glowing weak spot for double, and the last hit pays a finishing bonus
• Tools from a rock (25 hits, 37 % kept) to a power drill (9 hits, all of it); tools wear out and can be repaired
• Nodes stay at a count per area: a used-up tree grows back somewhere else, never under a base
• Every hit checked by the server: the tool you hold, its swing time, its reach, the spot you hit

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.gathering.

Grow & Steal#

The grow-and-steal loop: buy seeds before the restock, plant them on your own plot, harvest and sell, and sneak onto other gardens to steal ripe crops while they're unlocked.

• Every player gets a garden plot (the map's plots, or tidy placeholder plots), saved and regrown on every visit
• A seed stall with a restock timer; bushes and trees keep fruiting up to a cap (caught up while you're away), root crops are pulled whole
• Every crop and fruit rolls a size (now and then a HUGE one) and stacks mutations (Wet + Chilled = Frozen); sell with every boost
• A gear shop of timed sprinklers: placed on your plot, they speed up growth and grow bigger fruit in their radius
• Steal a ripe crop from an unlocked plot; owners lock their base (free, with a cooldown) or buy a long lock
• Sells Base Lock, Restock Seeds, Instant Grow and three passes; on a bases map (conveyor + pedestals) it plays steal-a-creature

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.grow_garden.

Health, Stamina & Ammo HUD#

The design's health, stamina, ammo and readout bars show the real numbers, with an optional sprint system.

• The hotbar equips your real Tools and shows each one's ammo; ammo counters follow the equipped Tool
• Hold Shift (or tap Sprint on phones) to run: stamina drains, recovers and is checked by the server
• Counters, meters, the compass and a boss bar come alive from simple attributes your scripts set
• Weapon makers just set the Tool attributes Ammo, MaxAmmo and Reserve; everything else is automatic

Has a part on the player's device. Settings in GameData: GameData.Features.hud_stats.

Horror Director#

A monster that really hunts your players: it patrols, sees, hears, chases, catches, and your gameover screen works.

• A monster that patrols, spots players, listens for running and chases with real pathfinding
• The Fear meter and vignette rise as it gets close; a jumpscare when it catches you
• Hide in closets and lockers (parts tagged HidingSpot, or the map's hide spots) to lose it
• The design's gameover screen works: Retry, Revive (Robux or your revive currency) and Spectate; with Lives, a catch costs a life
• Easy to Nightmare difficulty; drop your own monster model in ServerStorage > BloxGame > Monsters

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.horror_director.

Horror Soundtrack#

Every horror game its own sound: ambience, tension, chase themes and a lobby track picked for THIS game, mixed as the hunt goes.

• A set picked from Roblox's licensed-for-all library by the game's seed, setting and monster: no two games sound the same
• Follows the run: a calm bed, tension as the monster nears, a chase theme, silence when you got away, the bed again
• The lobby has its own calm track (a lobby place never sounds like the run); every new run plays another bed
• Modest volumes, through your design's Music slider; your own ambience and chase music ids play in the set's place

Has a part on the player's device. Settings in GameData: GameData.Features.soundtrack.

Infection#

Tag-style infection rounds: the infected catch survivors (by touch or by a kill), every catch spreads it, survivors win if one is left at the end.

• Every round starts with a few infected (fair: the longest wait is likeliest), the rest survive
• An infected player who reaches a survivor turns them, or a kill by an infected does
• The infected are a bit faster and glow green; survivors see how many are left
• Survivors win when time runs out with anyone left; the infected win when nobody is
• Works with Rounds and Maps & Voting; rewards for surviving and for every catch

Needs: Rounds & Match Flow, Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.infection.

Interactables#

Stations and objects players can use: press E, click or touch, with a cost, a cooldown, items and a reward.

• Any tagged part becomes usable: a prompt, a click or a touch
• Each use can cost money, need an item, give an item and pay a reward
• A cooldown per player, checked by the server
• Parts that appear later (spawned ones) work too; a map without them gets a tidy station by the spawn
• Other systems hear every use and can perform one themselves

Settings in GameData: GameData.Features.interactables.

Keys & Doors#

Find the keys, unlock the doors, collect what the exit needs and escape: an objective chain that builds itself from the map.

• Keys appear at the map's key spots, in a different place every run
• Locked doors and a locked exit that only their key opens; normal doors open and close
• Objective items (fuses, pages...) the exit needs, and an objective on the HUD that always says what's next
• Monsters push doors open while they hunt; every door makes a noise they hear
• A note pinned to each locked door tells a piece of the story

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.keys_doors.

Kill Feed & Scoreboard#

Real kills from any weapon fill the design's kill feed, scoreboard and team score, and tell your other systems.

• Works with any weapon that sets Roblox's standard "creator" tag (most kits already do)
• The design's kill feed, Tab scoreboard (kills, deaths, streaks, teams) and team score go live
• Kill streak shout-outs, a kill marker on your crosshair, optional coins per kill
• Levels, Quests, Achievements and Rounds hear every kill through the event bus

Has a part on the player's device. Settings in GameData: GameData.Features.kill_feed.

Land Grid#

A plot of land bought tile by tile: owning a tile puts its neighbours up for sale, and every tile you own grows loot to walk over and collect.

• Walk onto a tile that's for sale to buy it; the tiles next to it go up for sale, so the land grows the way the player walks
• Prices come from the map: distance from the plot's start x the tile's tier, with no price table to write
• Every owned tile grows a pile piece by piece; a bigger pile takes longer and pays more (value x pieces)
• The far land is a higher tier: dearer, with better loot
• The map's own tiles (a Land folder and a StartPoint in each plot) or a tidy field of tiles that fills any plot from its front edge
• A rebirth resets the land; Collect All and a whole-server Mega Harvest sell for Robux

Needs: Data Saving. Settings in GameData: GameData.Features.land_grid.

Live Minimap#

The design's minimap shows the real map, your team and every point of interest, and opens into a full-screen map.

• A top-down view of YOUR map, drawn live (terrain, parts and meshes), that follows the player
• Markers for you, your team and friends, spawns, shops, zones, quest targets, a battle royale storm and anything you tag
• Tap the minimap (or press M) for a full-screen map with zoom, pan and a waypoint beam
• Works on any map, with or without BloxMaps markers; huge maps just get a coarser picture
• Phone friendly: a light 3D block model in a ViewportFrame that only redraws when you move

Has a part on the player's device. Settings in GameData: GameData.Features.minimap.

Lives#

A few lives per run, hearts on the HUD, back at your checkpoint after each death, and extra lives for Robux when you run out.

• Each run starts with a few lives; every death (a monster, a fall) costs one
• Back at the last checkpoint you reached, or out of lives: spectate the others
• Extra Life and a lives pack for Robux, given once per purchase and saved first
• Out of lives? Play as the monster (a Robux option) and hunt the survivors

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.lives.

Maps & Voting#

Several maps in one game: players vote between 3 during the intermission, the winner loads for the round and is cleaned up after.

• Put your maps in ServerStorage > Maps: each round one is cloned in and removed after
• A vote between 3 maps in the lobby (ties are random, no votes = random)
• Every map comes up before any repeats (no map twice in a row)
• Each map can set its own round mode, length, name and picture
• Works with Rounds, Minigames, Murder Mystery and the lobby queue

Has a part on the player's device. Settings in GameData: GameData.Features.map_vote.

Melee Combat#

The design's Attack, Block, Dodge, Dash, Ability and Ultimate buttons really fight: server hitboxes, combos, parries, knockback and cooldowns on the buttons.

• Punches and slashes with combos, blocks and perfect-timing parries, dashes with dodge frames
• A light string with an ender; blocks that answer: guard breaks, perfect blocks, counters and grabs, NPCs on the same rules
• Abilities: shockwaves, fireballs and heals, each with its own cooldown shown on the Hotbar and buttons
• The server finds who got hit (hitboxes, walls, distance), so nobody can hit from across the map
• Knockback, a combo counter, damage numbers, and the standard 'creator' tag so kills count
• Works on phones with the design's buttons; moves can cost stamina when a stamina system is on

Has a part on the player's device. Settings in GameData: GameData.Features.melee_combat.

Minigames#

A different minigame every round, each building its own arena: a lava tower to climb, falling tiles, a colour floor, king of the hill, a jump race, a maze...

• Each round is a minigame with its own goal: last standing, race to the finish, most points or survive
• Every minigame builds its own arena for the round (a lava tower, tiles that fall, a maze...), dressed with your map's models, then takes it down
• Only minigames your map can really play are picked; every one comes up before any repeats, a special one every few rounds
• The lobby sees the next minigame and its arena; countdowns tell everyone when the lava rises or the floor drops
• Flood mode: the lava never outpaces a steady climber, and it speeds up when most players survive

Needs: Rounds & Match Flow. Settings in GameData: GameData.Features.minigames.

Mobs & Enemies#

Enemies that chase and fight: zombie waves that rise out of the ground and hunt you, monster camps with loot, health bars, rewards for the kill. Server-run and light on the network.

• Waves: zombies rise out of the ground near you and hunt you down, more and tougher each wave, a boss every few waves
• Real bodies with no setup: the owner's zombies (R6, Roblox's own animations and sounds) or a themed body for any name
• Camps: put a part tagged MobSpawner anywhere, its mobs guard it, chase intruders and walk home when led too far
• Loot tables with the odds, XP and coins for the kill (credited to whoever landed the blow)
• A wave counter, health bars and damage numbers, drawn on each device

Has a part on the player's device. Settings in GameData: GameData.Features.mobs.

Movement Gear#

A Jetpack in the shop really flies: owned movement gear (jetpack, jet boots, gravity coil, pogo, double jump, dash) changes how its owner moves.

• Any item or game pass whose name says jetpack, rocket pack, jet boots, gravity coil, moon boots, pogo, double jump or dash works the moment a player owns it
• Jetpack: hold Jump in the air to fly up, with a fuel gauge that drains, refills on the ground and warns when it's low
• Touch buttons on phones, the gamepad's A / B, and the design's own Jetpack keybind
• The server decides: it checks you own the gear, keeps the fuel and switches Roblox's own physics forces on and off

Has a part on the player's device. Settings in GameData: GameData.Features.movement_gear.

Murder Mystery#

Murderer, Sheriff and Innocents: secret roles, a knife you swing or hold to throw, a one-shot gun the hero can pick up, coins from every kill.

• Every round: one Murderer, one Sheriff, everyone else Innocent (fair: who waited longest gets the knife)
• The Murderer clicks to swing and holds to throw the knife; the Sheriff has a pistol that reloads in 3 s
• Shoot an innocent and you die too; a fallen Sheriff drops a floating gun for the first innocent
• A kill pops coins out of the body for the killer; assassin mode: everyone hunts a target
• Every hit is checked on the server: reach, line of sight, travel time, cooldowns

Needs: Rounds & Match Flow, Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.murder_mystery.

Obby Stages#

Obby checkpoints that save: players come back to their stage, can skip a stage for Robux and get a prize at the finish.

• Works with BloxMaps obby checkpoints, or any part tagged "Checkpoint" with a Stage number
• Saves each player's stage; returning players spawn right where they left off
• A "Skip Stage" Robux product (plus Skip 5) from GameData, the most common obby purchase
• Stage counter on the player list, back-to-any-stage teleports, pay for every new stage and a finish reward
• Cooperates with BloxMaps kill bricks and moving parts instead of replacing them

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.obby_stages.

Order Queue#

Customers line up with orders: serve them before their patience runs out for pay and a quick-service tip.

• A new customer every few seconds, up to a set number waiting at once
• Serve the oldest order you can: bring the item it asks for, or just serve
• Pay for every order, plus a tip that shrinks the longer they waited
• A customer who waits too long walks off (and can cost the last server a penalty)
• Works with any game's items and currency: kitchens, deliveries, shops, daycares

Settings in GameData: GameData.Features.order_queue.

Phase Machine#

The game moves through phases (lobby, round, intermission, turns) with their own clocks, round and round.

• A list of phases, each with its own length; 0 seconds waits until another system moves it on
• A phase can wait until enough players are in the game
• A turn phase hands turns round the players, a few seconds each
• Other systems and game rules hear every phase start and end
• Works beside Rounds: it keeps its own phase and never touches the round timer

Settings in GameData: GameData.Features.phase_machine.

Predator Pack#

Predators that hunt as a pack (wolves, bears, coyotes, hyenas, raptors, hounds, any beast or creature): they stalk, warn, bite, lunge, and can seize a player and drag them to their lair unless they fight free or a friend rescues them.

• A pack that patrols, investigates noise, stalks between the trees, warns, attacks, recovers and retreats: never spawning beside a player
• Bites, and lunges with a visible warning; a well-timed shove interrupts one attacker
• The grab: the predator drags its captive away while everyone watches; hold Fight Free, kick when it opens, or use the weapon in your hand
• Friends free a captive with one weapon hit, a short Help Friend hold, or a flare held close
• Fail the struggle and you wake in the lair with your gear, capped health and a few seconds to walk out
• Fair by design: nearby and attacking predators are capped by party size, one drag at a time, a calm spell after every big encounter

Has a part on the player's device. Settings in GameData: GameData.Features.predator_pack.

Quiz Show#

A quiz on a big board: players answer by stepping on a pad, with points for speed and a streak.

• Your own questions with up to four choices, shuffled fairly
• Players answer by stepping on a coloured pad (or a HUD button)
• Faster right answers score more, and a streak counts them in a row
• One answer per player per question, checked by the server
• Other systems hear every question and answer

Settings in GameData: GameData.Features.quiz.

RNG Rolls#

Roll for rare auras or titles: a "1 in 1,000,000" ladder, a slot-machine reveal, luck boosts and Auto Roll.

• Press Roll: the server rolls a "1 in X" ladder and the reveal spins to it
• Luck stacks: luck passes x luck potions (Robux) x the server's Lucky Hour
• Quick Roll and Auto Roll game passes, the odds always on screen
• Rare rolls are announced to the whole server; the best one can be equipped as a chat tag
• Everything rolled is saved and shows in the Index and Inventory as items

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.rng_rolls.

Racing Kit#

A complete race loop: grid, 3-2-1-GO, checkpoints and laps that can't be cut, live positions, nitro, drifting and a garage that tunes every car.

• Laps and checkpoints from your track (BloxMaps gates or Parts tagged RaceCheckpoint), passed in order: no shortcuts
• Live position and lap on the HUD, a countdown start, results with best laps, rewards and leaderboards
• Nitro and drift meters, respawn to the last checkpoint, and a placeholder car and track until you add yours
• Never alone: bots fill the empty grid slots and take places in the results (they never earn or save)
• A real garage: every car keeps its own tuning (Engine, Turbo, Tyres...) bought in the design's Upgrades screen
• Works on its own or inside the Rounds system; the server decides every lap, position and reward

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.racing_kit.

Raid Base#

Build a base anywhere from grid pieces, upgrade twig to steel, keep it with a claim cabinet's upkeep, and raid other bases.

• Foundations, walls, doorways, windows and floors snap to a grid; build as twig, upgrade in place to wood, stone, metal, steel
• Pieces stand on what's under them: break a support and what it held falls
• A claim cabinet: only its authorised list can build nearby; its store pays a daily upkeep or the base decays
• Raid other bases: each tool takes a set number of hits per material, charges blow walls open, a hit base can't build for 60 s
• Everything checked and saved by the server; health bars, a tier-coloured build ghost and the cabinet's upkeep panel

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.raid_base.

Roleplay: Jobs & Homes#

Real jobs with uniforms and paychecks, homes on plots with a lockable door, a wardrobe that dresses you and vehicles.

• The Jobs screen's buttons start a job: uniform, team, chat tag and a paycheck every few minutes
• Buying a home in the Homes screen builds it on a plot, one per player, with a door only you can open
• The wardrobe's Wear really changes your avatar, and it's still on when you come back
• Workplaces clock you in (a JobTask's job), car pads spawn their vehicle, a plot's own house is claimed as it stands
• Premium homes, premium cars and double paychecks come with their passes; nothing a client can fake, all saved

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.roleplay.

Roll Station#

A free roll at a station on your plot: N results fly out (eggs, crates, cards) with luck, a tier cap you level up, and lucky procs; the odds are always shown.

• Press the station (or the HUD's Roll): N results (an upgrade board) land on the displays and hatch
• Weighted tiers: 1 in N each at luck x1; luck makes the rarer tiers likelier (x luck^0.6)
• The station's level caps the rarest tier (an upgrade board levels it)
• Procs: a Super egg (big luck), x2 and x8 luck eggs, a token instead of a result
• Robux packs (1 of 5 with a mutation, odds on screen; never shown where Roblox restricts paid random items)

Needs: Data Saving, Unit Roster & Traits. Has a part on the player's device. Settings in GameData: GameData.Features.roll_station.

Round Mutators#

Between rounds, players chip in coins for one twist on the next round for everybody: low gravity, speed, fog, overtime or a rush clock.

• A board per mutator in the lobby: walk up, pay with the game's own currency, and the NEXT round has that twist for everyone
• Low gravity, speed, moon jump, thick fog, a longer round, or a rush clock that every finisher cuts
• Everyone is told who bought it; it is cleared the moment the round ends
• One per round by default (first come), so every round can be a different game
• A sink for earned currency that needs no Robux and works with any round game

Needs: Rounds & Match Flow. Settings in GameData: GameData.Features.round_mutators.

Round Series#

Rounds become a match: the first player to win three rounds takes it, with a prize, a lobby board and a champion's mark.

• Counts every round win; the first to the target takes the match and the count starts again
• A tie at the top is settled by the next round
• The match prize is paid in the game's own currency, once per match
• A board in the lobby: the match, the standing, the last champion
• Works with any round game: last standing, most kills, races, minigames

Needs: Rounds & Match Flow. Settings in GameData: GameData.Features.round_series.

Rounds & Match Flow#

A real round loop: lobby, intermission countdown, the round on your map, and the design's results screen with real stats and rewards.

• Lobby, intermission countdown, 3-2-1-GO, the round, then results, on repeat
• Win by last one standing, most kills, first to the finish line, or surviving the timer (teams too)
• Players are teleported to the map's spawn markers and back to the lobby afterwards
• The design's timer and objective show the countdown; its Victory screen shows placement, kills, time and rewards
• The server decides everything: kills, finishes, placements and the coins it pays out

Has a part on the player's device. Settings in GameData: GameData.Features.rounds.

Rule Runner#

The game's own rules as data: when something happens, if a condition holds, do a few things.

• Rules like "when a coin is touched, add 1 score" or "when score reaches 100, win"
• Scores, meters, timers and stats per player, saved where you want them
• Wins and losses with what happens next (a new round, results, the next level)
• Bounded: a rule can't fire too often or set off an endless chain; a broken rule is skipped
• Works with the other gameplay blocks: stations, spawners, customers, phases

Settings in GameData: GameData.Features.rule_runner.

Secret Roles#

A few players get a secret role each round; meetings, votes, and one side wins.

• A few hidden players each round; everyone else is the town
• Each player only ever learns their own role
• Meetings on a timer, from a button or a report; the most-voted player is out
• A tie or a skip sends nobody out
• The town wins when every hidden player is out; the hidden win when they are as many as the rest

Settings in GameData: GameData.Features.secret_roles.

Security Office#

A real night shift: doors, lights and cameras on a failing power supply, animatronics that creep closer, nights 1-5. Or an anomaly shift: spot what changes in the rooms on the cameras and report it before 6 AM.

• The design's doors, lights, mask and camera panel really work; each one uses power
• Animatronics move from camera to camera and try to get in; the server decides every move
• Survive until 6 AM on the night clock; nights 1-5 get harder, winning pays and unlocks the next
• Anomaly shift: a chair goes missing, a lamp flickers, a figure stands in a corner; report the room and the kind
• Cameras show parts tagged SecurityCam; the Nights screen shows what's unlocked
• A placeholder office and camera rooms are built so it plays the moment you press Play

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.security_office.

Shared Supplies#

Shared loot containers, four inventory slots each, drop / hand over / swap, and quick pings for a co-op survival run.

• Containers take a second to open and show EVERYONE what's inside; players take single items
• Four slots each: a weapon takes one, bandages and flares stack to two, ammo sits beside the revolver
• A full inventory offers a swap; drop supplies or hand them to a friend
• The run's loot is rolled once from its seed (rare weapons on a run budget) and never rerolled
• Pings for Danger (named after the game's threat), Supplies, Come Here and Help; a lost player's things wait in a pack

Has a part on the player's device. Settings in GameData: GameData.Features.shared_supplies.

Simulator Core#

The simulator loop for any theme: train a stat, break or catch things on the map, better tools, bosses, a bag to sell, zones and rebirths, all checked by the server.

• Pick a theme (mining, walls, pets, fishing, lifting, bubble gum, clicker, RNG, speed) or write your own rows
• Works on any map: the map's Breakable markers (or parts you tag SimNode) become ores, walls or fishing spots
• Tools and bags to buy, bosses that ask for a recommended stat, a world-finish bonus, a sell pad
• The server does every hit, catch and sale: distance, speed, zone and order are checked
• Pets, rebirths, boosts and passes multiply the stat and the earnings

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.sim_core.

Slot Grid#

Owned slots that grow in stages (a nest's floors, a hive's rings, a barn's rows): unlock each slot, place units, Equip Best.

• Stages add slots on any curve (1, 3, 6, 10, 15, 21, 28 by default); each slot is unlocked on its own at a rising price
• Press a slot: unlock it, put your best spare unit in, or level the unit up; F takes it out
• Every slot shows its unit (name, tier colour, mutation, level, stat); the frame takes the tier's colour
• Equip Best fills every slot with the best units; new units move into a free slot by themselves
• The map's nest (SlotAnchor_<n>, FloorAnchor_<f>) or a tidy stepped mound that grows with each stage

Needs: Data Saving, Unit Roster & Traits. Settings in GameData: GameData.Features.slot_grid.

Spawner#

Things keep appearing at map markers every few seconds, up to a cap, and can vanish after a while.

• Each kind of thing its own tag, place, timing and cap
• An optional lifetime: things vanish on their own after a while
• The game's own model by name, else a tidy stand-in (or a character)
• Spawned things can be used, collected or destroyed by the other systems
• Other systems hear every appearance and removal

Settings in GameData: GameData.Features.spawner.

Sports Match#

A real football match: a server-owned ball, pass, shoot and tackle, goals on the score bug, a match clock and results.

• Pass, charged power shots and tackles on keys, gamepad and the design's touch buttons
• Goals, kick-offs, the match clock, the score bug and kit bonuses (pace, shooting, passing, stamina) all run on the server
• End-of-match results with goals, assists, shots and pass accuracy, plus coin rewards
• Bots fill both teams (a keeper too), so one player gets a full match; players who join take their places
• Tag parts "Goal", "Ball" and "TeamSpawn" (BloxMaps stadiums already have them), or press Play and use the placeholder pitch

Needs: Data Saving. Has a part on the player's device. Settings in GameData: GameData.Features.sports_match.

Squad Status#

The design's team widget shows your real teammates: their names, live health and whether they're alive, downed, escaped or out, with hold-to-revive.

• Your team (or everyone, in co-op games) fills the design's TeamStatus portraits
• Live health bars, and Alive / Downed / Dead / Escaped / Caught states
• Downed players can be revived by a teammate holding E (or tapping and holding on a phone)
• Round and horror Extras report downed and escaped players; scripts can too

Has a part on the player's device. Settings in GameData: GameData.Features.squad_status.

Status Effects#