KNALLLKOPP Open for commissions
IndexN° 001 Edition2026 — Vol. II
StackLuau · JS · Workers

Knalllkopp

An independent developer who builds the whole thing.

* Three L’s. On purpose.

Roblox games and the systems inside them, web tools, websites and the APIs between them — scoped and built by one person, start to finish, with obsessive attention to feel, performance and craft.

GamesToolsWebsitesAPIs

§ 02 — Work

Selected work.

02 case studies
  1. № 01
    Platform
    Roblox
    Kind
    Game
    Status
    In development

    WC:RP

    Washington City Roleplay. A city roleplay game in the ERLC mould, built by one person — systems, interface and networking.

    ProblemCity roleplay is a genre where the game supplies the systems and the players supply everything else. A full server improvising at once will find every seam you left. ApproachOne developer across the whole stack: the gameplay systems, every screen of the interface, and the networking that keeps a server’s worth of players agreeing on what just happened. ResultIn active development and not public yet — so no link here, and no numbers until there are real ones.

    • Luau
    • Systems
    • UI
    • Networking
    • Solo build
  2. № 02
    Platform
    Roblox
    Kind
    Asset
    Status
    Complete

    Phone System

    A complete in-game phone for Roblox: seventeen apps, one command bar, nobody’s logo on it.

    ProblemA phone inside a game is a product inside someone else’s product. It has to feel native to their world, do enough to be worth opening, and wear their brand, not mine. ApproachSeventeen apps behind a command-bar interface. Built unbranded from the first line, so it drops into any game under that game’s name. ResultFinished and packaged as a sellable asset — a whole product, not a demo.

    • Luau
    • UI
    • Command bar
    • 17 apps
    • Unbranded
§ 03 — Practice

What I build.

07 disciplines
01 / Architecture

Systems & frameworks

Production-grade architecture in Luau — modular service patterns, signal-driven communication, dependency injection. The difference between code that ships and code that scales.

  • Knit
  • Matter
  • Fusion
  • OOP
  • ECS
02 / Interface

UI & UX

Native-feeling HUDs, menus, inventories, phone apps. Scale-aware layouts and microinteractions that breathe.

  • UIScale
  • Tween
  • Mobile-ready
03 / Networking

Multiplayer & replication

Server-authoritative gameplay, lag-compensated combat, robust anti-exploit. Replication that stays smooth when the server fills up and somebody starts poking at your remotes.

  • RemoteEvents
  • Sanity Checks
  • Rate Limits
  • Lag Comp
04 / Persistence

Data & state

Bulletproof DataStore wrappers, session locking, migration pipelines, leaderboard backends, MemoryStore for cross-server state. The plumbing your players never notice — until it breaks.

  • DataStore2
  • ProfileService
  • MemoryStore
  • HTTP
05 / Procedural

Generation & AI

Procedural worlds, NPC behaviour trees, pathfinding, dynamic encounters and content systems.

  • PathfindingService
  • BT
  • Noise
06 / Web & APIs

Websites, web apps & APIs

Static sites and web apps on Cloudflare Pages, with Workers behind them when the browser needs a server: custom REST APIs, proxies for APIs that won’t talk to browsers, PWAs that install like apps. Vanilla JavaScript, no framework unless one earns its weight — this site included.

  • Cloudflare Pages
  • Workers
  • REST APIs
  • Proxies
  • PWA
  • Vanilla JS
07 / End to end

The whole thing, one person

A Roblox game from first system to launch. A web tool from the frontend to the API it calls. An app from first screen to working build. Architecture, code, interface, polish and whatever the launch turns up — for solo creators with a sharp idea, or teams that need a missing piece built properly.

  • Games
  • Tools
  • Websites
  • APIs
  • Architecture
  • Polish
  • Launch
§ 04 — Method

How it runs.

04 stages

  1. Brief & scope

    You send what you’re building — a game system, a tool, a site, an API. We talk through scope, timeline and edge cases. I quote a flat fee.

    ~ 48 hours

  2. Architect & build

    I scaffold the architecture, build the systems and write the code you’d want to maintain. Daily updates if you want them.

    1 — 6 weeks

  3. Polish & ship

    Performance pass, mobile pass, edge cases, the microinteractions that make it feel real. Hand-off when you sign off.

    3 — 5 days

  4. Support & iterate

    Two weeks of post-launch support included. Bug fixes, balancing, extensions — whatever the launch surfaces.

    14 days included

§ 05 — Profile

About me.

Solo · Independent
Solo practice
Roblox · Web · iOS
Luau · JavaScript

Open for commissions

Knalllkopp is one developer building the whole thing: Roblox games and the systems inside them, web tools and the APIs they call, and the occasional app for the phone in your pocket.

The work focuses on systems that feel right — code, mechanics and interfaces where the gap between adequate and excellent is measured in milliseconds, easing curves and thoughtful defaults. That holds in Roblox, in a browser tab, and at the edge.

No agency, no hand-offs between departments. The person who scopes it is the person who builds it.

§ 06 — Commission

Got a project
in mind?

Send a brief on Discord — game, tool, site or API, the timeline, and whatever reference you have. I respond within 48 hours.

DM on Discord

Discord · @knalllkopp