This seems to go against Endelyon's wish that: "It's okay to make an (un)needed suggestion. We'll discuss them staff-side, and if we need a public debate about them we'll ask for one. Likewise, QCers shouldn't be posting here telling a user why a suggestion isn't viable or would tilt the module balance when programmers and development staff aren't even considering implementation of that change in the first place."
This New Rule #2, b and c subset, seem to be the most challenging to argue for and against violation:
My suggestion is as follows:Examples of reasons it is not okay to reply: b.) you want to discuss the mechanical balance or other aspects of a suggestion, c.) want to use the original suggeston to spark a debate on another aspect of the game will suffer,
- Allow any Player in good standing to post a Suggestion, Issue or Bug Report.
- That Post is auto-locked, for immediate/eventual review by Staff.
- A QC Coordinator or even a Forum Moderator may unlock the Post, if they deem it warrants public discussion, while still following the New Rules as stated by Endelyon.
- If QC takes up the issue staff-side, then a follow up post is made by the QC Coordinator, or if necessary, a QC member that has taken it staff-side.
- Results or decisions for or against the OP is made when possible, to allow for closure.