Crown Profiles

Community Crown profile store for Moonlight V+.

Moonlight V+ reads this repository as a static store. The app downloads index/v1.json, shows the published profiles, then downloads the selected .crown.json bundle from this repository.

Store URL

https://raw.githubusercontent.com/qiin2333/crown-profiles/main/index/v1.json

Repository Layout

index/v1.json                  Generated store index consumed by the app
policy/sensitive_words.txt     Blocked wording list used by local/CI validation
profiles/<game>/<profile>.json Published Crown profile bundles
schemas/                       JSON schema references
tools/generate_store_index.py  Rebuilds the generated store index
tools/validate_store.py        Local/CI validation

Submit a Profile

From Moonlight V+

1. Open Crown Configuration Management.
2. Choose "Publish to Crown Store".
3. Authorize GitHub when prompted.
4. Pick a local Crown profile and fill in the Store listing.
5. Moonlight V+ will fork this repository, commit the profile bundle, then open a pull request from your GitHub account. The store index is generated by this repository after the pull request is merged.

The app asks GitHub for public repository access only so it can create that fork, branch, commit, and pull request. It does not receive direct write access to the main store branch.

Manually

1. Export a Crown share package from Moonlight V+.
2. Add the .crown.json file under profiles/<game>/.
3. Run python tools/validate_store.py.
4. Open a pull request.

Do not edit index/v1.json in profile submissions. It is generated from the profile bundle files by GitHub Actions after merge.

Pull requests are also checked against policy/sensitive_words.txt. If a profile listing or payload contains blocked wording, CI will fail before merge.

If you are submitting from a phone, open an issue with the "Submit Crown Profile" template and attach the exported .crown.json file. A maintainer can move it into profiles/ after validation.

Moonlight V+ should never embed a repository write token. Fully direct in-app publishing must use the user's GitHub authorization and open a pull request from the user's account.