Hey everyone,
Following great engagement and feedback after our category enforcement tests and soft launch in February and March, we wanted to kick off what will be a monthly update cadence for competition and racing.
The goal is to provide you with insight as to what the team responsible for competition and racing has delivered, what’s currently being worked on, and what’s on deck in the coming months.
While this is not an exhaustive list, it is representative of all the major bodies of work the team is focused on.
This will follow the same format as the Clubs posts that have been going for some time. You can find an example of that here.
Finally, we welcome your feedback on this post! To make sure we capture it all in this moment in time, we will be auto-closing the post 7 days from the original post date.
Let’s get into it!
- What can you expect in the next release?
- What is Zwift working on now?
- What is the status of feedback the community provided?
What can you expect from the next release?
The next release - going out May 2022 as v 1.25 - will include:
- Pace Partners changes*
*Note: These changes will be announced in more detail with the next batch of release notes. You can find all release notes here.
What is Zwift working on now?
- Category Enforcement Improvements - clearer UI, friendlier UX, women-only categories, and an optional E pen for Zwifters with no data in the last 60 days
- Event Hardware Minimum Requirements - the ability to race against other Zwifters that are on similar hardware: power meters with power meters and classic trainers with classic trainers.
- Individual and Team Time Trial Improvements - Improved TT user experience, including a new paddock experience, and more route variety
What is the status of feedback the community provided?
- Discovery : Early in the process
- Backlog : It’s on our radar and some work has been done
- In Progress : It’s actively being worked on
- Done : Released
Community Feedback & Status
Improving Fairness in Competition
- Category Enforcement (aka pen restriction) - Done
- Category Enforcement more accommodating for lighter riders - Done
- Category Enforcement for community race organizers - Done
- Removal of Anti-sandbagging events from race calendar - Done
- Segment Leaderboard technical improvements - Done
- Improved time gaps logic in events - Done
- Hardware Restriction - In Progress
- Better UI for Category Enforced races - In Progress
- Women’s specific power curve for Category Enforced events - In Progress
- Extending all leaderboard PR data beyond 30 days - Discovery
- Category Enforcement as an option in clubs - Backlog
- Custom category limits when using Category Enforcement - Backlog
AI Tech
- Improved backend Pace Partners scheduling - Done
- Expand active Pace Partners: more worlds, test - Done
- Extend pedal assist when joining a Pace Partner - Done (1.25 release)
- Pace Partners as event leaders - In Progress
- Pace Partners Dynamic Paces - In Progress
- Pace Partners expanded route capability - In Progress
- Expand Pace Partners: more pace capability in single world - In Progress
- Expand Pace Partners: incorporate previous tests to global schedule - In Progress
- More nuance and dynamism with Pace Partner behavior - Backlog
Bugs
A note for bugs: this update is from one team’s perspective, and will not be representative of everything affecting events, segment results, etc. This team’s bodies of work focus most directly on competitive events, Pace Partners, and the future of competition at Zwift.
- ZwiftPower: rider search fix - Done
- ZwiftPower: “friends” list on riders tab fix - Done
- ZwiftPower: SSO bugs - Done
- ZwiftPower: missing events - Done
- ZwiftPower: when re-activating a ZP account after deletion, account is missing - Done
- ZwiftPower: age of U23 riders not displaying correctly on profile - Backlog
- ZwiftPower: using “days to show” in filters for series breaks - Backlog
- ZwiftPower: users with exceptional height are incorrectly DQd - Backlog
- ZwiftPower: heart rate can show in profile page results but not specific race - Backlog