Skip to content
Available for work

Roblox scripter and systems architect.

I build the code, and I plan the structure before the code.

01 — Services

Two services. Standalone or stacked.

01  /  BUILD

Systems & Scripting

Custom Luau systems built to production standards — server-authoritative, exploit-resistant, version-controlled.

Includes
  • Core gameplay systems (combat, inventory, economy, progression)
  • Networking & data persistence with ProfileStore-style session patterns
  • Codebase architecture using Knit, Matter, or custom frameworks
  • Hand-off documentation so your team can maintain it
02  /  PLAN

Game Structure & UX Planning

Before a single line of code, your game needs a blueprint. I produce the structural docs that prevent rewrites at month six — system diagrams, data schemas, UI/UX flows, and a clean module layout your team can build against.

Includes
  • Core architecture blueprint (modules, services, data flow)
  • UI/UX flow specs and screen-level breakdowns
  • Data schemas and persistence strategy

Standalone or combined. DM for scoping.

02 — Process

How an engagement runs.

  1. 01  /  SCOPE

    Discovery call.

    We pin down genre, core loop, scope ceiling, and what success looks like before any deliverable is quoted.

  2. 02  /  BLUEPRINT

    Architecture pass.

    Module map, data schemas, networking boundaries, and folder structure. Delivered as a doc you can hand to any dev.

  3. 03  /  BUILD

    Implementation.

    Strict-mode Luau, Knit/Matter where it fits, server-authoritative by default, version-controlled with Git.

  4. 04  /  HANDOFF

    Documentation and walkthrough.

    Inline docs, a README per system, and a recorded walkthrough so your team can maintain it without me.

03 — Stack

Tools I reach for, in order of how often.

Languages
  • Luau
  • Roblox-TS
Frameworks
  • Knit
  • Matter (ECS)
Data
  • ProfileStore
  • ProfileService
  • DataStore2
Tooling
  • Rojo
  • Wally
  • Git
  • Trove
Concepts
  • Anti-exploit
  • OOP
  • ECS architecture
  • Game architecture & system design
  • UI/UX flow design
04 — About

Short version.

I'm a Roblox developer focused on the systems layer — inventories, combat, economies, the infrastructure that makes a game feel solid. I care about clean architecture, server-authoritative design, and code the next dev can actually read.

I work in two modes. As a scripter, I build production-grade systems in strict-mode Luau under Knit, version-controlled with Git, with data persistence and exploit-resistance treated as defaults. As an architect, I help teams plan a game's structure before the build starts — a lot of Roblox projects fail not because the scripting is bad, but because no one designed the structure in the first place. Modules tangle, data schemas drift, UI flows get bolted on. The blueprint phase prevents that.

Currently open to commissions, consulting, and collaborations. Best way to reach me is Discord.

05 — Contact

DM for project quotes, consulting, and availability.

No public pricing. Send a brief, a deadline, and a budget range — I'll come back with a yes / no / scope.

Copied __6ds to clipboard