Upcoming QOL Plans
Hello everyone!
This is the first of what we plan to be an ongoing series, where we share the Quality of Life features and content ideas from the Community that we have in the pipeline!
The intention of these blogs going forward is to share what is happening currently. Which QOLs are at the end of their review process.
Review process: The Production team has read the request/suggestion and it has or hasn’t been approved.
These blogs may also include features/requests we are currently not going forward with, whether that is ever, just for now or in a different way to what has been suggested.
There are also some requests that are unsuccessful, but will go back through the review process, if there is an alternative suggestion or just more to discuss. These will not be shared in these blogs.
As there is a backlog, these blogs initially will have a regular release cadence.
But once that has been cleared, we will share them less frequently/consistently and save making a post until there are multiple QoL/feature requests to share at once. So please, be patient and hold off asking when the next blog is coming, if you have not seen one in a little while.
Which is a great segue for..
Housekeeping TLDR;
- Everything shared is a work in progress and subject to change
- Do not comment about other QOLs not mentioned in this blog
- Don’t derail the thread.
- Anything with an Outcome listed as pending/ongoing does not require further community suggestions
Everything we share in these blogs will be a work in progress. Everything is subject to change.
If there are any ETA’s or predicted updates shared, this could change, be delayed, no longer happen at all, move backwards or move forwards!
On the flip side, some things we mention may not even have an ETA or predicted update yet. So, please do not ask; Once we can share that information, we will!
We will be sharing a shortlist in each blog.
Please do not post in these threads to ask or comment on OTHER QOLs/features that are not mentioned.
Comments that derail or are off-topic to the blog itself will be moved into new or existing feedback threads or deleted completely.
For example: “Why are you implementing X! What about B QOL -something something”
We can get into the why of X-QOL being implemented! But we won’t be going into why B-QOL won’t be, if it’s not mentioned in that blog.
If there isn’t a thread already discussing a QOL, please feel free to start one!
In some blogs, we will also call something out as a “Feature”, which differs from Quality of Life requests.
Some examples of what a QOL is versus a Feature:
- QOL Request:
- A task that can be completed in a short period of time
- A change one dev can complete around other tasks
- Works within the existing frame of the game
- Minimal to no other components of the game require an update for it to exist
- Minimal to no changes required to our tools
- A task that can be completed in a short period of time
Example: Adding a pop-up screen to describe a game mode
- Feature:
- Something that takes a number of days or longer to work on.
- Something that requires potentially multiple devs to implement
- A change they might be working on as a primary task
- Something that may require our tools to be updated or whole new tools to be created.
- Something a whole update could be centred around.
- An item that adds a new component to the game, or significantly changes/updates an existing component.
Example: Reworking a gamemode
Each item will be broken down into 3 short sections:
- The issue
- At the core, what is the problem we want to resolve
- The suggestion
- The idea of how this could be resolved
- The outcome
- This can be varied. It could be what is being implemented if it differs from the Suggestion, what are the current blockers/limitations, any ETA’s if we have them.. Etc
If an item has an outcome listed as pending or still in discussion, please do not share further suggestions in this thread.
Everything that has reached this point already has community suggestions included when it starts this whole process.
Anyways, finally, onto our first items!
Guild name changes made in-game
The issue: Players are required to reach out to the support team with a support ticket, everytime a Guild leader wants to change the name of their Guild.
The suggestion: Much like how players can change their own name, add a feature into Guild Admin to allow Guild leaders to change their Guild name without leaving the game.
The outcome: Current ETA is 8.9.
Testing your own teams
The issue: Players cannot easily test out their own Teams. Currently requires setting up team in PvP > Central Spire, then navigating through their own hero menus to fight this specific team.
The suggestion: Creating a space where players can set up and test a team, without needing to go through so many menus.
The outcome: Given the scope of what we have been discussing, this would be a whole feature. We want to create a place where you can easily build a team and then compete against them, so this currently has no ETA, but we wanted to share that it is in the works.
Guild Wars Roster
The issue: This will address a lot of requests all at once.
- It takes a lot of investigation for Guild leaders to see who is and isn’t participating in Guild Wars. Which is most important for Guilds with a Guild Wars participation requirement
- There isn’t one place where players can see everyone in a Guilds score, wins/losses, who hasn’t set a defense team, etc.
The suggestion: Add a menu to Guild Wars called the Guild Roster.
The outcome: Current ETA is 8.9
World Event Scoring displayed in-game
The issue: You do not know the World Event scoring, unless you read the weekly blog, as it’s not displayed in the event.
The suggestion: Update the World Event UI to display the scoring information within the event.
The outcome: Still currently investigating the scope of this. Will share an ETA once we have one.
Tower of Doom map will reveal rooms if cleared by Guild members
The issue: Players use 3rd party community-made tools to track Tower of Doom rooms to help each other within the Guild target rewards. This required players to leave the game to do so.
The suggestion: Update the Map UI to show which rooms have been cleared by another Guild member and the rewards available.
The outcome: Still currently investigating the scope of this. Will share an ETA once we have one.
Improving the Soulforge Mythic & Legendary cycle
The issue: As there are over 200 troops in the Soulforge cycle, it takes months before the cycle clears and then allows new troops to be added to the pool. Only increasing the time it takes for the cycle to complete.
The suggestion: This one had a lot of various suggestions, with the end goal being to just make the Soulforge cycle through faster.
The outcome: Soulforge refreshes every Monday and Thursday, or every 3 days, instead of just at Weekly reset. Currently pending for 8.9, depending on scope.
This will be under review after the change has been made.
And that’s it! A huge first blog, but going forward, they will just be the QoL and Feature list mentioned just above. So, a much lighter read.
We will also have more Community Surveys in future, to continue collating data on released QOLs and features! As well as ones we are investigating for the future.
So, keep an eye out for those, as that data is incredibly important!
It helps me push priority suggestions if I have data to support the feedback, especially as they reach a much wider audience than those who are active on the community forum.
Lastly, please do not make me tap the sign to remind everyone of the housekeeping of these blogs.