Good feedback describes an observation and gives the creator a choice. It does not need to be flattering, but it should be specific enough to use.
Start with the intended result
Ask what the build is trying to achieve: a dramatic entrance, a comfortable home or a readable game arena. A feature that seems unusual may be deliberate. Evaluate the work against its purpose before suggesting a different style.
Describe what you see
“The entrance blends into the wall from the path” is more useful than “the entrance is bad.” Explain where you were looking and what made the important element hard to recognise. If you suggest a change, connect it to that observation.
Offer one or two practical options
A contrasting frame, clearer lighting or a simpler path might address the same problem. Present these as options, not mandatory corrections. The creator may know a material or gameplay constraint that is not visible in the screenshot.
Keep taste and function separate
You can dislike a colour while acknowledging that it makes navigation clear. Likewise, an attractive detail can still obscure a sign. State which kind of judgment you are making.
End with the most useful next experiment. A small revision that can be compared with the original is usually easier to act on than a request to rebuild everything.
Related reading
Tell the story of a build with five useful views
https://panel.zeismoplay.com/community/topic/29
Compare two design ideas without relying on popularity alone
https://panel.zeismoplay.com/community/topic/23
0 thanks