Connection protection, anti-dupe and anti-hack tuning
Protection settings can reject legitimate sessions or remove duplicated items. Tune with evidence from the relevant logs and a controlled test account.
The outcome to aim for
Protection settings can reject legitimate sessions or remove duplicated items. Tune with evidence from the relevant logs and a controlled test account.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
AllowableIpList files restrict trusted service connections. Use the deployment’s actual addresses and keep backend SQL/DataServer/JoinServer access restricted to their intended network.
- STEP 2
MaxIpConnection and MaxConnectionPerHID are different limits. Test users sharing one public IP separately from multiple sessions on one device.
- STEP 3
For duplicate-item scanning, AutoQuetItemDupe, TimeQuetItemDupe, DeleteDupeItem and DisconectDupeItem affect scan, interval, deletion and disconnect behavior. Do not test deletion against valuable player inventories.
- STEP 4
Speed/latency/potion/combo checks use distinct tolerance fields. Change one check at a time and record false positives under normal latency.
- STEP 5
Use the relevant reload group or service restart, then verify normal login, reconnect, transfer and expected rejection. Preserve the owner’s private license and service configuration.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →Verify the result in game
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.