Raiderz Help

Troubleshooting for RaiderZ server owners: connection errors, database problems, client crashes and configuration mistakes.

Most problems posted here come down to a handful of causes: the client pointing at the wrong address, a database the server cannot reach, a missing runtime library, or a port that was never opened. Search before posting - the same RaiderZ errors come up often and usually already have an answer.

RaiderZ releases cover the Maiet SDK source, the 2013 Bola server files with the RaiderZ Brasil client, and a 2016 package of NA client, Jan 2016 build and Visual Studio 2015 source needing no API server. The source produced SoulHunterZ; Bolas server files carry Project Everlasting content. Servers are Windows executables (MasterServer, LoginServer, AppServer, GameServer) set in server.ini over an ODBC DSN on MSSQL 2008 R2; 2008 Express cannot restore R2 backups. The 2013 files need telnet to a Linux API server, later rebuilt on XAMPP; runtest.bat carries the server IP. MRF Unpacker, z3ResEx and rzfswizard open .mrf and fileindex.msf, with .elu model source and a system XML editor.

Common questions

Why will my RaiderZ client not connect to the server?

Nearly always the address the client is pointed at. On many builds the server address sits inside a packed client file rather than a plain text config, so it has to be edited there. Check as well that the server is listening and the port is actually open.

Why will my RaiderZ server not start?

Usually a database it cannot log in to, a missing runtime, or a port already in use by something else. The server console or log normally names the cause on the first failure, and the processes often have to be started in a particular order.

How do I get a useful answer about RaiderZ here?

Post the RaiderZ build you are running, the file set you used, the exact error text and what you have already tried. Threads with that detail get answered; vague ones usually do not.

Tags used in Raiderz Help

• raiderz