1.5.3BETA
Config Guard + clearer detection settings
Parity now checks your own resources for scripts that a detection would mistake for cheating, and the detection settings are rebuilt so every choice is clear.
- Action: Do a full FXServer restart after updating (not just ensure).
- Action: Open Configuration → Detections once after updating and review what Config Guard found on your server.
- New: Config Guard checks your resources on your own server on every start, with progress in the console and the dashboard. If one of your scripts does something a detection would see as cheating, that detection only logs until you decide. Your code never leaves your server; only the resource name, file name, line number and function name are shown. You can switch it off.
- New: Integrity Protection: choose the reaction for each INT code (Off, Log, Kick or Ban). The protection itself always stays active.
- New: Detection settings redesigned: one row per detection with a single Off, Log, Kick or Ban choice, groups that show how many checks are on, filters and a phone layout.
- New: The Live Console tells you when Parity isn't allowed to run server commands, shows the line to add to your server.cfg, and can add it for you.
- Improved: Staff with the admin menu permission are no longer flagged for using Parity's own admin menu features.
- Improved: Anti License Clear is now part of Anti Injector, and Anti Speed Changer is part of Speedhack.
- Improved: Removed settings that had no effect: Framework Spawn Guard, Combat Roll, Steal Outfit and the Trolling Module.
- Improved: Fewer server hitches while Parity starts.
- Improved: Install on All for the Isolation Guards shows its progress and lists any resource it could not change, with the reason.
- Fixed: Anti Injection Guard reports did not reach the dashboard.
- Fixed: The allowed list for attached entities was not applied.
- Fixed: Local Event Spoofing ignored its list of allowed resources.
- Fixed: Physic Gun logged the wrong player.
- Fixed: False INT-002 bans when joining.
- Fixed: Restarting a resource while Parity was starting could crash the server.
Release notes: Do a full FXServer restart after updating. Then open Configuration → Detections once: Config Guard lists scripts on your server that a detection would otherwise mistake for cheating.
Download 1.5.3