Built for paid Roblox development, not throwaway scripts.
Roblox Scripting & Luau Development
Roblox scripting for projects that need real technical help.
I build systems, fix broken code, clean up messy foundations, and support serious Roblox projects with paid Luau development.
Systems built properly
Messy code brought under control
Support for active projects
From fresh builds to cleanup on projects that already have problems.
One-off commissions, ongoing work, or focused technical support.
Client work stays private and handled properly.
Services
Clear scripting support for the work serious Roblox projects actually need.
The goal is not just to add more code. It is to make the project easier to build, easier to update, and less painful to manage.
Gameplay Systems
Feature systems that shape how the game actually plays.
- Combat, tools, progression, quests, and interactions
- Systems designed around the game, not copied into it
- Stronger foundations from the start
Backend & Data
Server-side work that keeps the project stable and easier to manage.
- Data saving, currencies, inventories, remotes, and permissions
- Cleaner structure behind the scenes
- Less fragile logic as the project grows
UI Programming
Interface scripting that makes the game feel sharper and easier to use.
- Menus, HUD logic, shops, prompts, and transitions
- Clearer player feedback and flow
- Smoother interface behaviour
Optimisation & Bug Fixing
Technical problem solving for projects that are slowing down or breaking down.
- Issue tracing, stability work, and performance cleanup
- Broken systems brought back under control
- Less time lost to recurring technical problems
Rewrites & Cleanup
Refactors and repair work for code that is already creating friction.
- Less technical debt in the way of future updates
- Cleaner structure where it matters most
- Better foundations going forward
Ongoing Project Support
Flexible support for teams that need more than a one-time script drop.
- One-off commissions or longer support
- Help inside existing projects and live workflows
- Extra scripting capacity when the project needs it
Bring Me In Before The Technical Mess Gets Worse
If your project needs stronger systems, cleaner structure, or rescue work, this is the point to reach out.
Projects
Public showcase work that demonstrates both isolated systems and full game builds.
Public showcase material is limited, so what appears here needs to show real scripting value. These examples cover both focused technical systems and a complete live Roblox progression game.
Featured Demo
NPC Pathfinding Script Demo
This is a basic pathfinding demo showing a hostile NPC navigating a maze to hunt the player. It is a simple showcase version compared to the fuller client builds I work on, where this kind of enemy logic can be expanded much further for real game use.
- Can be extended with ranged combat, melee behaviour, and smarter attack timing
- Can support audio cues, alert states, suspicion systems, and target memory
- Can be developed into patrol routes, group AI, cover logic, and open-world pursuit systems
Live Game
Zen Incremental
Zen Incremental is a Roblox progression game built around meditation, upgrades, rebirths, enlightenment, rewards, and long-term AFK progression. It was built as a full playable framework rather than a small isolated feature demo.
I handled the full progression backend and live-service scripting, including persistent player data, upgrade scaling, rebirth and enlightenment systems, reward pipelines, gamepass effects, tutorial flow, auto-collect systems, leaderboard syncing, admin tools, chat tags, global announcements, and soft shutdown rejoin handling.
- Full progression framework with server-authoritative persistent systems
- Rewards, boosts, codes, monetisation hooks, and long-session retention systems
- Live-game support features for stability, admin control, and player continuity
Why Hire Me
Even without a public portfolio, the reason to reach out should be obvious.
I reduce technical chaos
Good scripting is not about adding more code for the sake of it. It is about fewer problems, stronger structure, and less friction when the project grows.
I can step into messy projects
Existing codebases do not need to be in good shape first. Rescue work, rewrites, tracing problems, and cleanup are part of what I offer.
I build with future changes in mind
The point is not just to get something working today. It is to avoid turning future updates into a bigger technical mess.
I handle private work properly
I do not leak client systems or unpublished work to make a website look fuller. The lack of public proof is part of how I handle paid client work.
How I Work
A straightforward process built around clarity, scope, and delivery.
You message me with the task
Tell me what needs to be built, fixed, cleaned up, or reviewed.
I review the scope
I look at what the project actually needs and whether I am the right fit.
I build, fix, refactor, or optimise
The work is handled with the actual project in mind, not in isolation.
I test and refine
The goal is not rough code that “kind of works.” It needs to hold up.
I deliver and support where needed
One-off work is fine. Ongoing support is fine too. It depends on the scope.
Ready To Reach Out?
If the scope is clear enough to discuss, that is enough to start.
Best Fit Projects
The right fit matters. This site is meant for serious project work.
Best Fit
- Projects that need real scripting help, not random filler work
- Games with systems to build, fix, optimise, or clean up
- Teams that value stronger structure and better long-term maintainability
- Clients who can explain the problem, even if the brief is still rough
- One-off commissions or ongoing support with clear communication
Not A Fit
- Projects built around copied or stolen systems
- Very vague rush jobs with no usable scope
- Work where price is the only real priority
- Projects with no direction and no clear communication
- Teams that only want speed and do not care what that does to quality
Confidentiality
Private client work stays private.
Most paid work I do is covered by NDAs or private agreements. I do not post client systems, unpublished features, or internal code just to make a landing page look fuller.
That is not a missing proof section. It is part of how I handle paid client work.
FAQ
Short answers to the things clients usually want to know first.
What kinds of Roblox work do you take on?
Systems work, bug fixing, optimisation, UI scripting, backend logic, cleanup, rewrites, and ongoing support.
Do you work on existing projects?
Yes. A lot of the work I take on is inside existing projects that need fixes, cleanup, or stronger scripting support.
Can you fix broken or messy code?
Yes. Rescue work and cleanup are part of the service, especially when systems were rushed or built badly.
Do you do one-off jobs or long-term work?
Both. It depends on the scope, the project, and whether the working setup makes sense.
Why is your work private?
Because most paid work I do is under private agreements or NDAs, and I treat client work like client work.
Do I need to know exactly what I want before messaging?
No. A rough but clear explanation is enough to start the conversation.
Do you only work on full systems?
No. I also take on targeted fixes, cleanup, optimisation, and smaller scoped scripting tasks.
What should I include in my first message?
Game type, what needs doing, whether it is new or existing code, any deadline, and whether it is one-off or ongoing.
Contact
Message me on Discord with the basics and I’ll tell you if the project is a fit.
Discord is the main contact method. A short clear brief is enough. You do not need a perfect spec before reaching out.
Start Here
Main ContactDirect contact for commissions, fixes, systems work, and ongoing support.
Clear messages make it easier for me to tell you quickly whether the project is a fit.
