Add translated discovery tags and extension families - #1
Draft
Krarilotus wants to merge 3 commits into
Draft
Krarilotus wants to merge 3 commits into
Krarilotus wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: Make this package searchable by translated topics in the proposed launcher tag filter.
The proposed launcher search can use package-owned topic labels. This supplies those labels; it does not fix a gameplay defect.
Changes: Add stable tag IDs and translated labels in the package manifests and locale files. Add family metadata to group related packages; it does not install or activate them together. Fill missing localized descriptions. Proposed versions: ApeX-AI-Behaviour-Applied 1.4.1.
Review / testing: Optional feature proposal; ordinary extension loading does not need these tags. The changed files contain metadata/localization rather than a new game module or framework implementation. The original checks report YAML and locale-key coverage; translations still need human review. Recheck proposed version numbers against current releases before publishing.
Display support: GUI #382 · Store #33. Review the shared format there before asking each package maintainer to adopt it.