Gameplay, backend,
and tools.

I build Roblox features, backend systems, and tools for your workflow, then connect them to the project you already have.

Start with what you need.

It can be one feature, an integration into an existing project, or a new system. Each area links to a project where I built something similar.

From brief to implementation.

Before I write any code, we agree on what to build and how to check that it works. The handover follows that agreement.

Describe the feature

Send the goal, an example flow, the platform, and any existing code. For a bug, include the steps to reproduce it.

Agree on scope

We list the work, dependencies, priorities, timeline, and what counts as done, so nothing is left to assumption.

Build & check the flow

I build and integrate the feature, then test normal use plus cases like cancelling, bad input, or a disconnect.

Hand over with context

You get the source code, integration steps, configuration notes, test results, and any limits that remain.

Before we start.

A few answers about how I work and the areas I can help with.

Yes. I read through the existing code and how its parts depend on each other before adding or changing anything.
Send a brief first. Estimates depend on the feature, complexity, existing code, and integration needs. We agree on scope and timeline before work begins.
Yes, on the scripting side: UI controllers, input, feedback, and integrating animations. In Bentengan I designed the Match Found screen that appears when a match is ready, and reworked the basic attack animation (hit/M1). New art or animation made from scratch is agreed separately in the brief.
Yes. Most of my current work is on Roblox, but I also take on Unity projects, developer tools, AI/ML experiments, and security reviews.

Describe the feature.
Let’s work out the scope.

A goal, platform, example flow, and rough timeline are enough to start a conversation.

Send a brief