The Feedback Process
This document defines how feedback flows on WesterosCraft, who provides authoritative feedback in different contexts, and the tools and channels used in our process. The goal is to make feedback predictable, constructive, and actionable.
Feedback Hierarchy
Feedback can come from different avenues, but not all of it carries the same weight. This hierarchy clarifies whose input is advisory versus authoritative.
Authoritative Feedback
Authoritative feedback must be addressed before a build can progress. The builder is expected to implement changes or discuss alternatives with the feedback giver.
ContextAuthoritative SourceNotesApprentice probation buildsAssigned StewardSteward has final say on probation requirementsPlots within a projectProject LeadProject Lead defines style, layout, and expectationsProject applicationsWarden(s)One Warden for Canon; two for Server and City ProjectsRegional style complianceWardenWarden maintains regional consistencyServer rules & conductMaesterFinal authority on rule interpretation
Advisory Feedback
Advisory feedback is valuable input from community members. Builders should consider it thoughtfully but are not obligated to implement it. Advisory feedback includes:
- Suggestions from fellow builders who are not the Project Lead
- Style ideas from builders outside the project's region
- General community commentary
Builders may choose to incorporate advisory feedback, but if it conflicts with authoritative feedback, the authoritative source takes precedence.
When Feedback Sources Conflict
If authoritative sources disagree (for example, a Project Lead and Warden have different views):
- The builder should not be caught in the middle. Pause changes.
- The conflicting parties should discuss and reach consensus.
- If no resolution, escalate to a Maester to mediate a ruling.
- Document the decision in the project thread for future reference.
Giving Feedback
Providing feedback is a valuable way to contribute to WesterosCraft's growth. To ensure feedback is constructive and useful, focus on specific aspects you want to address, maintain a respectful tone, and offer suggestions for improvement rather than just pointing out problems.
- Make sure all feedback given in-game via melons, note blocks, or any other method includes your name. You are responsible for your feedback and should stand by it. Any untagged feedback can be removed by the build leader.
- Use positive and constructive language when giving feedback. Avoid solely negative criticisms of creative choices, and instead emphasize potential improvements.
- Be clear and concise in your observations to ensure better understanding. Vague feedback is harder to act on.
- Never use feedback blocks to intentionally intimidate, bully, or negatively impact another player's experience. Any instances of this should be flagged to the mod team for suitable action.
Use the appropriate channels, whether that's in-game messaging, Discord, or with the right builder, to share your feedback effectively.
Receiving Feedback
Receiving criticism and feedback with an open mind is crucial for a collaborative, thriving community. Feedback plays a significant role in refining our builds and enhancing the overall experience.
- When receiving feedback, actively listen to what others have to say without becoming defensive. Keep an open mind and be willing to consider different perspectives.
- Show appreciation to those who take the time to offer their insights. Their input demonstrates their commitment to helping the community grow.
- Remember that feedback is usually given with good intentions, even if the delivery isn't perfect. Be considerate of the feelings and efforts of those trying to help.
- Focus on the constructive aspects of the feedback and try not to take it personally. Detaching your emotions helps you see the potential for improvement more clearly.
- If something in the feedback is unclear or you need more detail, don't hesitate to ask for clarification.
- If you're unsure about implementing feedback, defer the decision to the build leader or consult with the project's approving moderators for guidance.
By embracing feedback with a receptive and appreciative attitude, we can collectively create an environment that encourages the innovation in quality WesterosCraft has become known for.