NSS Docs
nss_players_snapshot
Search
K
Links

README

Visit our Discord / Homepage / Store !

Requirements / Dependencies

The following resources are required for nss_players_snapshot to work:

Changelog

See CHANGELOG.md for more information.

Features

  • Players can snapshot nearby players for later support requests.
  • Snapshots will be sent to a configurable Discord channel.
    • Discord message contains reporter and reported players (sorted by range to reporter)
    • Detailed information:
      • Coordinates of each player
      • Char ID & Name
      • Steam ID
      • Discord ID
      • IP
      • Status icons (v1.0.1)
  • Includes configurable anti spam protection.
  • All configurable!
    • Snapshot range (radius in meters)
    • Snapshot key (combinable with modifiers like SHIFT + B or CONTROL + B)
    • Snapshot sound
    • Delay for anti-spam protection
    • Discord webhook & avatar
    • All in-game messages are configurable
    • Full language support
    • Detail of information is configurable (v1.0.1)
  • Resource injection detection (v1.1.0)
    • Detects if a client resource is not available on server and post a warning to a specific Discord channel.
  • Cam abusing detection (v1.2.0)
    • Detects the distance between current camera und player coordinates to detect possible cheaters.
    • Log possible cam abusers to a specific Discord channel.
    • If you use spooner you can test it ;)
  • Never miss updates again:
    • Automatic version check included.
    • Automatic dependency version check included.
  • Know how it works: Everything is documented in detail in the README.md and commented in the demo.config.lua file.

Open ToDo's

  • Give the reporter a snapshot ID, so he can use this in support tickets.

Known issues

  • Currently, no known issues.

Setup script

  1. 1.
    Ensure that the nss_players_snapshot folder is in your resources folder.
  2. 2.
    Rename config.demo.lua to config.lua and fill in the values.
  3. 3.
    Add ensure nss_players_snapshot to your server.cfg.
  4. 4.
    Restart your server.

FAQ

Currently, no FAQ available.
Last modified 1mo ago