LuxRP - FiveM Roleplay Server

A comprehensive FiveM roleplay gaming server that I built and maintained from 2020 to 2022. This project demonstrates my ability to manage build a project from scratch, maintain complex infrastructure, handle community management, and develop custom solutions.

Project Overview

LuxRP is a unique roleplay community server built on the FiveM platform. As a core we used ESX and migrated later on to QBCore. I was in charge of hosting the server and maintaining it. This included the game server, the website and the discord community (more than 1000 members). Over the years I added more and more features to the server.

Technical Implementation

Infrastructure

• Server Management: Windows and Linux-based server configuration and optimization managed via txAdmin.
• Database: MySQL database with for player data, economy, and logging managed via phpMyAdmin
• Performance Optimization: Resource monitoring and load balancing. Modified the assets to be more optimized.
• Backup Systems: Automated daily backups
• Linked Servers: Linked servers for whitelisting and main gameplay (with DB)
• VPN: VPN for remote access to the server with accounts for each developer

Custom Development

• Script Development: Lua-based custom scripts for unique gameplay features
• Custom Game Launcher: Custom FiveM launcher using a forked project

• Modified InGame Phone: Customized the phone to be fit better into the server.

• Converted ESX to QBCore: Converted assets to work with QBCore
• Custom storefront: Post Luxembourg based storefront for phone purchase
• Website: Built on top of MicroWeber View on the Wayback Machine

• Custom Loading Screen: Custom loading screen with server information and rotating images

Other Features

• Whitelist Management: Whitelist system with discord role-based permissions (Interlinking system with discord bot)
• Discord Integration: Real-time chat and notification systems

• Analytics Dashboard: Player statistics and server performance metrics
• Teamspeak Integration: Teamspeak server for voice communication via Salty Chat

Technologies Used

• Backend: Windows, Linux, MySQL, Lua, PHP, phpMyAdmin
• Frontend: HTML5, CSS3, JavaScript
• Infrastructure: MicroWeber, Nginx, Cloud (DigitalOcean)
• Monitoring: Discord logging and txAdmin analytics system
• Communication: Discord API, Webhooks

This project showcases my ability to manage complex technical infrastructure while maintaining a focus on user experience and community engagement.

Fun fact: The fritz.box cannot handle the load of 64 players ;)

Example of planning features

Ingame screenshot of player list

Reskin of the ATM UI

Patch List Creator

My motivation

As a live sound technician, I found that it was time consuming and difficult to create patch lists for clients without technical rider. This system allows me to send an artist a link, which they can use to add the equipment they are bringing or need, and the connections they need. Using this system, I can download the patch list as a PDF, which I can then print and give to the technician. It also serves as a way of keeping track of certain events.

The system

The frontpage

The frontpage is a simple page that displays information about the system and gives a quick explanation of what it does.

The login page

Using the login page, admins can log in to the system.

The admin navigation page

This page allows admins to navigate to different pages.

List of all events

When clicking on the list of all events, you will be taken to a page that shows all events. You can click on an event to view it.

Example of an event in the admin view

When viewing an event, you can see all the equipment that is needed and the connections that are needed. This is information added by the artist. You can also download the patch list as a PDF.

Example of an exported PDF

Here is an example of an exported PDF. This is a list that was used for an actual production.

The manage events page

This page allows admins to manage events. You can add new events and edit existing events.

Editing an event on the manage events page

This page allows admins to edit an event.

The manage bands/artists page

This page allows admins to manage bands/artists. You can add new bands/artists and edit existing bands/artists.

The manage links page

This page allows admins to manage links. You can add new links and remove existing links. It creates a link that allows the editing of a specific patchlist. This link can be sent to the artist.

The create patch page

This page allows artists to create a new patchlist. The artist can then add the equipment they are bringing or need, and the connections they need. Once the artist has added the equipment and connections, the artist/admin can download the patch list as a PDF.

PIF - Plantimeter System

The presentation:

The documentation:

Overview

Gives an overview of the logs

Configuration

Shows the changes in the configuration of the server startup command over time

Error Analysis

Shows the types of errors in the logs

Plugin Information

Shows the plugins that are installed on the server, which versions and their load times

Yona-RS

The presentation:

The documentation:

Radioactive Rust - LU PvE/PvP Server Project

Motivation

I want to create a casual Rust Server that offers PvP with some PvE. It needs reliable uptime as it is one of the crucial aspects determining a high quality server. To guarantee the uptime I will use comprehensive monitoring and scalable technologies.

I always found that Rust is a game that is hard to get into. Rust started offering multiple new game modes (difficulties), but they still change the game mechanics too much. I want to run a server that allows every skill level to have fun. I don’t want to strip the PvP elements completely as I find it is a necessary part of the Rust experience. It should encourage players to work together towards a goal. There will be a storyline building the servers unique feel.

It should be a modded server that gets wiped monthly, allowing players to get quality of life improvements and have time to build.

I will look into Ainsible, Terraform and Kubernetes to make the project scaleable. The server should allow selective EAC to allow linux clients on a trust basis. A player can ask for trust, once they break it they will never get it back. This data should be stored in a database.

What is RUST? (Definition)

Rust is a multiplayer survival game developed by Facepunch Studios where you spawn on a harsh island with nothing but a rock and torch. The goal is to survive by gathering resources, crafting tools and weapons, building shelters, and defending against wildlife, environmental hazards, and other players who can kill you and steal your loot. Wikipedia

The game features base building, raiding other players’ bases, and systems for electricity, farming, and various transportation options. Servers operate on a “Wipe” cycle that resets player progress periodically, with a mandatory monthly wipe on the first Thursday of each month that forces everyone to start from scratch. Facepunch

What differentiates this server from others?

1. Focus on uptime
2. Comprehensive monitoring and fast response (Automation)
3. Unique storyline (continuation of the games storyline)
4. Linux compatibility
5. Proper Documentation
6. Custom maps/plugins
7. Good implementation of plugins and continuous balancing
8. Server fun even when empty

The 3 essential parts

• Game Server (Rust)
• Information Portal (Website)
• Community (Discord)

Rough planning outline

1. Run a stable modded Rust server and tweak to liking
2. Implement some PvE elements
3. Get feedback on what people are searching for
4. Design elements (logo, banner, colors) and create branding
5. Create Website
6. Create/Reuse Discord Server
7. Expand community and get more feedback
8. Add lore and more PvE elements
9. Make the project more scaleable
10. Advertise

Infrastructure

Test:

• Hardware: Ryzen 9 7950X, 128GB RAM (Proxmox VMs), NVMe + HDD storage
• Hosting: Home Linux VPS with Dynamic IP for public access
• Networking: Port forwards
• Management: Pterodactyl Panel (pre-installed)
• Cloud VPS for RUST+ pass trough, static IP

Production:

• Hardware: Variable Kubernetes scaling
• Hosting: Cloud VPS with Static IP for public access
• Networking: UFW Firewall
• Management: To be seen

Event:

• Hardware: Normal/Variable Kubernetes scaling
• Hosting: Cloud VPS with Static IP for public access
• Networking: UFW Firewall
• Management: To be seen

Tools/Technologies getting used

• MS-Planner
• Open Book Stack
• Carbon (Rust)
• Steam CMD
• RCON
• ProxMox
• Prometheus
• Pterodacytl
• Docker + Kubernetes
• Grafana
• Terraform
• Ainsible
• CDN
• Hetzner (and other clouds)
• CMS