DocumentationStrict Mode (Auto-Kick)

Strict Mode (Auto-Kick)

Choose whether standard clients may play or whether every player must have a valid Spynixx Launcher announce before joining.

Optional and Strict Modes

Mode 0: Detect and Reward

Default mode. Standard clients may join, while verified launcher players can receive the permanent first-use package and five-hour milestone rewards.

Mode 1: Require Launcher

Players without a matching launcher announce are shown the requirement message and kicked after the configured delay.

Enable Strict Mode

Edit the configuration section of pawno/include/spynixxlauncher.inc, set SPYNIXX_REQUIRE to (1), then recompile both the filterscript and gamemode so they use the same configuration.

pawno/include/spynixxlauncher.inc

// pawno/include/spynixxlauncher.inc

// 0 = allow standard clients; launcher users receive rewards
// 1 = kick players without a matching pre-join announce
#if !defined SPYNIXX_REQUIRE
    #define SPYNIXX_REQUIRE       (1)
#endif

// Delay before a non-verified player is kicked
#if !defined SPYNIXX_GRACE_MS
    #define SPYNIXX_GRACE_MS      (8000)
#endif

#if !defined SPYNIXX_MSG_REQUIRE
    #define SPYNIXX_MSG_REQUIRE   "[+] This server requires the Spynixx Launcher. Download it and join again."
#endif

Exact Auto-Kick Flow

The launcher sends its TCP announce before starting the game connection.
During OnPlayerConnect, the filterscript immediately tries to consume a valid pending announce.
If no record matches, the player remains unverified and an 8,000 ms kick timer starts.
When the timer expires, an unverified connected player receives SPYNIXX_MSG_REQUIRE and is kicked.

What the grace setting means: SPYNIXX_GRACE_MS delays the kick notice. The current filterscript does not retry or consume a late announce during that delay, so increasing it does not make a post-connect announce valid.

Test Checklist

Start the server and confirm that the filterscript reports listening on 0.0.0.0:11020.
Join through Spynixx Launcher and confirm the server logs a successful announce and launcher join.
Spawn and confirm the detected message and first-use reward, then reconnect and confirm the saved reward is not issued again.
Reconnect without the launcher and confirm the requirement message followed by a kick.
Confirm NPC players are ignored by verification and auto-kick logic.

Troubleshooting

Symptom	Check
Every player is kicked	TCP `11020` firewall rule, launcher host/port, detect token, and whether the socket plugin loaded.
Server reports `socket_create failed`	Use `socket.dll` on Windows or `socket.so` on Linux and load it before the filterscript.
Verified but no rewards	Confirm `#include <spynixxlauncher>` is compiled into `main.pwn`, the player has spawned, and check whether that name already has saved progress in `scriptfiles/spynixxlauncher_rewards.ini`.
Announce returns `ERR:auth`	Player name length must be valid and the launcher token must match `SPYNIXX_SECRET`.

← Back to Rewards System