Jackal
From NFBSP
| Jackal | |
|---|---|
| Author(s) | FordGT90Concept |
| Size | 16.0 KiB |
| Release Date | 28 Jan 2009 |
| Current Version | 1.2.1 |
| Prerequisites | .NET Framework 2.0 |
| CLR Compliant | No |
| Download | |
Notice: This program is now deprecated. The latest server patch has the ability to disable pjump without any extra programs required with no side effects. Simply install the latest server patch from the [NORULEZ website] and change the sv_pjump command to 0 in your server.cfg or in console.
An active countermeasure against momentum exploits including "pjumping" and speedhacks.
Contents |
[edit]
Usage
- Review the "Warnings" below.
- Run it from anywhere. It will attempt to find Dedicated Nightfire automatically. If it can't find any or finds more than one, it will ask you which to attach to.
- Once it has a process to attach to, it will start the Heartbeat and Jackal threads. It is now fully functioning.
- Base Address: The location in the memory it is using to base further searches from.
- Discovered Players: The list of players being monitored.
- Threads Active: This is blank unless the application is properly functioning. It will display "HEARTBEAT" if the player list is being updated. It will also display "JACKAL" if it is actively stopping people from using the Momentum Exploit.
- Punishment Method: This setting controls the behavior of how to react to people that are speeding. The options are:
- Reset to a second ago at 0 in/s: If it sees someone speed, it marks them as caught. If they are still speeding at the next check, it will reset them to where they were when they were originally caught. It will also set their velocity to zero meaning they may fall out of the sky. Prefers a higher delay value.
- Slow to 250 in/s: At every iteration, it checks if the player is currently speeding. If they are, it scales their linear velocities down to 250 at most. For instance, if you're moving at 1000 on x and 100 on y, x will become 250 and y will become 25. Prefers a lower delay value.
- Halve velocity: At every iteration, it halves the linear velocities of those speeding. For instance, if you were moving 1000 on x and 100 on y, x will become 500 and y will become 50. The next iteration (assuming the player maintained those velocities) will reduce x to 250 and y to 25 because they are still offending the default angular velocity rules (see Low, Grapple Low, and Grapple High below).
- None: Disables the checking and punishment of those breaking the limits. The thread still runs which allows you to reenable any of the other options at any time with immediate effect.
- Delay (milliseconds): This is how much time is between each iteration in millseconds (min 100; max 1000). The lower this value, the more frequently it runs meaning it is more likely to catch those violating the limits; however, it comes at a performance penalty by tying up more clocks that would otherwise be used for something else. If Nightfire is lagging while using Jackal, try using a higher value. 500 is default.
- Velocity Limit (in/s): This is the lowest speed to consider speeding. This is an angular velocity, not linear. 440 is default. This value must be greater than 0 and less than Grapple Low.
- Grapple Low (in/s): Along with Grapple High this forms an exception for the grapple to prevent grapple use from being interrupted. 575 is default. This value must be greater than Velocity Limit and less than Grapple High.
- Grapple High (in/s): Along with Grapple Low this forms an exception for the grapple to prevent grapple use from being interrupted. 625 is default. This value must be greater than Grapple Low.
If AngularVelocity > VelocityLimit And AngularVelocity < GrappleLow Player is Speeding If AngularVelocity > GrappleHigh Player is Speeding
Examples of this (assuming defaults speeds are used):
250.0 Not Speeding MAXIMUM: Linear Run Velocity (X- & Y-axis)
260.3 Not Speeding MAXIMUM: Linear Jump Velocity (Z-axis)
300.0 Not Speeding MAXIMUM: Linear Run Velocity (X- & Y-axis) w/ Speed Powerup
439.1 Not Speeding MAXIMUM: Angular Run Velocity
440.0 Not Speeding DEFAULT: Velocity Limit
440.1 Speeding
497.8 Speeding MAXIMUM: Angular Run Velocity w/ Speed Powerup
500.0 Speeding
574.9 Speeding
575.0 Not Speeding DEFAULT: Grapple Low
600.0 Not Speeding MAXIMUM: Angular Grapple Velocity
625.0 Not Speeding DEFAULT: Grapple High
625.1 Speeding
800.0 Speeding
1000.0 Speeding
9999.9 Speeding
etc.
[edit]
Warnings
- Before running it, make sure Nightfire is hosting a server and someone has joined. If you don't do this, it is liable to make Nightfire rather laggy.
- Once it found someone, it is safe to leave it running even if there are no players in the server. It will automatically detect if someone joined.
- It is highly recommended not to use this application on single core processors. It will likely be too detrimental to the game performance.
[edit]
Known Bugs
- Sometimes it detects two of the same person. This doesn't cause any problems as it will monitor both. Eventually, one will go away and the correct one will remain.
- Sometimes it doesn't detect someone altogether. Please use the discussion page on the Wiki to notify me of this. If it happens with great frequency, an updated version will be released correcting it.
[edit]
Version History
- 1.2.1 - Fourth public release. Includes mostly cosmetic changes to reflect research done on jumping.
- 1.2.0 - Third public release. This verison adds many options including methods, rates, and values to customize the operation of the software. It also saves those changes to "settings.bin" on close and reloads them on opening.
- 1.1.0 - Second public release. Most code has been updated to use 64-bit integers instead of 32-bit signed and unsigned integers. Basically, this means the software is far more stable but may run slower on 32-bit computers. It also has several other changes to improve stability.
- 1.0.2 - Private release. Fixed multiple minor bugs.
- 1.0.1 - First public release. Updated meta data and made the Heartbeat a little more efficient.
- 1.0.0 - Private release.
[edit]
