About
A decade on Roblox. Five years building for it.
Puwido Enterprises is the Roblox development practice of Puwido — a developer who spent years as a player before opening Studio, and stayed long enough to start building the systems games depend on.
Background
Puwido was a Roblox player for years before writing a line of Luau. That time on the platform still shapes the work: knowing how players actually behave, and how exploiters actually cheat, is most of what makes a system hold up.
Today most of the work runs on the server — moderation tools, anti-exploit checks, admin panels and data saving — along with the menus and loading screens that sit on top of them. Alongside those systems, Puwido has contributed to games across simulators, tycoons, combat and military roleplay.
Outside Roblox, Puwido also writes C#, C++, Java and HTML.
Principles
How the work is held together.
- 01
The server decides.
Clients ask; the server checks. Every remote and every admin action is validated server-side, so exploiters can’t simply fire events.
- 02
Readable over clever.
Clear names and modular structure, so the next developer can pick the code up without guessing.
- 03
Configured, not rewritten.
Colours, text, timings, word lists and limits live in one config file or an in-game settings panel.
- 04
Built for every screen.
Interfaces are built for PC, mobile and console, and scale from a phone to an ultrawide monitor.
- 05
Nobody gets stuck.
Loading stages time out, failed saves retry, and systems are built to fail safely rather than lock players out.
Toolkit
Luau first. Not only Luau.
- LuauPrimary language — all Roblox work
- C#
- C++
- Java
- HTML
On Roblox, the work leans on the platform’s own tools wherever they exist — DataStores, the Ban API, text filtering and pathfinding — rather than reinventing them.
Have a project that needs to hold up?
Share the game, what it needs built and when you need it. Enquiries are answered on Discord.