Validation

How to validate yourself in NQR

---

To avoid any stressed situations that can occur when people have no idea what a ruleset is and they are 20 minutes overdue for playing, with an admin trying to help them fix all problems, here is how you make sure that you are valid for playing. Before you start, connect to a server of choice, or just type /map dm4, whatever you choose as long as you are on a map and can move around. Then proceed to make sure that you pass these 3 tests.

Version validation

Check what client version you are using by typing: f_version

For nQuake/ezQuake users:

The correct response is: ezQuake 1.8.3 stable (build 2160)

If you get a different response, follow these step:

1a (for versions 1.8, 1.8.x or 1.9). Download the ezQuake 1.8.3 executable (Win32).

1b (for versions older than 1.8). Download the ezQuake 1.8.3 full release (Win32 Linux32 Mac OS X FreeBSD).

2. Extract the archive to your Quake folder.

3. Start Quake again.

For FuhQuake users:

The correct response is: FuhQuake 0.31 (build 675)

If you get a different response, follow these steps:

1. Quit Quake.

2. Download FuhQuake 0.31 build 675 (Win32)

3. Extract the archive to your Quake-folder.

4. Start Quake again.

For FTE users:

The correct response is: FTEQuake v3343

If you get a different response, follow these steps:

1. Download FTE 3343 (Win32 Linux32 Linux64 MorphOS).

2. Extract the archive to your Quake-folder.

3. Start Quake again.

Models and sounds validation

Check if you have any modified models/sounds by typing: f_modified

For nQuake/ezQuake/FuhQuake/mQWCL users:

The correct response is: all models ok

If you get a response like "armor.mdl backpack.mdl grenade.mdl armor1.wav itembk2.wav & more..." it means that you have modified models/sounds. To fix this you can try the following things:

1. Go to your Quake-folder and go into the id1-folder.

2. Make sure that the only .pak-files you have are pak0.pak and pak1.pak.

3. Rename any other .pak-files so they end in .bak.

4. If you have a progs-folder here, rename it to progs.bak.

5. If you have a sounds-folder here, rename it to sounds.bak

6. Go up one step to your Quake-folder and go into the qw-folder.

7. Rename any .pak-files so they end in .bak.

8. See a progs-folder here? Rename it to progs.bak.

9. Same thing for any sounds-folder you might have.

10. You may restart Quake between each file or folder that you rename to track down where the problem lies, and only rename that particular file/folder.

For FTE users:

By using ruleset nqr it will autovalidate models for you the next time you connect.

Ruleset validation

Check your ruleset by typing: f_ruleset

For nQuake/ezQuake users:

The correct response is: ezQuake Ruleset: smackdown [rj scripts blocked]

If you get a response like ruleset: default you need to follow these steps:

1. Disconnect from the server.

2. Type: ruleset smackdown

3. Type: allow_scripts 0

4. Reconnect to the server.

5. You may cfg_save these settings so they apply for the future too.

For FuhQuake/mQWCL users:

The correct response is: FuhQuake Ruleset: smackdown [rj scripts blocked]

If you get a different response, follow these steps:

1. Quit Quake.

2. Add these flags to your commandline: -norjscripts -ruleset smackdown

3. Start Quake and reconnect to the server.

For FTE users:

The correct response is: Ruleset: nqr

If you get a different response, follow these steps:

1. Disconnect from the server.

2. Type: ruleset nqr

3. Reconnect to the server.