How to restrict enchant, classes and skills in PvP events

[Joselito]

Config file: config\pvp_events.properties
Goal: Improve fairness and reduce broken builds inside TVT/CTF/DM.

1) Enable enchant restrictions​

PvPEventsRestrictEnchant = True
PvPEventsEnchantStatLevelArmor = 6
PvPEventsEnchantStatLevelMageWeapon = 8
PvPEventsEnchantStatLevelPhysWeapon = 8
PvPEventsEnchantStatLevelAccessory = 6

This caps effective enchant in events and prevents over-geared domination.

2) Restrict classes (optional but useful)​

PvPEventRestrictClassId = 13,14,15

• Comma-separated class IDs.
• Use this only when a class is truly unhealthy for your event design.

3) Restrict problematic skills​

PvPEventsRestrictedSkillIds = 5000;5001;5002
PvPEventsRestrictClanSkills = True

• Skill IDs separated by ;
• PvPEventsRestrictClanSkills = True helps reduce gap between casual clans and max-skill clans.

4) Protect registration from fake/dual abuse​

PvPEventRestrictIP = True
PvPEventRestrictHWID = True

• IP restrict: blocks same-network multireg abuse (with caveats for LAN houses).
• HWID restrict: stronger if your guard/protection supports it.

​

5) Balanced example​

PvPEventsRestrictEnchant = True
PvPEventsEnchantStatLevelArmor = 6
PvPEventsEnchantStatLevelMageWeapon = 8
PvPEventsEnchantStatLevelPhysWeapon = 8
PvPEventsEnchantStatLevelAccessory = 6
PvPEventRestrictClassId =
PvPEventsRestrictedSkillIds = 7029;7030
PvPEventsRestrictClanSkills = True
PvPEventRestrictIP = True
PvPEventRestrictHWID = False

​

6) Common mistakes​

• Wrong separator for skills/classes.
• Blocking too many classes and killing event diversity.
• Forgetting to test all 3 modes after applying restrictions.

​