Janek
Member
- Joined
- Nov 13, 2021
- Messages
- 67
- Thread Author
- #1
Following recent events, undoubtedly the September 19th raid on The Front's base, I'd like to propose solutions to address some noteworthy issues in the Combine vs Rebels (CvR) engagements seen. The goal is to promote fairness, have rules clarified, and improve the player experience for both factions. These suggestions aim to tackle problems like wave timer disputes, inconsistent permakill (PK)/New Life Rule (NLR) rulings, raid justifications and missed roleplay (RP) opportunities.
Suggestions
1. Clarify and Enforce Wave Timer Rules (Ref: Guidelines Section 6, Rule 3.2 General Scale Crimes):
Rule 3.2 mandates a 10-minute cooldown between waves for "general scale" crimes, but the recent raid saw an Overwatch Transhuman Arm (OTA) wave deployed 5-8 minutes after a Civil Protection (CivPro) response sweep's defeat, disrupting roleplay like hostage negotiations. Confusion arose over whether the initial sweep was "generic" or a "response" to a crime, as it was claimed to be generic, while a dispatch player called it a response sweep.
Proposals:
The PK Policy outlines specific PK scenarios and NLR conditions, but the raid saw inconsistent rulings; responding rebels were PKed, while base defenders and Combine players received NLR, some without refunds. This contradicts the PK Policy's "Not an involved party, but engaged in combat = NLR (no refund)" rule.
Proposals:
The rapid OTA deployment disrupted roleplay opportunities (e.g. hostage negotiations, evacuation planning and MedRP).
Proposals:
Players holding both rebel and Combine roles risk metagaming, as speculated in several instances, when many rebels were offline (The Front Raid as a notable example).
Proposals:
Some players feel uninformed about staff decisions (e.g. raid approvals, PK rulings), leading to mistrust.
Proposals:
Please share your thoughts to refine these suggestions. Thank you for reading.
Suggestions
1. Clarify and Enforce Wave Timer Rules (Ref: Guidelines Section 6, Rule 3.2 General Scale Crimes):
Rule 3.2 mandates a 10-minute cooldown between waves for "general scale" crimes, but the recent raid saw an Overwatch Transhuman Arm (OTA) wave deployed 5-8 minutes after a Civil Protection (CivPro) response sweep's defeat, disrupting roleplay like hostage negotiations. Confusion arose over whether the initial sweep was "generic" or a "response" to a crime, as it was claimed to be generic, while a dispatch player called it a response sweep.
Proposals:
- Define Sweep Types: Update Rule 3.2 to explicitly define "generic" (e.g. routine patrols with no specific IC trigger) vs "response" sweeps (e.g. triggered by reported crimes, defeated waves, or specific IC events like spotting rebels). Specify or clarify whether response sweeps always trigger a 10-minute cooldown.
- Admin Oversight: Require a staff member to monitor high-stakes CvR engagements (e.g. base raids) to enforce the 10-minute timer, using in-game logs or timers to verify.
The PK Policy outlines specific PK scenarios and NLR conditions, but the raid saw inconsistent rulings; responding rebels were PKed, while base defenders and Combine players received NLR, some without refunds. This contradicts the PK Policy's "Not an involved party, but engaged in combat = NLR (no refund)" rule.
Proposals:
- Define an example in the "Example Scenario" column for "Not an involved party, but engaged in combat = NLR".
- Pre-Approval for PKs: Require a large staff-wide pre-approval for PKs in major raids, especially for responders, to align with the PK Policy's emphasis on fair and warranted PKs.
The rapid OTA deployment disrupted roleplay opportunities (e.g. hostage negotiations, evacuation planning and MedRP).
Proposals:
- Hostage Protocols: Add a guideline requiring Combine forces to attempt negotiations for High IC Value Characters before escalating, unless IC circumstances justify immediate action.
- Leader Training: Provide training for faction leaders (e.g. OTA lead(s)) on balancing combat and RP, with mentorship from senior staff and the like.
Players holding both rebel and Combine roles risk metagaming, as speculated in several instances, when many rebels were offline (The Front Raid as a notable example).
Proposals:
- Role Restrictions: Amend Section 2 to prohibit players from holding leadership roles in opposing factions (e.g. Rebel Group and CivPro commander) to minimize metagaming risks and conflicts of interest.
- Activity Monitoring: Require players to declare active factions during major events, with admins tracking logoffs/switches for potential metagaming or changes due to conflicts of interest (e.g. switching off Combine when certain rebels are active).
Some players feel uninformed about staff decisions (e.g. raid approvals, PK rulings), leading to mistrust.
Proposals:
- Event Debriefs: After events such as sweeps and/or raids, post brief admin summaries on the Willard Networks (WN) Discord or forums (e.g. "Raid approved per IC scout report; PKs issued per PK Policy...) to clarify decisions without necessarily naming players.
- Private Feedback Channel: Create a ticket system for the WN's Discord server for players to submit rule and decision concerns directly.
Please share your thoughts to refine these suggestions. Thank you for reading.

