Problem
Users often struggle to determine which Beat Saber version they should install.
The currently recommended version may be difficult to find when it belongs to a previous year, while other versions that are still relevant for modding are only visible inside their respective yearly tabs.
As a result, users may:
- Choose an arbitrary moddable version with a limited or outdated modding ecosystem.
- Assume that the latest moddable version is always the best choice.
- Miss the recommended version entirely.
- Ask the community which version they should use.
- Start using a deprecated version before noticing the warning displayed after creating the instance.
BSManager currently distinguishes the recommended version, but it does not provide a curated list of other versions that are still considered suitable for modding.
Solution
Add a new Suggested Versions section alongside the existing year tabs.
This section would display a curated list of Beat Saber versions that are still considered relevant for modding. The existing recommended version would remain unique and would be displayed as the recommended choice among the suggested versions.
The distinction would be:
- Suggested versions: versions that are still relevant for modding and have a sufficiently active mod ecosystem.
- Recommended version: the suggested version considered the most suitable for most users, particularly due to compatibility with popular mods.
The version metadata JSON should receive an additional boolean field for each version, for example:
{
"version": "1.44.0",
"suggested": true
}
This avoids changing the overall JSON structure by introducing a separate array and keeps the metadata directly associated with each version.
The suggested-version list would be maintained manually in the same data source currently used for the recommended flag. It would not depend on the BeatMods API.
Alternative Solution
No response
Operating System
None
Additional Context
This proposal follows the discussion from the existing community feature request about helping users choose an appropriate Beat Saber version.
The original proposal suggested showing all moddable and non-deprecated versions. After discussion, a smaller curated list of suggested versions, with one clearly identified recommended version, appeared to be more useful and less likely to imply that every old moddable version is still equally suitable.
The implementation approach was also discussed with a BSManager owner. The agreed direction is:
- Create a Suggested Versions section.
- Keep a single recommended version among the suggested versions.
- Add a
suggested field directly to each relevant version in the existing JSON.
- Do not use the BeatMods API for this metadata.
Problem
Users often struggle to determine which Beat Saber version they should install.
The currently recommended version may be difficult to find when it belongs to a previous year, while other versions that are still relevant for modding are only visible inside their respective yearly tabs.
As a result, users may:
BSManager currently distinguishes the recommended version, but it does not provide a curated list of other versions that are still considered suitable for modding.
Solution
Add a new Suggested Versions section alongside the existing year tabs.
This section would display a curated list of Beat Saber versions that are still considered relevant for modding. The existing recommended version would remain unique and would be displayed as the recommended choice among the suggested versions.
The distinction would be:
The version metadata JSON should receive an additional boolean field for each version, for example:
{ "version": "1.44.0", "suggested": true }This avoids changing the overall JSON structure by introducing a separate array and keeps the metadata directly associated with each version.
The suggested-version list would be maintained manually in the same data source currently used for the recommended flag. It would not depend on the BeatMods API.
Alternative Solution
No response
Operating System
None
Additional Context
This proposal follows the discussion from the existing community feature request about helping users choose an appropriate Beat Saber version.
The original proposal suggested showing all moddable and non-deprecated versions. After discussion, a smaller curated list of suggested versions, with one clearly identified recommended version, appeared to be more useful and less likely to imply that every old moddable version is still equally suitable.
The implementation approach was also discussed with a BSManager owner. The agreed direction is:
suggestedfield directly to each relevant version in the existing JSON.