Gobrix Studio Docs

Getting started

Gobrix Studio is where you make Gobrix games. A game is a place: a world of parts, models and scripts, saved as a .gbrx file on your computer.

Studio opens on the Home page. Start from a template (Baseplate, Obby, Tycoon and more), open a place from your computer, or pick one of your recent places. You can get back to it any time with File › Home.

• File › New Place Ctrl+N, Open Place Ctrl+O, Save Ctrl+S and Save As Ctrl+Shift+S work like any other program. File › Open Recent lists the last 10 places you used.
• File › Import Parts copies the parts from another place into the one you have open, along with that place's Environment settings.
• Studio saves a backup of unsaved work every 3 minutes. If Studio closes unexpectedly, open the backup from Autosave backups on the Home page.

The Studio window

Ribbon

The tool bar at the top, with four tabs: HOME (tools, clipboard, inserting parts, testing), MODEL (parts, grouping, constraints, inserting objects), TEST (Play, Run, Stop) and VIEW (show or hide panels and the grid).

Viewport

The 3D view of your world in the middle.

Explorer

Everything in your game as a tree, under World, Players, Environment and Teams. Click to select, right-click for more options, use + to insert objects, and press F2 to rename. While you're testing, it also shows the players and their characters.

Properties

Settings for whatever you've selected: name, color, size, surfaces and more.

Output

Messages from Studio and your scripts (print, warnings and errors).

Moving the camera

Building

Inserting parts

Click Part on the ribbon for a block, or use its little arrow (or the MODEL tab) for other shapes. New parts land on the ground in front of the camera.

Tools

Moving snaps to a 1-unit grid, so parts line up easily.

Selecting, copying and grouping

• Ctrl+click parts to select more than one.
• Copy Ctrl+C, Cut Ctrl+X, Paste Ctrl+V, Duplicate Ctrl+D, Delete Del.
• Undo Ctrl+Z and Redo Ctrl+Y.
• Group Ctrl+G puts the selected parts in a Model, so you can move them together. Ungroup Ctrl+U takes them back out.
• Folders help you organize the Explorer. They don't change how anything works.
• Anchor on the ribbon locks parts in place. Anchored parts never move, not even when something hits them.

Parts and properties

Select a part and change it in the Properties panel.

Every part is smooth plastic: there are no materials, just colours, so every build has the same bright brick look.

Welds, hinges and joints

Joints come from the surfaces of parts. When the game starts, every face joins its part to whatever touches that face:

Use the Surface tool on the toolbar: pick a surface, then click faces of parts. Parts that are snapped, welded or glued together move as one solid piece, and if any of them is anchored the whole piece stays put.

For a joint between two parts you choose, use Insert › Joint (advanced): pick one, click the first part, then click the second part. Press Esc to cancel. Parts joined this way don't collide with each other.

Create Store

The Create Store has Free Models (ready-made builds), Decals (images) and Meshes (3D models) that anyone can use in their games. Everything in it is made by players and checked by a moderator.

• Search by name, creator or ID. Each asset's page shows its ID and how to use it.
• Upload your own on Create › Decals or Create › Meshes. Once approved, it's in the store for everyone.
• In Studio, the Decal and Mesh properties have a button that opens the store.

Toolbox and Free Models

The Toolbox (the toolbox button on the toolbar, or View › Toolbox) shows the Create Store right inside Studio, down the left side.

• Pick Free Models, Decals or Meshes, and search by name, creator or ID.
• Click a Free Model to drop it in front of the camera. It comes in selected, ready to move.
• Click a Decal to stick it on the selected part's front, or a Mesh to insert a MeshPart.
• Create Store at the bottom of the Toolbox opens the store in your browser.

Publishing your own: sign in, select a Model (or a part), and choose File › Publish to Create Store. Studio takes a picture of it, then a moderator checks it. You can insert your own models from the Toolbox (My Models) straight away.

Free models can contain scripts. Check what they do in the Explorer before you publish a game with one.

Decals

Decals put a picture on a face of a part, like a sign, poster or logo.

