Source-level control
A codebase we can inspect and improve lets us investigate client problems at their source instead of only working around them.
Building a future we can maintain
The 64-bit RaiderZ game client with DirectX 11, built to give RaiderZ Global a technical foundation we can understand, improve and maintain for the years ahead.
Where this work begins
The current live client originated from the North American release and has served the community well. Its source code is not available to our team, however, which limits structural fixes and makes deep client-side investigation impossible.
The RaiderZ Global server and Client 2.0 share the same development lineage, giving the team source-level access on both sides of the connection for the first time.
More than a visual upgrade
Client 2.0 is now the official RaiderZ client. Its modern foundation lets us continue improving compatibility, stability and gameplay over time.
A codebase we can inspect and improve lets us investigate client problems at their source instead of only working around them.
A native x64 architecture removes an important memory constraint, while DirectX 11 gives us a better base for current Windows versions, drivers and hardware.
A maintainable client makes careful fixes, diagnostics and future improvements possible without replacing the game players love.
Official client
Client 2.0 is the only RaiderZ client offered for download and connects to the live game world.
In development
The client continues to improve while remaining playable on the live server. Its rendering, stability and compatibility evolve with each update.
The launcher installs Client 2.0, which connects to the RaiderZ Global live server with your account.
Progress without hiding the rough edges
Rebuilding from an earlier source base means some behaviour already correct in the live client must be identified and restored. A temporary regression is evidence to investigate, not a feature we intend to keep.
Some UI elements may be misplaced, incomplete or behave differently while systems are restored.
Skills, effects or interactions may reveal differences that need reproduction and correction.
FPS, stuttering and loading can vary by hardware until bottlenecks are measured and addressed.
Evidence before release
Different PCs reveal different problems. Structured testing helps us separate hardware-specific issues from general client regressions.
Applicants record how RaiderZ performs on their PC before installing a test build.
Testing waves include different processors, graphics cards, Windows versions and player profiles.
Testers repeat the same scenarios with comparable settings across Client 2.0 builds.
Clear reproduction steps, screenshots, video and diagnostics turn discoveries into actionable work.