Guide To Feedback
What is feedback?
- Feedback is information provided about a product or action, or in our case, about a map or code change.
- Feedback should be able to be used to improve that map or code project.
- Good feedback is critical for projects to be successful.
How do I give effective feedback?
- Feedback can be better communicated if you start with a positive about the project, before providing your negatives. "While I enjoy this about the project, I think this other thing would be better if-" Sounds much better than "I think this other thing would be better if-"
- Feedback should be something a contributor can act on. "I do not like this" or "This is shit" will likely be ignored because it's not something they can change about the project.
- Focus on the content of what you're giving feedback to, not the person behind the content. Personal attacks will get your feedback ignored, even if you're correct about something.
- Be realistic with your expectations, expect your feedback to improve or alter the project at best, not to entirely change it or shut it down entirely.
- Use "I" statements to keep the feedback relevant to your own experiences. Examples include "I enjoy this because-" or "I think this could be better if-"
- Place feedback where the developer behind a project is likely to see it. Links to these locations are below.
Where do I send feedback?
Mapping Projects:
In the Pull Request of the relevant project
On the forums, on a map specific thread.
On the TGstation discord, underneath player-dev-projects
Coding Projects:
In the Pull Request of the relevant project
Alternatively here, if it's a balance PR
On the forums, on a code specific discussion thread
On the TGstation discord, underneath player-dev-projects
Spriting Projects:
In the Pull Request of the relevant project
On the forums, on a sprite specific thread.
On the TGstation discord, underneath player-dev-projects