Disable SysStats kicking on join

If you try to join an RCC GameServer and the Golden Hash (and/or normal hash) isn't correct, it will kick you.

What even are those hashes? They just represent if the client is signed or not, and since revivals usually don't have the money to sign applications, we can't do that.

Tutorial

Open your RCC FFlags (either stored locally, or on the server as RCCService(your settings key) or ClientSharedSettings, returned through QuietGet or /v1/application/settings), and add (or change) these 2 fflags:

"DFFlagUS30605p2": "____7____6____5____4____3____2____1____0",

"DFFlagUS30605p1": "____7____6____5____4____3____2____1____0",

Explanation

The US30605p DFFlags represent the behavior of incorrect hashes, here is what the characters mean (from 2016 source code):

static const char kKickChar = '.'; // kick+report for normal hash only

static const char kGoldKickChar = ':'; // kick+report for gold hash and

static const char kReportChar = 'r'; // report for normal hash only

static const char kGoldReportChar = 'g'; // kick for normal hash, report gold hash

// (any other char) ignore

// every 5th character is a number

By making both of these DFFlags filled with _ (other characters), it disables kicking the player when the client is unsigned.

More specifically, the p1 DFFlag is SendStats config, while the p2 DFFlag is HashStats config, there is also p3-p5, but they are normal sysstats (ApiStats, MccStats, ExtraStats), so you shouldn't disable them.