FiveM-Script-Developer · Community Founder & Manager of the Multigaming Community Nebelbank.net since 1997 · Creative Streamer & Gaming Pioneer since the C64 / Amiga 500 era
[WIP] Nebelbank.net – Legacy RP – Back to the Roots
Founder and Manager of the Multigaming Community Nebelbank.net — since 1997.
I have been building, breaking and rebuilding systems since the C64 / Amiga 500 era. Today my work sits at the intersection of three disciplines that turn out to reinforce each other remarkably well:
| Domain | What I actually do |
|---|---|
| FiveM · QB-Core | Server-authoritative resources, framework-level integrations, OneSync-safe state handling, performance budgets that survive a full server. |
| IT Automation | Deployment pipelines, scripted server operations, monitoring and self-healing infrastructure — removing every task that repeats. |
| Applied AI | LLM-assisted development workflows, agent tooling and automation that produces reviewable, production-ready output — not demos. |
Note
Current project — Nebelbank.net · Legacy RP · Back to the Roots (WIP)
A roleplay server built on the principle that stability and fair play beat feature bloat.
Every resource I ship is measured against the same four gates. This is the flow a script goes through before it ever reaches a live server:
flowchart LR
A["💡 Concept"] --> B["🏗️ Server-Authoritative<br/>Design"]
B --> C["🔒 Trust Boundary<br/>Review"]
C --> D["⚡ Performance<br/>Budget"]
D --> E["🤖 Automated<br/>Deployment"]
E --> F["✅ Production"]
C -.->|"client input<br/>never trusted"| B
D -.->|"over budget"| B
classDef node fill:#0ea5e9,stroke:#0369a1,stroke-width:2px,color:#ffffff;
classDef done fill:#16a34a,stroke:#15803d,stroke-width:2px,color:#ffffff;
class A,B,C,D,E node;
class F done;
What each gate means in practice — click to expand
Server-Authoritative Design — the client renders, the server decides. Money, inventory, jobs and state transitions are validated server-side, always. No exceptions for convenience.
Trust Boundary Review — every RegisterNetEvent is treated as a public, hostile API. Payloads are
type-checked, rate-limited and bound to the caller's actual source. Events that mutate state are never
callable without validation.
Performance Budget — resources are profiled under load, not on an empty server. Threads run at the
lowest viable tick rate, loops exit early, and Citizen.Wait(0) is justified or removed.
Automated Deployment — no manual file copying, no "it works on my server". Reproducible builds, scripted rollouts, verifiable rollbacks.
|
Core Development |
Data & Infrastructure |
Tooling & Workflow |
#FiveM · #QBCore · #Lua · #Roleplay ·
#ITAutomation · #AI · #OpenSource · #Nebelbank