1. Find one in the Create Store, or upload your image on Create › Decals (once a moderator approves it, it's in the store). Note its Decal ID.
2. In Studio, select a part and insert a Decal (ribbon or right-click › Insert Object).
3. Set its Texture to the Decal ID and its Face to the side it should go on (Front, Back, Top, Bottom, Left or Right).

Meshes (MeshParts)

A MeshPart is a part shaped like a 3D model from the Create Store: a chest, a tree, a car.

1. Find a mesh in the Create Store and note its Mesh ID, or upload your own .obj (with an optional PNG or JPG texture) on Create › Meshes. In Blender: File › Export › Wavefront (.obj).
2. In Studio, choose Insert Object › MeshPart.
3. In Properties › Mesh, type the ID into MeshId and press Enter. Once it downloads, the part takes the mesh's own size.

• The mesh stretches to fill the part's Size, so you can resize it like any part.
• A mesh with a texture shows its texture; without one it uses the part's Color.
• MeshParts collide as a box the size of the part.
• Scripts: local part = Instance.new("MeshPart"), part.MeshId = "12", part.Parent = workspace.

Sounds and Audio

A Sound plays Audio from the Create Store in your game: music, footsteps, a coin pickup. (Needs Gobrix Studio 0.2.7 and Gobrix 0.7.6.)

1. Find a sound in the Create Store › Audio, or upload your own on Create › Audio (MP3, OGG or WAV; a moderator checks it first).
2. In Studio, open the Toolbox, choose Audio and click a sound (right-click › Preview to hear it). It adds a Sound to the selected part, or to the World. Or use Insert Object › Sound and type the Audio ID into SoundId.
3. Turn on Playing to start it when the game starts, and Looped to repeat it (music).

• A Sound in a part is heard around that part and fades out with distance. Anywhere else (the World, a Model, a Folder) everyone hears it the same everywhere.
• Volume: 0 is silent, 1 is full. PlaybackSpeed: 2 plays it twice as fast and an octave higher.
• Scripts: sound:Play() starts it from the top, sound:Stop() stops it, sound.Playing says whether it's playing (a one-shot sets it back to false when it ends).

-- A coin that plays a sound when touched (put a Sound named "Ding" in the coin)
local coin = script.Parent
coin.Touched:Connect(function(hit)
    coin.Ding:Play()
end)

Environment

Select Environment in the Explorer to change the time of day and the mood of your game.

Testing your game

While you're playing: WASD walk, Space jumps, hold the right mouse button to look around, the mouse wheel zooms, and Shift turns on shift lock.

Press Esc for the game menu. It lists the players in the server, has settings (volume, camera sensitivity, invert camera, FPS counter and, in the game, fullscreen), and buttons to Reset Character R, leave L, or resume Esc.

Publishing

1. Log In with your Gobrix account using the button at the top of Studio.
2. Choose File › Publish to Gobrix.
3. Go to Create on the website, where your game shows up. Click it to set its name, description and thumbnail, and choose who can play.

To update a game, publish it again. Players get the new version the next time they join.

Multiplayer

• Up to 12 players can be in one server. When it's full, the next players get a new server of the same game.
• Scripts run on one player's game (the host), and what they change is sent to everyone.
• When you push a loose part, your game takes over simulating it, so shoving things around feels smooth.
• Click a name on the player list (or in the Esc menu) to send a friend request or view their profile. A heart marks your friends.

Tools

Tools are things players hold: swords, blasters, building tools. A Tool's part named Handle goes in the character's right hand, and its other parts come along around it.

1. In the Explorer, click + next to StartingTools (or right-click › Insert Tool). You get a Tool with a Handle.
2. To build it, uncheck In StartingTools (those tools aren't in the world), then build around the Handle and check it again. The Handle goes in the fist of the outstretched arm with its Front face pointing up (a sword built pointing toward -Z is held upright) and its Top facing back; the other parts come along around it.
3. Put a Script inside the Tool. Activated fires when the player clicks while holding it.

• Tools in StartingTools are given to every player each time their character spawns. They aren't in the world while you edit or play.
• A Tool in the World is picked up by touching its Handle (Insert Object › Tool).
• Players press 1–9 (or click the hotbar) to hold a tool, press the key again to put it away, click to use it, and press Backspace to drop it.
• Properties: ToolTip, Enabled, RequiresHandle, CanBeDropped, GripPos (where on the Handle the hand holds it) and GripRotation (how it's turned in the hand, in degrees around the Handle's own X, Y and Z).
• Setting up the grip: select the Tool in Studio and a character appears next to it, holding a copy exactly like in game. Change GripPos and GripRotation (or use the Turn 90° buttons) and watch it update. Meshes often need a quarter turn or two.

A simple sword

local tool = script.Parent
local swinging = false

tool.Handle.Touched:Connect(function(hit)
    local humanoid = hit.Parent:FindFirstChildOfClass("Humanoid")
    if swinging and humanoid and hit.Parent ~= tool.Parent then
        humanoid:TakeDamage(25)
    end
end)

tool.Activated:Connect(function()
    swinging = true
    local anim = Instance.new("StringValue")   -- plays the slash animation
    anim.Name = "toolanim"
    anim.Value = "Slash"                       -- or "Lunge"
    anim.Parent = tool
    task.wait(0.35)
    anim:Destroy()
    swinging = false
end)

Aiming with the mouse

local tool = script.Parent

tool.Activated:Connect(function()
    local player = game.Players:GetPlayerFromCharacter(tool.Parent)
    local mouse = player:GetMouse()
    print("Clicked on", mouse.Target, "at", mouse.Hit.Position)
end)

Teams

Teams split players into groups. The player list groups players by team, and name tags take the team's color.

1. In the Explorer, click + next to Teams (or right-click › Insert Team). Each new team gets its own color.
2. Select a team to set its Name, TeamColor and AutoAssignable. New players join the AutoAssignable team with the fewest players.
3. To give a team its own spawn, select a SpawnLocation, turn off Neutral and pick the team in the Team list. Neutral spawns are used by everyone.

Changing teams with a script

local Teams = game:GetService("Teams")
local red = Teams:FindFirstChild("Red Team")

script.Parent.Touched:Connect(function(hit)
    local player = game.Players:GetPlayerFromCharacter(hit.Parent)
    if player and red then
        player.Team = red
    end
end)

Scripting basics

Gobrix scripts are written in Luau, a fast, friendly scripting language based on Lua. If you have written Lua before, you'll feel at home.

• Insert a Script (ribbon › Script, or right-click › Insert Object) into the World or into a part. Double-click it to edit.
• When the game starts, every enabled Script runs, in the order they appear in the Explorer.
• script is the Script itself, so script.Parent is whatever it's inside.
• print() and warn() write to the Output panel. Errors show up there too, with the line number.
• Loops must wait. A script that runs for 5 seconds without waiting is stopped with an error, so while true do end can't freeze your game. Put task.wait() in every loop.

The server and the players (LocalScripts)

A Gobrix game has two sides:

• The server runs Scripts. In a multiplayer game that's the host's computer; what server scripts change (parts, Environment, the leaderboard, health) is sent to everyone.
• Each player's own game runs LocalScripts. They see the same world and get the keyboard, the mouse and the camera, but what they change in the world only that player sees.

Containers in the Explorer

SharedStorage

Both sides can see it. Keep RemoteEvents, ModuleScripts and models to clone here. Nothing in it is in the world.

ServerVault

Only Scripts see it: maps, prizes and tools waiting to be cloned in. LocalScripts can't use it.

ServerScripts

Scripts that run on the server, out of the way of the World.

PlayerSetup › PlayerScripts

LocalScripts here run once on each player's game when they join.

PlayerSetup › CharacterScripts

Copied into each character when it spawns, so script.Parent is the character. LocalScripts run on that player's game, Scripts on the server.

Drag things onto these rows to move them, or right-click a row › Insert Object.

RemoteEvents: talking across

Make a RemoteEvent in SharedStorage in Studio (right-click SharedStorage › Insert Object, or its +). Then:

-- LocalScript (PlayerScripts)
local remote = game.SharedStorage:WaitForChild("Shout")
remote:FireServer("Hello!", Vector3.new(1, 2, 3))

remote.OnClientEvent:Connect(function(text)
    print("The server says", text)
end)

-- Script (ServerScripts)
local remote = game.SharedStorage.Shout
remote.OnServerEvent:Connect(function(player, text, position)
    print(player.Name, "said", text)
    remote:FireAllClients(player.Name .. " shouted!")   -- or remote:FireClient(player, ...)
end)

A RemoteFunction asks and waits for an answer: the server sets remote.OnServerInvoke = function(player, ...) return ... end and a LocalScript calls local answer = remote:InvokeServer(...). Arguments can be numbers, strings, booleans, tables, Vector3, Color3, CFrame, parts, objects and players.

More ways for scripts to work together

ModuleScript

local lib = require(game.SharedStorage.Lib) runs it once (per side) and gives back what it returns, usually a table of functions. It can't wait() at its top level.

BindableEvent / BindableFunction

Scripts on the same side: bindable:Fire(...) with bindable.Event:Connect(f); bf.OnInvoke = function(...) return x end with bf:Invoke(...).

ClickDetector

Put one in a part (or a Model). Clicking it fires detector.MouseClick:Connect(function(player) ... end) on the server and on the clicking player's LocalScripts. Also RightMouseClick, MouseHoverEnter, MouseHoverLeave (LocalScripts) and MaxActivationDistance (32). The cursor turns into a hand over it.

Message / Hint

A Message with Text in the World dims everyone's screen with big text in the middle; a Hint shows a bar along the top. Change Text or Destroy() it.

Debris

game:GetService("Debris"):AddItem(thing, seconds) destroys it later.

Input and the camera

These work in LocalScripts.

local UIS = game:GetService("UserInputService")
UIS.InputBegan:Connect(function(input, gameProcessed)
    if gameProcessed then return end            -- typing in the chat
    if input.KeyCode == Enum.KeyCode.E then
        print("E pressed")
    elseif input.UserInputType == Enum.UserInputType.MouseButton1 then
        print("click at", input.Position.X, input.Position.Y)
    end
end)

local mouse = game.Players.LocalPlayer:GetMouse()
mouse.Button1Down:Connect(function()
    print("clicked", mouse.Target, mouse.Hit.Position)
end)
mouse.KeyDown:Connect(function(key) print(key) end)   -- the character typed: "e", " "...

local camera = workspace.CurrentCamera
camera.CameraType = Enum.CameraType.Scriptable
camera.CFrame = CFrame.new(Vector3.new(0, 50, 30), Vector3.new(0, 0, 0))

UserInputService

Events InputBegan, InputEnded, InputChanged (mouse movement, the wheel) with an input that has KeyCode, UserInputType, UserInputState, Position and Delta. IsKeyDown(Enum.KeyCode.X), IsMouseButtonPressed, GetMouseLocation(), GetKeysPressed(), MouseBehavior (Enum.MouseBehavior.LockCenter locks the cursor in the middle), MouseIconEnabled.

Mouse (player:GetMouse())

Live in LocalScripts: Hit, Target, Origin, UnitRay, X, Y, ViewSizeX/Y, TargetFilter, Icon. Events Button1Down/Up, Button2Down/Up, Move, WheelForward, WheelBackward, KeyDown(key), KeyUp(key). In a server Script, a Tool's Equipped(mouse) mouse has Hit, Target and Button1Down/Up.

ContextActionService

BindAction(name, function(name, state, input) end, false, Enum.KeyCode.F, ...) and UnbindAction(name).

workspace.CurrentCamera

CFrame, CameraType (Custom follows the character, Scriptable goes where you put it, Fixed stays put), CameraSubject (a part to follow instead of the character), FieldOfView, ViewportSize, ScreenPointToRay(x, y), WorldToScreenPoint(position).

Players.LocalPlayer

This player (only in LocalScripts). RunService:IsClient() is true there.

Seats, conveyors and body movers

Seat

Insert › Seat. Characters sit when they touch it, facing its front (-Z), and Space gets up. Scripts: seat.Occupant (a Humanoid), seat.Disabled, humanoid.Sit, humanoid.SeatPart, humanoid.Seated:Connect(function(sitting, seat) end); humanoid.Sit = false stands them up.

VehicleSeat

Weld it to a car. Sitting in it, W/S drive the car along the seat's front and A/D turn it. MaxSpeed, Torque, TurnSpeed, and Throttle / Steer (-1, 0, 1) for scripts. Wheels on hinges roll along. In multiplayer the driver's game drives the car.

Conveyors

Anchor a part and give it a Velocity (Properties › Conveyor, or part.Velocity = Vector3.new(10, 0, 0)). The part stays put; whatever stands on it, characters and parts, is carried along at that speed.

Body movers

Put one inside a part. BodyVelocity (Velocity, MaxForce, P) pushes toward a speed, BodyPosition (Position, MaxForce, P, D) pulls to a spot and holds it, BodyGyro (CFrame, MaxTorque) keeps it turned a way, BodyForce (Force) is a constant push, BodyAngularVelocity (AngularVelocity, MaxTorque) spins it. They push whatever the part is welded to as well.

More values

ObjectValue (a part or object), Vector3Value and Color3Value.

Script examples

Kill brick

Put this Script inside a part. (Or just turn on the part's KillsOnTouch property.)

local part = script.Parent

part.Touched:Connect(function(hit)
    local humanoid = hit.Parent:FindFirstChild("Humanoid")
    if humanoid then
        humanoid.Health = 0
    end
end)

Leaderboard (leaderstats)

A folder named leaderstats inside a player shows its values on the leaderboard.

local Players = game:GetService("Players")

Players.PlayerAdded:Connect(function(player)
    local leaderstats = Instance.new("Folder")
    leaderstats.Name = "leaderstats"
    leaderstats.Parent = player

    local coins = Instance.new("IntValue")
    coins.Name = "Coins"
    coins.Value = 0
    coins.Parent = leaderstats
end)

Coin you can collect

Put this inside a part. It works with the leaderboard script above.

local coin = script.Parent
local Players = game:GetService("Players")
local taken = false

coin.Touched:Connect(function(hit)
    local player = Players:GetPlayerFromCharacter(hit.Parent)
    if player and not taken then
        taken = true
        local coins = player.leaderstats.Coins
        coins.Value = coins.Value + 1
        coin.Transparency = 1
        task.wait(5)          -- comes back after 5 seconds
        coin.Transparency = 0
        taken = false
    end
end)

Spinning part

Put this inside an anchored part.

local part = script.Parent

while true do
    part.CFrame = part.CFrame * CFrame.Angles(0, math.rad(3), 0)
    task.wait()
end

Disappearing platform

local platform = script.Parent

while true do
    task.wait(2)
    platform.Transparency = 0.8
    platform.CanCollide = false
    task.wait(2)
    platform.Transparency = 0
    platform.CanCollide = true
end

Day and night cycle

local Environment = game:GetService("Environment")

while true do
    Environment.ClockTime = (Environment.ClockTime + 0.01) % 24
    task.wait(0.1)
end

Speed pad

local pad = script.Parent

pad.Touched:Connect(function(hit)
    local humanoid = hit.Parent:FindFirstChild("Humanoid")
    if humanoid then
        humanoid.WalkSpeed = 40
        task.wait(3)
        humanoid.WalkSpeed = 16
    end
end)

Make parts with a script

for i = 1, 10 do
    local part = Instance.new("Part")
    part.Size = Vector3.new(4, 1, 4)
    part.Position = Vector3.new(i * 5, 2 + i * 2, 0)
    part.Color = Color3.fromRGB(255, 80, 80)
    part.Anchored = true
    part.Parent = workspace
end

Scripting reference

Everything Gobrix scripts can use today.

Globals

game, workspace (or world), script

The game, the World and the running Script. game:GetService(name) gets World, Players, RunService, Environment, Teams, StartingTools, SharedStorage, ServerVault, ServerScripts, PlayerSetup, UserInputService, ContextActionService or Debris.

require(moduleScript)

Runs a ModuleScript once and returns what it returned.

Instance.new(className, parent?)

Makes a Part, WedgePart, SpawnLocation, MeshPart, TrussPart, Seat, VehicleSeat, Model, Folder, Decal, Sound, the values (IntValue, NumberValue, StringValue, BoolValue, ObjectValue, Vector3Value, Color3Value), Humanoid, Team, Tool, RemoteEvent, RemoteFunction, BindableEvent, BindableFunction, ClickDetector, the body movers, Message, Hint or Explosion.

task.wait(t), task.spawn(f), task.delay(t, f), task.defer(f), task.cancel(thread)

Waiting and running code later. The older wait, spawn and delay work too.

print, warn, tick(), time(), typeof(v)

Output, time and type helpers.

Value types

Vector3

Vector3.new(x, y, z), .zero, .one, .xAxis/.yAxis/.zAxis. Fields X Y Z, Magnitude, Unit. Methods Dot, Cross, Lerp, FuzzyEq, Abs, Floor, Ceil, Min, Max. Math with + - * /.

CFrame

A position plus a rotation. CFrame.new(x, y, z), CFrame.new(pos, lookAt), CFrame.lookAt, CFrame.Angles(rx, ry, rz), fromEulerAnglesXYZ/YXZ, fromOrientation, fromAxisAngle, CFrame.identity. Fields Position, LookVector, RightVector, UpVector, X Y Z. Methods Inverse, Lerp, ToWorldSpace, ToObjectSpace, PointToWorldSpace, PointToObjectSpace, VectorToWorldSpace, VectorToObjectSpace, ToEulerAnglesXYZ/YXZ, ToOrientation, GetComponents. cf * cf and cf * vector work.

Color3

Color3.new(r, g, b) (0 to 1), Color3.fromRGB(r, g, b) (0 to 255), fromHSV, fromHex("#ff0000"). Fields R G B. Methods Lerp, ToHSV.

BrickColor

BrickColor.new("Bright red"), BrickColor.Random(), BrickColor.Red() and friends. Fields Name, Color.

Enum

Enum.Material (kept so old scripts run; every part stays Plastic), Enum.NormalId, Enum.PartType, Enum.RaycastFilterType, Enum.KeyCode, Enum.UserInputType, Enum.UserInputState, Enum.CameraType and Enum.MouseBehavior, e.g. Enum.NormalId.Top.

Every instance

Name, Parent, ClassName, Destroy(), Clone(), FindFirstChild(name, recursive?), FindFirstChildOfClass, FindFirstChildWhichIsA, FindFirstAncestor…, WaitForChild(name), GetChildren(), GetDescendants(), IsA(class), IsDescendantOf, IsAncestorOf, GetFullName(), ClearAllChildren(), GetAttribute, SetAttribute, GetAttributes, GetPropertyChangedSignal(prop). Events: Changed, ChildAdded, ChildRemoved, Destroying.

Events: event:Connect(f) returns a connection you can :Disconnect(). There's also event:Once(f) and event:Wait().

Part

Position, Size, CFrame, Orientation, Rotation, Color, BrickColor, Transparency, Anchored, CanCollide, Shape, Locked, Velocity / AssemblyLinearVelocity, AssemblyAngularVelocity, Elasticity, KillsOnTouch, Mass, MeshId (MeshParts). Methods ApplyImpulse(force), ApplyAngularImpulse, GetMass(), GetTouchingParts(), BreakJoints(). Events Touched(otherPart) and TouchEnded(otherPart).

Model and Folder

Model: PrimaryPart, GetPivot(), PivotTo(cframe), MoveTo(position), SetPrimaryPartCFrame, TranslateBy(offset), GetBoundingBox(), GetExtentsSize(). Folder just holds things.

Parts can go in the World, a Model or a Folder, but not inside another part (group them in a Model instead).

Values, Decals and Scripts

IntValue, NumberValue, StringValue and BoolValue have a Value and a Changed event. Decal (inside a part) has Texture (a Decal ID), Face and Transparency. A Script has Enabled. A Sound has SoundId (an Audio ID), Volume, PlaybackSpeed, Looped and Playing, and Play(), Stop(), Pause() and Resume().

Players

Players

GetPlayers(), GetPlayerFromCharacter(model), GetPlayerByUserId(id), RespawnTime, MaxPlayers. Events PlayerAdded, PlayerRemoving.

Player

Name, DisplayName, UserId, Character, LoadCharacter(), Team, TeamColor, Neutral, Backpack, GetMouse() (Hit, Target, Origin: where the player last clicked). Events CharacterAdded, CharacterRemoving. A leaderstats folder inside shows on the leaderboard.

Character

A Model with a Humanoid, Head, Torso, HumanoidRootPart and the arms and legs. Move it with character:PivotTo(cframe).

Humanoid

Health, MaxHealth, WalkSpeed (16), JumpPower (50), RootPart, TakeDamage(amount), EquipTool(tool), UnequipTools(). Events Died, HealthChanged.

Name tags

Put a Humanoid in any Model that has a part named Head, and the Model's name shows above the head, like a player's. Handy for signs and buttons.

Services

World

Raycast(origin, direction, params?) with RaycastParams.new() (FilterType, FilterDescendantsInstances), returning Instance, Position, Normal, Distance and Material. Also GetPartBoundsInRadius(pos, radius), GetPartBoundsInBox(cframe, size), Gravity and DistributedGameTime.

RunService

Events Heartbeat(dt), Stepped, RenderStepped. IsServer(), IsClient(), IsStudio().

Environment

ClockTime, TimeOfDay, Brightness, FogStart, FogEnd, FogColor, Ambient, OutdoorAmbient, GeographicLatitude, GetMinutesAfterMidnight(), SetMinutesAfterMidnight(m).

Tool

Enabled, RequiresHandle, ToolTip, CanBeDropped, GripPos, GripRotation, Grip (a CFrame), GripForward / GripUp / GripRight, Activate(), Deactivate(). Events Equipped(mouse), Unequipped, Activated, Deactivated. While held, tool.Parent is the character; otherwise it's in player.Backpack.

StartingTools

Tools every player gets when they spawn (game.StartingTools).

Teams

GetTeams(). Each Team has TeamColor, AutoAssignable and GetPlayers(). A SpawnLocation has Neutral and TeamColor.

Units and numbers

Distances are in units: one unit is the width of one stud on a brick.

Keyboard shortcuts

Stuck? Ask in the Forums.