C# / TypeScript FiveM Developer
Custom Systems • Existing Codebases • NUI • Backend • SQL • Bug Fixes
Hey!
I’m a FiveM developer focused mainly on custom systems, backend development, existing codebase maintenance and debugging.
I’m not looking to simply install and configure public scripts.
I prefer working on projects where something actually needs to be built, fixed, redesigned or cleaned up.
If your server already has a large codebase, unfinished systems, technical debt or bugs that keep coming back after temporary fixes, that’s exactly the kind of work I’m interested in.
What I Can Help With
Custom FiveM Systems
I can build or expand systems such as:
-
Inventory systems
-
Faction / organization systems
-
Dynamic permissions
-
Divisions / sub-units
-
Police / EMS systems
-
Dispatch systems
-
MDC / MDT systems
-
Injury / death systems
-
Character systems
-
Property / housing systems
-
Vehicle systems
-
Garages
-
Businesses
-
Admin systems
-
Reports / support systems
-
Duty systems
-
Radio integrations
-
Item interactions
-
UI-based systems
-
Logging / audit systems
And other server-specific mechanics depending on your requirements.
Existing Codebase Rescue
Already have a server but the codebase is becoming difficult to maintain?
I can work with existing resources instead of automatically suggesting a complete rewrite.
I can investigate:
-
Recurring bugs
-
Duplicate logic
-
Temporary patches
-
Dead / unused code
-
Broken resource dependencies
-
Client ↔ server synchronization issues
-
Incorrect state handling
-
Database inconsistencies
-
Permission problems
-
Event flow issues
-
Resource lifecycle problems
-
Performance problems
-
Systems that break after resource restart
-
Features that work locally but fail in production
-
Old systems that need refactoring
My approach is generally:
Find the root cause → understand related systems → fix the actual problem → test the surrounding flow.
Not:
Add another patch and hope it works.
Backend & Server-Side Development
A large part of my work is backend-focused.
I can work on:
-
Server-authoritative logic
-
Secure client/server events
-
Input validation
-
Permission validation
-
Player / character state
-
Database operations
-
Async flows
-
Resource lifecycle
-
Cross-resource communication
-
API integrations
-
Logging
-
Persistent systems
-
Server-side business logic
I especially care about avoiding situations where important actions are trusted directly from the client.
NUI Development
I can also work on modern FiveM NUI systems.
Experience includes:
-
TypeScript / JavaScript
-
React / Next.js-style frontend development
-
HTML / CSS
-
Responsive interfaces
-
NUI callbacks
-
Backend ↔ NUI synchronization
-
State management
-
UI debugging
-
Existing UI redesign / cleanup
I prefer clean and usable interfaces instead of oversized or overly game-like UI.
Database
I work with relational databases and persistent game systems.
Main experience:
-
MySQL
-
SQL schema design
-
Relationships
-
Migrations
-
Character-linked data
-
Vehicle data
-
Inventory data
-
Permissions
-
Persistent system state
-
Query debugging
-
Duplicate / inconsistent data investigation
Main Stack
FiveM
-
C# / .NET
-
TypeScript
-
JavaScript
Frontend
-
React
-
Next.js
-
HTML
-
CSS
Backend / Data
-
C#
-
PHP
-
MySQL
-
REST APIs
-
Webhooks
Development
-
Git
-
GitHub
-
Branch-based development
-
Code review
-
Refactoring
-
Debugging
My strongest FiveM work is primarily C# / TypeScript based.
If your project is heavily Lua-based, send me the details first so I can tell you honestly whether I’m the right person for the job.
Experience
I’ve been working on a large custom text-roleplay ecosystem containing interconnected systems rather than isolated standalone scripts.
Some of the areas I’ve worked on include:
-
Custom inventory
-
Character systems
-
Factions
-
Dynamic faction permissions
-
Divisions
-
Police / EMS gameplay
-
911 / dispatch
-
MDC
-
Injury and death lifecycle
-
Properties / housing
-
Vehicles
-
Garages
-
Businesses
-
Administrative tools
-
Reports
-
Radio systems
-
Clothing
-
UI / NUI
-
Web/UCP integrations
-
Database-backed persistent systems
This has given me a lot of experience working on situations where changing one system can affect several others.
That’s also why I’m comfortable taking over existing and complicated projects instead of only starting from an empty resource.
What I’m Particularly Interested In
I’m especially interested in projects like:
“Our developer left and the project is unfinished.”
“The system works, but the code has become impossible to maintain.”
“We keep fixing the same bug and it keeps returning.”
“We need a custom system instead of another public script.”
“The frontend works but the backend state doesn’t stay synchronized.”
“Our database / character / faction systems are connected and something is breaking between them.”
“We need someone who can understand the current architecture before changing it.”
Those are the projects where I can provide the most value.
How I Work
1 — Understand the problem
You explain:
-
What the system should do
-
What it currently does
-
Your framework / stack
-
The relevant resources
-
Any existing errors
2 — Inspect the existing implementation
For existing codebases, I first try to understand the current architecture.
I don’t immediately rewrite everything.
3 — Define scope
We agree on exactly what needs to be changed.
4 — Development
Work is preferably done using Git / branches so changes remain trackable.
5 — Testing
I test the feature itself as well as the systems directly connected to it.
6 — Delivery
Changes are delivered together with a clear explanation of what was changed.
Code Review / Technical Audit
If you’re not sure what’s wrong with your server yet, I can also review an existing resource or subsystem.
Things I can look for include:
Critical bugs
Security / trust issues
Architecture problems
Duplicate logic
Resource lifecycle problems
Technical debt
Performance issues
Maintainability problems
Optional improvements
This can be useful before paying for a large rewrite without knowing whether one is actually necessary.
Pricing
Both fixed-price and hourly work can be discussed depending on the project.
For small bugs or clearly defined tasks, I normally prefer a fixed quote.
For larger existing codebases or long-term development, hourly / milestone-based work usually makes more sense.
I prefer seeing the actual problem before giving a random price.
Long-Term Work
I’m also open to ongoing development relationships.
If you’re building a serious server and need someone for:
-
Regular development
-
New systems
-
Maintenance
-
Refactoring
-
Bug fixing
-
Technical decisions
-
Existing system improvements
we can discuss a longer-term arrangement.
Contact
Send me a Cfx private message with:
Framework / stack:
What you need:
Existing or new system:
Relevant resource(s):
Current problem:
Expected result:
Budget if already defined:
You don’t need to write an essay.
Something like this is enough:
“We have a custom C#/TypeScript RP server. Our faction duty and radio state become inconsistent after character switching. We need someone to inspect the existing resources and fix the lifecycle properly.”
From there, I can tell you whether it’s something I can take on.