Glorious Alpha Two Testers!
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
đź“ť Help shape Ashes of Creation | A Feedback Guide & Template
Glorious Ashes of Creation community,
As we continue improving and working on Alpha Two, your feedback plays a crucial role in helping the team make informed decisions. This post is a guide and template to ensure your input is as impactful as possible for the team and easy to discuss with other players.
If you have bugs to report, please use the Bug Reporting Template, and be sure to post them in the Bug Reporting category of the forums.
Subject & Title - A Brief Summary of Your Feedback
Start with a short, clear title that sums up your feedback. This makes it easy to find and understand your thoughts.
Example:
“Nighttime is too dark and the skybox is hard to see”
Describe the Problem
Provide a concise description of what you’d like to highlight. It may help to focus on the who, what, when, where, why, and how, of what you want to discuss.
When giving feedback, it’s most helpful to focus on describing the problem—what you do and don’t like, and why—rather than emphasizing specific solutions. This helps us better understand the issue and explore possible solutions.
Example:
“I feel that the darkness during nighttime feels too extreme, and the night skybox is not very visible. This makes it difficult to navigate, enjoy the scenery, or identify threats or POIs.”
Make It Easy for Others to Join the Discussion
When giving feedback, think about how others might want to weigh in. Make your post easy to follow by keeping it clear, structured, and focused. Avoid long walls of text and use proper punctuation to the best of your ability. This helps both developers and fellow players understand and add to the conversation.
Example:
“[At night, it’s almost pitch-black, and the stars are hard to see.] Has anyone else noticed this? Do you think the skybox should be more visible?”
Set The Tone
Avoid venting frustrations or being overly negative. Constructive criticism is far more effective than venting or purely negative comments. Highlighting things you like can also help us capture the fun!
Example:
Instead of: “Night lighting is awful and I hate it 💩”
Try: “The nighttime environment is too dark, and it’s hard to enjoy the scenery. I feel that brighter stars or different light balances might make it more immersive and I’d enjoy that more. The skybox during the day is awesome and captures daytime so well! I’d love it if nighttime did that too.”
By following this structure, your feedback will be easier to read, understand, and contribute to!
Thanks for helping build the world of Verra!
Here is a brief example of this guide put to use
As we continue improving and working on Alpha Two, your feedback plays a crucial role in helping the team make informed decisions. This post is a guide and template to ensure your input is as impactful as possible for the team and easy to discuss with other players.
If you have bugs to report, please use the Bug Reporting Template, and be sure to post them in the Bug Reporting category of the forums.
Subject & Title - A Brief Summary of Your Feedback
Start with a short, clear title that sums up your feedback. This makes it easy to find and understand your thoughts.
Example:
“Nighttime is too dark and the skybox is hard to see”
Describe the Problem
Provide a concise description of what you’d like to highlight. It may help to focus on the who, what, when, where, why, and how, of what you want to discuss.
- What the problem is.
- Why does it matter?
- How does it affects your gameplay?
When giving feedback, it’s most helpful to focus on describing the problem—what you do and don’t like, and why—rather than emphasizing specific solutions. This helps us better understand the issue and explore possible solutions.
Example:
“I feel that the darkness during nighttime feels too extreme, and the night skybox is not very visible. This makes it difficult to navigate, enjoy the scenery, or identify threats or POIs.”
Make It Easy for Others to Join the Discussion
When giving feedback, think about how others might want to weigh in. Make your post easy to follow by keeping it clear, structured, and focused. Avoid long walls of text and use proper punctuation to the best of your ability. This helps both developers and fellow players understand and add to the conversation.
Example:
“[At night, it’s almost pitch-black, and the stars are hard to see.] Has anyone else noticed this? Do you think the skybox should be more visible?”
Set The Tone
Avoid venting frustrations or being overly negative. Constructive criticism is far more effective than venting or purely negative comments. Highlighting things you like can also help us capture the fun!
Example:
Instead of: “Night lighting is awful and I hate it 💩”
Try: “The nighttime environment is too dark, and it’s hard to enjoy the scenery. I feel that brighter stars or different light balances might make it more immersive and I’d enjoy that more. The skybox during the day is awesome and captures daytime so well! I’d love it if nighttime did that too.”
By following this structure, your feedback will be easier to read, understand, and contribute to!
Thanks for helping build the world of Verra!
Here is a brief example of this guide put to use
2
This discussion has been closed.