Gameplay systems
Combat, abilities, inventories, progression, quests, NPCs, vehicles, and moment-to-moment game feel.
- Client prediction
- State machines
- Modular architecture
Available for selected projects
I build responsive gameplay, clean interfaces, secure data systems, developer tools, and the services that connect everything together.
-- shipping reliable experiences
local Developer = {
discipline = "full-stack",
platform = "Roblox",
priorities = {
"feel", "scale", "security"
}
}
function Developer:Ship(idea)
return prototype(idea)
:test()
:polish()
:launch()
end
01 · Selected work
A selection of gameplay, interface, infrastructure, and tooling work. Replace these samples with your own projects in script.js.
02 · Capabilities
I can take a feature from an early idea to a stable system that feels good for players and remains easy to maintain.
Combat, abilities, inventories, progression, quests, NPCs, vehicles, and moment-to-moment game feel.
Responsive Roblox UI with clear hierarchy, satisfying motion, controller support, and mobile-first layouts.
Secure remote boundaries, persistent player data, matchmaking, analytics, moderation, and resilient services.
Dashboards, APIs, Discord integrations, internal tools, build pipelines, and web experiences around your game.
03 · About
I build systems that feel simple to players, even when the work behind them isn't.
I'm Blobby. I build Roblox games from the player-facing buttons down to the server code saving their inventory.
I care about responsiveness, readable code, exploit-resistant systems, and not leaving the next developer with a mysterious pile of scripts.
Download résumé ↗Core stack
04 · Process
A straightforward process for testing ideas early, building carefully, and getting useful work into players' hands.
Clarify the player outcome, technical constraints, risks, and smallest valuable release.
Prove the feel and the architecture early with something playable, measurable, and easy to change.
Build the complete feature with secure networking, responsive UI, instrumentation, and documentation.
Profile, playtest, tune, handle edge cases, and launch with a clear path for iteration.
Have something in mind?
Tell me what you're making, what stage it is at, and where you need help.