NOLF PLUS 0.94 Beta - By Dan

Download: http://www.nolfgirl.com/files/pafiledb.php?action=file&id=406
Main Site : http://nolfplus.nolfgirl.com
General Discussion: http://thegluefactory.com/forums/forumdisplay.php?f=40
Report Bugs: http://thegluefactory.com/forums/forumdisplay.php?f=41

Important: This is a beta release and as such may contain bugs, if you find a bug and you can reproduce it, please report it here. Note that this mod does not make it impossible to cheat, it does however stop a large number of known expoilts. Any new cheats or missing fixes will be addressed if reported.

1. Installation
2. Fixes & New Features Overview
3. General Notes
   1. File Protection
   2. Map Hack Prevention
   3. Client-side Chat Logging
   4. Next Map Information
   5. Screenshot Mode
4. Server Hosts
   1. MapPunish
   2. Speed Hack Detection
   3. Logging
   4. Banning & The Ban Manager
   5. Auto Message
   6. Server Side Health & Armor commands
   7. ListClients command

Installation

1. Extract the installation zip file using WinZip to your No One Lives Forever Directory. This is usually "C:\Program Files\Fox\No One Lives Forever\".
2. Start No One Lives Forever. On the Launch Window click "Advanced..."
3. Click on "Customize"
4. Highlight NOLFPLUS.REZ in the left hand listbox and click the "Add >" button
5. Ensure "Always load these rez files" is ticked
6. Click on "OK", then "OK" again and then click on the "Launch" button to start No One Lives Forever.

To Remove

1. Start No One Lives Forever. On the Launch Window click "Advanced..."
2. Click on "Customize"
3. Highlight NOLFPLUS.REZ in the right hand listbox and click the "< Remove" button
4. Click on "OK", then "OK" again and then click on the "Launch" button to start No One Lives Forever.

Fixes & New Features

Fixes

New in V0.94:

• Zip Cord Exploit (another variant)
• Pic Exploit
• Corrector Jumping
• Additional key multiplayer file checking
• The Pad DM - Box Hack & Mountain climbing
• Exploit checking Blizzard AM Changed
• Exploit checking Hydro AM Changed
• Periodic updates of client ammo from the server
• Ping time update frequency reduced to reduce bandwidth usage

0.93 and earlier:

• Protection against tampering with key multiplayer files. This prevents many known (and unknown) hacks, including:-
• Cameo Skins
• Walk Through All Walls Hack
• Reload Hack
• Extra Health for given model hack
• Zip Cord Hack
• Map Hack Prevention - prevents some known hacks on the following maps :-
• Hydro – Base Wall Exploit & Wall Climbing Exploit
• Beaujolais - Wall Climbing Exploit
• Blizzard - Wall Climbing Exploit
• Oasis - Wall Climbing Exploit
• The Pad - Wall Climbing Exploit
• ChillKill - Wall Climbing Exploit
• Club Dead - Wall Hack
• Server Crash Exploit
• Run Speed Hack (Velocity tracking) - See below
• Vehicle Flying Exploit
• Remote Server Control Exploit
  • Changing Server Settings Remotely
  • Spawning vehicles
  • Running Server Console Commands
• Chat as any player Exploit
• GameSpy Password Display Exploit.
• Joining Password Protected Server With No Password
• Blank Player Names (no longer allowed)
• Player Name DoS Exploit
• Spectator Mode Exploit
• Wireframe Hack
• Proxy Mine "Jump" Exploit
• Shoot Through Walls Exploit

New Features

New in V0.94:

• Server console commands to control Armor and Health Settings
• ListClients server console command
• Ban Manager now includes column sorting

V0.93 and earlier:

• Server Console Logging
• Banning (including standalone Ban Manager)
• Server Auto Message
• Clientside Chat logging
• Next Map Information
• Screenshot Mode
• Server Side Health and Armor Options

General

File Protection

A new attributes file now exists called verifybutes.txt, this holds the list of files which are integrity checked when NOLF starts. If the file does not match the CRC value held in verifybutes, an error message will be displayed and NOLF will shutdown.

Common Questions

Won't cheaters just be able to change verifybutes.txt and then join the server with their cheats?

Yes and No. They will be able to edit the file, however when a player connects to a server, the client side verifybutes.txt is checked to ensure it is exactly the same as the server side copy, if it's not, the player will not be allowed to connect.

Which attribute files are checked during the handshake process?

The following files are checked during the client server handshake process:-

• weapons.txt
• verifybutes.txt
• modelbutes.txt
• fx.txt

If these files are not exactly the same as the server side copy, the player will not be allowed to connect.

Map Hack Prevention

The following maps contain "hot spots" where common expoilts take place, if a player moves into any one of these areas, they will be booted from the server automatically:

• Hydro
• Beaujolais
• Blizzard
• Oasis
• The Pad
• ChillKill
• Club Dead

