Skip to content
vdit.nrw

/ Labs

Open source, gaming and experiments

Projects outside client work: server systems for game communities, plugins and analysis tooling. This is where we test techniques we later use in production.

/ Labs projects

  • 01

    Wizard-Life RP

    Multiplayer roleplay server modification for Hogwarts Legacy — custom server-side systems, tooling and community infrastructure operated in production.

    Gaming / Server systemswizard-life.de ↗
  • 02

    CS2 server plugins

    Open-source server-side plugins for Counter-Strike 2, e.g. finestats-lite: per-player statistics and ranking backed by a local SQLite database — no external backend required.

    Gaming / Plugins (C#)GitHub ↗

/ L1 · Gaming software

Software around games

Subsystem: gaming // ecosystem engineering

Games are complex software ecosystems.

We develop modifications, backend services, community infrastructure and tools around those ecosystems — with the same engineering standards we apply to production software anywhere else.

That means reliable server-side behavior, clean interfaces and tooling that operators can actually maintain.

  • 01Game modifications
  • 02Dedicated server tooling
  • 03Server-side systems
  • 04Launchers & APIs
  • 05Community systems
  • 06Developer tools

/ L2 · Analysis & interoperability

When the documentation stops

Some systems do not provide the interfaces, documentation or tooling required to integrate with them.

In those environments, we analyze software behavior, protocols, file formats and system boundaries to understand how components interact. The goal is always the same: make the system work together — cleanly, predictably and without guesswork.

  • 01Protocol analysis
  • 02Undocumented API analysis
  • 03Legacy software integration
  • 04Data format analysis
  • 05Interoperability engineering
  • 06Software behavior analysis
  • 07Reverse engineering where legally permitted

[LEGAL] All analysis and reverse engineering work is performed within applicable legal and contractual boundaries.

Protocol view — illustrative frame
00000000  7e 42 44 47 01 04 00 21  53 54 41 54 55 53 3d 4f   ~BDG...!STATUS=O
00000010  4b 2c 4e 4f 44 45 53 3d  30 37 2c 43 52 43 3d 38   K,NODES=07,CRC=8
00000020  38 34 32 7e                                        842~
Structure reconstructed from behavior — no live traffic
← Back to the homepage