Add BC250 Toolkit plugin

[Necrosiak]

Add BC250 Toolkit to Plugin Store

A DeckyLoader plugin for the ASRock BC-250 (AMD Ryzen Embedded V2000 / Cyan Skillfish) running Bazzite or SteamOS Linux.

This is a niche hardware device with no existing Decky plugin. The plugin addresses specific BC-250 limitations (live CU management, community game database, hardware monitoring).

Features:

• Games Tab — Community database of optimized launch options. Detects the active game, displays recommended Proton version and launch options, applies in one click via Python backend (VDF write to config.vdf / localconfig.vdf)
• CU Tab — Live Compute Units readout via GPU SPI registers (umr). 4 profiles: 24 CU (stock), 32 CU, 36 CU, 40 CU. Save-to-boot via systemd service. Auto-installs umr via rpm-ostree if not present
• System Tab — Real-time CPU/GPU temperatures, scx_lavd / tuned / gamemode status
• Settings Tab — Auto-apply toggle, DB refresh from GitHub

Interface available in 9 languages (EN, FR, DE, ES, IT, PT, NL, PL, RU) — auto-detected from Steam language.

Screenshots: https://github.com/Necrosiak/bc250-toolkit-decky/tree/main/assets/screenshots

Task Checklist

Developer

• I am the original author or an authorized maintainer of this plugin.
• I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.
• Generative AI was NOT used to write a majority of the code I am submitting.

Plugin

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

• No: I am using a custom backend other than Python.
• Yes: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked. (umr — installed via rpm-ostree, not bundled)
• No: I am using a custom binary that has all of it's dependencies statically linked.

Community

• I have tested and left feedback on two other pull requests for new or updating plugins.
• I have commented links to my testing report in this PR.

Testing

• Tested by a third party on SteamOS Preview update channel.

[github-actions]

Issues Found

• Neither testing box is present in your description. Please include one of them per the Markdown comment above the testing section.

Next Steps

1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

[Necrosiak]

Updated the PR description to follow the plugin_addition.md template. Added Task Checklist and Testing section (Preview channel — plugin uses umr, a 3rd party FOSS tool installed via rpm-ostree).

[github-actions]

This pull request is stale as no updates or testing reports have been posted within the last 7 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

[github-actions]

Your pull request has been closed for being stale. If you want to resubmit a plugin pull request, please ensure you have a tester for your plugin and have resolved all issues discussed.