I'm Lukas — a full-stack Roblox scripter. I build games the way software gets built: config-driven, split into services, server-authoritative by default. Right now I'm shipping Untitled Backrooms, a horror round game running on 16+ of my own services. It's age-restricted for the moment — once I've raised the Robux to promote it properly, it opens up to everyone and goes out across group pages. While I build it, I'm taking commissions.
-- one config drives the whole game, no magic numbers
local Config = {}
Config.Version = "BETA 0.1"
Config.IsBeta = true
Config.ShowBetaBadge = true
Config.Debug = false
Config.Round = {
IntermissionTime = 20,
VotingTime = 15,
LoadingTime = 3,
CountdownTime = 5,
RoundTime = 180,
EndScreenTime = 10,
MinPlayersToStart = 1,
RespawnInLobby = true,
}
Config.Movement = {
WalkSpeed = 20,
SprintSpeed = 30,
SprintSpeedGamepass = 40,
MaxStamina = 100,
MaxStaminaGamepass = 165,
StaminaDrainPerSec = 18,
StaminaRegenPerSec = 13,
RegenDelay = 1,
MinStaminaToSprint = 5,
JumpPower = 40,
SlideSpeed = 40,
}About
@lukas929222
"I'd rather spend the first day on structure than spend the last week untangling it."
I've been writing Luau for over three years — long enough to have built the same system badly, then properly. What I do now is treat a Roblox game like software: one config module holds every tunable value, each system lives in its own service with a clear boundary, and the server is the only thing that decides what's true.
That matters to whoever hires me for a plain reason: you can change things without me. Want the round two minutes longer, stamina drain slower, the monster less aggressive? That's a number in a config file, not a call to your scripter. And when someone else picks the codebase up later, they can read it.
I work solo, I quote per task, and I tell you up front when something isn't worth building.
Services
Every job is quoted per task after we've scoped it — no fixed price list, because no two systems are the same size.
You have a game and need one part of it built properly.
Quoted per task · paid on completion
You have the idea, the map and the models — I write everything that makes it a game.
Quoted per milestone · split into tasks
Something already exists and it's slow, broken or exploitable.
Quoted per task · after a free look
Currently building
A horror round game. Started September 1st, targeting release October 28th. Every line of it is mine.
Round-based horror: intermission, map voting, a timed run, and an end screen — with a monster hunting players through it. Built as a service architecture rather than a pile of scripts, so each system owns its own state and talks over a single networking layer. Every tunable value lives in one config module, which means a balance change is a one-line edit instead of a hunt through the codebase.
Portfolio
Standalone systems, all written from scratch. Press play on any of them to watch it run.
Solo · drivetrain & UI
Full driving sim: automatic and manual gearboxes, drive modes, nitro, launch control, traction control, ABS and ESC, live suspension readout, headlights and indicators — with a dashboard reading real drivetrain state, not fake numbers.
Solo · simulation
Autonomous traffic on a road network: cars follow lanes, obey signals, queue at intersections and keep distance from the vehicle ahead — a living city that runs without a player touching it.
Solo · weapons framework
A full first-person weapons framework: nine weapons from rifles to a sniper, pistol, grenade launcher and RPG, each with its own fire mode, recoil and reload. Aiming down sights, a live ammo and reserve counter, camera shake and a slot bar — and every shot resolved by a server damage service behind a rate limiter, so the client can't invent hits.
Solo · in-game device & apps
A working phone inside Roblox, not a picture of one: home screen with live widgets, an app grid, a dock, and real apps behind them — weather with hourly and ten-day forecasts, camera, clock, notes and a calculator. Each app is its own module, so a new one is a file rather than a rewrite.
Solo · combat framework
Combo-based melee with hit detection, knockback, blocking and ability cooldowns, wired to a HUD showing the combo counter and cooldown timers. Built against training dummies so the numbers were tunable before any art existed.
Support the game
Building it costs time. Getting anyone to see it costs Robux — ads, sponsored slots, and clearing the game for everyone instead of 16+ only.
Every Robux goes into the game, not into me. If you want to help, the fastest way is buying a gamepass in-game — or just playing it and telling someone.
Lift the 16+ restriction so the game reaches the full Roblox audience, not a slice of it.
The only reliable way a new game gets its first thousand players.
Placement on established pages that already have the audience I don't.
Commissioned models, sound and UI art, so the game looks as finished as it plays.
Capabilities
Stack
| Tool | Used for | Level |
|---|---|---|
| Luau | Everything in-engine, server and client | 3+ years |
| Service architecture | Splitting a game into systems that don't tangle | Daily |
| DataStores | Saves, inventories, currency, leaderboards | Strong |
| RemoteEvents / networking | One layer, server-authoritative by default | Strong |
| Pathfinding & AI | Monsters, NPCs, autonomous traffic | Strong |
| UI / TweenService | HUDs, dashboards, shops, menus | Strong |
| Physics & constraints | Vehicles, suspension, handling | Working |
| Monetization APIs | Gamepasses, developer products | Working |
Process
Each step gates the next, so you always know where the work stands.
You tell me the system and what "done" looks like. I come back with what I'd build, how long it takes, and the price for that task.
I write the config and the service boundaries first. You see the shape before any gameplay code exists.
Regular updates with test footage. You can play it in a test place while it's being built.
Commented code, a config you can tune yourself, and a walkthrough. You pay once the task is done and working.
Contact
Best first message: what the system has to do, roughly how big your game is, and your deadline. I reply within 24 hours and I'll tell you straight whether I'm the right person for it.
Untitled Backrooms currently requires Roblox 16+ age verification to play.