📖 The Context: "Closed-Circuit Excellence"
The FiveM world is saturated with "copy-paste" servers. PakeTekos takes a completely different approach: 90% of the code is proprietary, developed specifically to ensure a unique experience and total control over performance.
Although the project is currently in the MVP (Minimum Viable Product) phase, every software block is designed for scalability. To support this massive development, I had to create my own production tools, from which some generic modules have been extracted to be shared with the community.
🛠️ The Ecosystem: Between Proprietary and Open Source
PakeTekos is not just a script; it's an ecosystem. While the core gameplay remains private, I chose to open up certain technical blocks that redefine the development workflow on FiveM:
- tk-ui (Open Source): My "Developer Experience" (DX) solution. This bridge allows the use of Nuxt/Vue.js for in-game interfaces with a modern workflow (
npm run dev), enabling UI coding without even launching the game. - The PakeTekos Core (Proprietary): A massive set of scripts managing the economy, entity persistence, and social interactions, representing the heart of the project's value.
- tk-engine (Open Source): An ECS (Entity Component System) engine in TypeScript. It serves as a base for creating ultra-high-performance mini-games (like tk-coppertheft) integrated directly into NUI interfaces.
- tk-phone (Premium Example): A demonstration of what my stack allows: a responsive, fluid, and modular smartphone, designed like a cutting-edge web application.
🎯 My Role: System Architect & Lead Developer
As the project's creator, I juggle between maintaining the private "Core" and evolving the public tools. My work focuses on transitioning from a modified QBCore base to a lighter 100% proprietary framework (C# / Lua).
1. Interface Development (NUI)
Thanks to tk-ui, I've been able to industrialize the creation of complex interfaces. This allows for offering a "zero latency" HUD and menus that respect the server's premium visual identity.
2. Persistent State Management
I use MariaDB to orchestrate a city where nothing is lost. Every vehicle, every item, and every character history is saved with a database logic optimized for real-time.
🧠 Under the Hood: Architecture & Technical Challenges
The biggest challenge in a multiplayer open world is simulating an "infinite" city with limited resources.
⚙️ Optimization through "Client-Side Ownership"
To handle resource-heavy systems like permanent vehicles without crushing the server CPU, I implemented intelligent delegation logic via OneSync:
- Culling & Virtualization: Vehicles are only physically instantiated when a player enters a 200-unit perimeter.
- Calculation Delegation: The server dynamically assigns entity "ownership" to the nearest client. This client handles physical calculations and synchronizes state changes to the DB via the server, thus optimizing global bandwidth.
- Resilience: This model allows for hundreds of "persistent" vehicles on the map while maintaining constant fluidity for players.
🔭 The Vision and What's Next
PakeTekos is my personal laboratory. The next steps include:
- Full migration to a "from scratch" framework to eliminate any third-party dependencies.
- Integration of NPCForge to bring the city to life with NPCs aware of their environment.
- Enriching the tk- suite to continue professionalizing the tools available to other developers.
Note: While the PakeTekos universe is strictly private, my development tools and game engines (tk-engine, tk-ui) reflect my technical expertise and can be viewed on my GitHub.