Gun System
- Server-side hit registration on rewound positions
- Raycasts against oriented bounding boxes
- Ammo authority, spring recoil
- Unreliable remotes for cosmetic effects
// available for commission
Strict-mode Luau. Server-authoritative logic. Every system below is open-sourced, so you can read the code before you pay for it — not just take my word for it.
I communicate in
Comfortable in voice chat — I'd rather talk through a complex system than send 40 messages.
Client work stays with the client — nothing here was sold to anyone. These are rebuilt from zero with the same architecture and the same standards, small enough to read in ten minutes.
If you're not sure I can do it, ask. I'll tell you honestly if it's outside what I do well, and point you to someone who can if it is.
Ask me directlyEvery file starts with --!strict. Public types live in a dedicated Types module next to the code that uses them.
Remotes, DataStores, and Players stay in the outer layer. Core logic takes plain values and returns plain values — which is what makes it testable.
Every timing constant and weight sits in one place per system, with table.freeze on top so nothing rewrites it at runtime.
A client request carries intent, never a result. Every outcome is computed and verified server-side.
Every system's README states what it doesn't do. A showcase that claims to handle everything is one nobody can review.
stylua, selene, and strict-mode luau-lsp analysis run clean across the repo — the same bar client work is held to.
Open a ticket in my Discord server or DM me. Describe the system, even vaguely. We'll figure out the details together.
No hourly surprise invoices. We settle on a clear scope and a fixed price in Robux before I write a single line.
I deliver with documentation. If something isn't right, we fix it. I don't disappear after sending the script.
I respond to every serious inquiry. The easiest way to reach me is through my Discord server — open a ticket and I'll get back to you as soon as I'm available.