Add SteamInputDB-Buddy

[Alia5]

Add SteamInputDB-Buddy to Plugin Store

SteamInputDB-Buddy is the official buddy-app for SteamInputDB
It provides direct integration into the Steam client, allowing users to easily access and manage their Steam Input configurations.

The Decky-Plugin mainly serves as an alternative installation method of the SteamInputDB-Buddy-App.

More detailed descriptions and (limited, at the time of writing) screenshots can be found here:

• What is SteamInputDB?
  Read the FAQ
• You can read more about SteamInputDB-Buddy specifically and find limited (at the time of writing) screenshots here

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.

Plugin

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
  I do not (and never will) run SteamOS myself on my Deck

• I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

• Yes: I am using a custom backend other than Python.
• No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• Yes: I am using a custom binary that has all of it's dependencies statically linked.

Community

• [1/2] I have tested and left feedback on two other pull requests for new or updating plugins.
• [1/2] I have commented links to my testing report in this PR.
  • Add Decky Proton Pulse to Plugin Store #1020 (comment)
  • [2/2] No other Plugins that currently have PR interest me in any way. ¯_(ツ)_/¯

Testing

• Tested by a third party on SteamOS Stable or Beta update channel.

[github-actions]

Issues Found

• Both testing boxes are present in your description. Please remove 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. ❤️

[Copilot]

Pull request overview

Adds the SteamInputDB-Buddy plugin to the Decky plugin database by registering it as a git submodule so it can be included in the Plugin Store submission flow.

Changes:

• Register new submodule plugins/SteamInputDB-Buddy
• Point submodule source to https://github.com/Alia5/steaminputdb.com

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Alia5]

Both testing boxes are present in your description. Please remove one of them per the Markdown comment above the testing section.

Removed one of them

[EMERALD0874]

Hi, multiple issues that I'd like to start with:

• Your LICENSE is invalid. Please add the Decky plugin template's license to the bottom of your own. This is a requirement regardless of whether or not your plugin is on the store, as it is a derivative of our plugin template.
• Your submodule appears to be a repo with multiple codebases inside of it, so our pipelines will attempt to build everything as a single plugin. Please move your plugin to its own repository and add that as a submodule.
• Please elaborate on why your plugin needs the Steam beta for full functionality.
• Regardless of whether or not you're interested in running SteamOS on your devices, someone needs to do basic testing and say the plugin basics work on their SteamOS device before we proceed. Please find a tester either within your community or our own.

[Alia5]

Your LICENSE is invalid. Please add the Decky plugin template's license to the bottom of your own. This is a requirement regardless of whether or not your plugin is on the store, as it is a derivative of our plugin template.

Whoops! Sorry about that.

• I added a secondary file containing your license and attribution, meeting the license requirements in the main repo
• My pipeline concatenates both files into a single LICENSE.txt on the orphaned buddy-decky-plugin-branch (the one added as submodule)
  The third-party-notices file is addtionally present.

Please elaborate on why your plugin needs the Steam beta for full functionality.

The plugin itself does not, SteamInputDB-Buddy itself does (and only for full functionality; it did work on the stable Steam client in principle).
(Though I admit the wording/phrasing here might be pedantic)

Some of the JS injected into Steams SharedJSContext was not compatible with the stable version of the Steam Client.
This requirement has now been lifted.

Regardless of whether or not you're interested in running SteamOS on your devices, someone needs to do basic testing and say the plugin basics work on their SteamOS device before we proceed. Please find a tester either within your community or our own.

No worries...
I was just explaining why I haven't and will not be able to tick the checkbox when filling out the template.

[mdeguzis]

Does this simply open up a webpage to steam input db? Making sure I am not missing the scope of the plugin.

[Alia5]

Does this simply open up a webpage to steam input db? Making sure I am not missing the scope of the plugin.

It does add a button that opens the webpage, but it does a few more things:

• When SteamInputDB detects a running buddy-app it replaces the steam://-protocol link to apply configs with a custom dialog that is deeper integrated into Steam
  
• The controller-filters in the Layout/config search are pre-filtered to actually connected controller types, instead of showing the full cluttered list
  

You can read more here or here, in the announcement post

Note that the latter two points take effect regardless if the site was opened from the added buttons on Steam or not.
Switch to desktop-mode and open up any old browser?
Still have site integration into Steam

As we speak, I'm also working on making the site gamepad navigable from Steam BPM
Which for Steam Controllers (that extends to the Decks controller) is a tad more involved than utilizing the browsers gamepad APIs on the site itself, so it really needs an addon / Buddy-App as well... -.-