Systems that hold players, not decorate pages

Roblox Systems & Gameplay Engineer — 4 years of Luau

Four years inside Roblox Studio, on the part players don't see but feel: saves that don't vanish, hits that count when they land, movement with weight. Code another dev can continue without rewriting.

Watch the systems run Ask for a fixed quote See how they're built

Engine: Roblox Studio / Luau strict
Performance readout: Frame time profiled in ms
Quote: Fixed, per milestone, in writing

01Where it already ran

Each genre charges one thing. I deliver that thing.

Gameplay loop, server logic and replication, tuned to what each genre punishes when done badly.

02Under the hood

Three systems I repeat on every serious project

Modular, readable Luau, profiled with MicroProfiler — frame time, scheduler, physics and replication kept flat. Each file says what breaks when done badly.

03Proof, not promise

Recorded running. Hit play and check.

Systems recorded running in-engine. Nothing here is a mockup: it's the game on, with people inside.

04Direct contact

Send the scope. I send back a fixed price.

Discord chat, written scope, price per milestone. No hidden fees, no spaghetti code.

01

Discord

eo_bm
02

Roblox

Profile & DevForum

Profile DevForum
03

YouTube

@seu-canal

Channel

Every job runs the same

The same discipline on every job, so systems stay cheap and consistent to run:

Typed Luau and modular state machines
Code written to be read by whoever comes next
MicroProfiler + Script Profiler: script cost in ms, no spikes, no leaks
Milestones with fixed prices, agreed in writing