These maps also include a "hot spot" directly above them to try and prevent wall climbing. If a player goes higher than the allowed limit, they will be either be killed or booted from the server automatically (depending on the MapPunish setting (see the Server Hosts section).

Beta Version Note: If you get punished by the server when you believe you shouldn't have, type mppos in the game chat. This will display your x,y,z coordinates in the bottom right of the screen. If you can reproduce it, make a note of your coordinates just before you get punished and report it at the support forums (see link at the beginning of this readme).

Client-side Chat Logging

This will log all game chat (on the client) that the player can normally see. The log filename is nolfchat.log and is held in the main NOLF directory.

Note: This options is off by default, but can be switched on under Options -> Game -> Log Chat

Next Map Information

This will display the next multiplayer name name at the bottom of the player scores screen (TAB key in the game).

Note: This options is on by default, but can be switched off under Options -> Game -> Show Next MP Map

You can also see the next map name when browsing the Server List on the Join Game screen in NOLF.

Screenshot Mode

This will remove every part of the HUD apart from your current score, for the purposes of taking "cleaner" screenshots.

To Switch on or off the Screenshot Mode

Press the F3 key while playing.

Server Hosts

MapPunish

This setting controls how the server punishes a player if they use a detected map exploit; either by kiling the player or kicking them from the server.

To set the server to kill players

In the server console type "MapPunish 0" (without the quotes)

To set the server to kick players

In the server console type "MapPunish 1" (without the quotes)

The default setting is 0 (kill the players). You can check the current setting by typing "MapPunish" (without the quotes) in the server console.

Speed Hack Detection

Speed hack dectection is off by default (see warning).

To Switch on Speed Detection

In the server console type "SpeedDetect 1" (without the quotes)

To Switch off Speed Detection

In the server console type "SpeedDetect 0" (without the quotes)

Fine Tuning

If you find that on the odd occasion players are getting kicked for speed hacking when they shouldn't, you can fine tune the speed detection (note: In this beta release, this setting is not fine tuned yet!)

NOLF Plus makes use of a varible called SpeedThreshold which is essentially a multipiler that is used when calculating if a player is exceeding the speed limit. By default it is set to 2.0.

To adjust this multiplier, in the server console type "SpeedThreshold 2.0 " (without the quotes) - the higher the value, the less strict the detection.

To check the current value, in the server console type "SpeedThreadhold" (without the quotes)

WARNING: Only change SpeedThreshold by +/- 0.1 each time, then test, getting this value wrong could mean all of your players get kicked.

Logging

To turn on logging, in the server console type "UseLog 1" (without the quotes)
To turn off logging, in the server console type "UseLog 0" (without the quotes)

Banning & The Ban Manager

Every player is assigned an unique ID. This ID is displayed in the server console when the player joins the game, chats or is kicked. The the ban list is held in bans.txt in your main nolf directory.

Ban Manager

The Ban Manager(nolfbanmgr.exe) is a standalone application that allows you to create, modify and delete bans easily. Note that if bans.txt does not exist, it will be created automatically by either the NOLF Server (on startup) or the Ban Manager. You can sort the information displayed in the Ban Manager by clicking on the column headers.

To ban a player:-

1. Make a note of the players ID.
2. Start the NOLF Ban Manager (nolfbanmgr.exe)
3. Add the Player ID as a new ban (remember to click the "Write Ban List" button!)
4. In the server console type "UpdateBans 1" (without the quotes)
5. You should then see "<+> Ban list update successful" in the server console

The player is now banned and will be auto kicked should they attempt to reconnect.

To unban a player:-

1. Make a note of the players ID.
2. Start the NOLF Ban Manager
3. Either delete or disable the ban (remember to click the "Write Ban List" button!)
4. In the server console type "UpdateBans 1" (without the quotes).
5. You should then see "<+> Ban list update successful" in the server console.

The player is now unbanned and should be able to connect.

Auto Message

Allows a custom message to be sent every between every 5 and 30 minutes to all players on the server.

To Set an Auto Message

1. In the server console type "AutoMsgStr "This is an example Auto Message"" (without the external quotes)
2. In server console type "AutoMsg 5" - this will display your custom message every 5 minutes to players on your server.

Note: The AutoMsg command will accept values between 5 and 30, values outside of this range will be ignored.

To switch off an Auto Message

In server console type "AutoMsg 0" (without the quotes)

Server Side Armor & Health Commands

Four new commands allow you to overide the settings held in modelbutes.txt from the servers console for Maximum Armor, Armor, Maximum Hit Points and Hit Points.

New Commands

MaxArmor - The maximum armor that a player is allowed to hold.
Armor - The initial armor that a player has when they spawn.
MaxHitPoints - The maximum health that a player is allowed to hold.
HitPoints - The initial health that a player has when they spawn.

Note that if you change these settings during a game, the players will not be updated with the new settings until they respawn.

To check the current value of a command

Type the command name the server console e.g. "Armor" (without the quotes).

The default value for all four commands is -1, meaning that the server will use the values in modelbutes.txt. See modelbutes.txt for more information about suitable values to use with these commands.

Important: These settings are saved when you shutdown the server, so they will be reused the next time the server is started. If the server crashes, they will not be saved.

ListClients Command

The ListClients command displays various information about the clients on the server - Player Name , UID, Team (if playing AM), Maximum Velocity and Last Known Position.

To run the ListClients command, type "ListClients 1" in the server console (without the quotes).

You will see a display similar to the following:

<+> 1. PlayerName1 (123456), Team: Unity, Max Vel: 432, Last Pos: <-5568,2101,1920>
<+> 2. PlayerName2 (1234567), Team: HARM, Max Vel: 433, Last Pos: <5824,2101,320>

The breakdown of this display is:

1. Player Number (1..Max Number of players allowed)
2. Player Name
3. Player UID
4. Team - only displayed if playing AM
5. Maximum Velocity - The Maximum Velocity that the player has reached while playing on the server (note this value will be zero the first time the player spawns on the server, because they have not yet moved)
6. Last Position - The players last reported position in the map in X,Y,Z coordinates

Note that if they are no clients on the server, this command will return nothing.

"Dancing Goodman" by Monolith Productions
This add-on is not made by or supported by Monolith Productions, or any of its affiliates and subsidiaries.