// available for commission

Backend systems
for your game.

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

  • GermanNative
  • EnglishFluent
  • RussianText only

Comfortable in voice chat — I'd rather talk through a complex system than send 40 messages.

// systems

Real systems, rebuilt from scratch
so you can read the work first.

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.

systems/gun-system View source

Gun System

  • Server-side hit registration on rewound positions
  • Raycasts against oriented bounding boxes
  • Ammo authority, spring recoil
  • Unreliable remotes for cosmetic effects
systems/player-data View source

Player Data

  • Session-locked DataStore access
  • Schema migrations, retries with jittered backoff
  • Safe shutdown handling
  • In-memory Studio fallback backend
systems/rng-pet-system View source

RNG Pet System

  • Weighted rolling with cached pools
  • Luck curve that only touches rare items
  • Server-authoritative results
  • Token-bucket rate limiting

Need something else?

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 directly
// approach

Standards most Roblox
scripters skip.

--!strict

Strict Luau everywhere

Every file starts with --!strict. Public types live in a dedicated Types module next to the code that uses them.

edges

Side effects at the edges

Remotes, DataStores, and Players stay in the outer layer. Core logic takes plain values and returns plain values — which is what makes it testable.

freeze()

Config in one frozen table

Every timing constant and weight sits in one place per system, with table.freeze on top so nothing rewrites it at runtime.

0 trust

Nothing from the client is trusted

A client request carries intent, never a result. Every outcome is computed and verified server-side.

docs

Honest limits, documented

Every system's README states what it doesn't do. A showcase that claims to handle everything is one nobody can review.

CI-clean

Checked before it ships

stylua, selene, and strict-mode luau-lsp analysis run clean across the repo — the same bar client work is held to.

// process

Simple, transparent,
no surprises.

  1. 01

    Tell me what you need

    Open a ticket in my Discord server or DM me. Describe the system, even vaguely. We'll figure out the details together.

  2. 02

    We agree on scope & price

    No hourly surprise invoices. We settle on a clear scope and a fixed price in Robux before I write a single line.

  3. 03

    I build it. You review it.

    I deliver with documentation. If something isn't right, we fix it. I don't disappear after sending the script.

// contact

Let's talk
about your project.

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.