Roblox · Luau · 6 years
6+ years on Roblox. Backend, gameplay, networking. Anything you need as long as it doesn't break TOS. A lot of people on the dev forum just paste code and charge you for it. I write my own.
no modeling, building, animation, or sfx. bring your own
about
6 years writing Luau for Roblox. Lead programmer at KMAP Studios, technical degree in quality, studying robotics and advanced computing. I do custom character controllers, combat state machines, lag compensation, server replication, stuff most scripters can't.
Backend: game logic, secure datastores, inventory tracking. Gameplay: combat engines, movement, TD, whatever you need. I don't use ProfileService, Knit, DataStore2, or FastCast. Everything is written from scratch.
If you're tired of paying people who just copy from dev forums or AI, reach out.
combat
State machines, hitboxes, ability pipelines, server-validated
movement
Custom controllers, wall-running, vaulting, physics feel
networking
Client-server sync, lag comp, low bandwidth
backend
Secure datastores, inventory, data architecture
frontend
Client scripting, viewport rendering, input
architecture
Framework design, flat structure, stays clean as it grows
why me
Most scripters can follow a tutorial. Some can write a system from scratch. Very few actually understand both client and server. I do.
dependencies
0 third-party modules
No ProfileService, no Knit, no DataStore2, no FastCast. I wrote all my own systems, so I know how they work and why.
Client and server
Only knowing one side is a problem. They're connected, every choice on one affects the other. Server is authoritative, client is responsive. Replication connects them properly.
Built for real servers
100 players, exploiters sending weird data, designers changing things mid project. Validation and error handling from the start, not added at the end.
Code you can read
Flat, simple, no over the top stuff. Hand it to the next dev on your team and they'll understand it without me.
6 years of experience
I already know which replication patterns waste bandwidth, which data layouts cause bugs later, which quick fixes take weeks to undo. You're not paying me to learn on your project.
