Skip to content

feat: added the steam-protondb-plugin#144

Closed
cecilia-sanare wants to merge 1 commit intoSteamClientHomebrew:mainfrom
cecilia-sanare:steam-protondb-plugin
Closed

feat: added the steam-protondb-plugin#144
cecilia-sanare wants to merge 1 commit intoSteamClientHomebrew:mainfrom
cecilia-sanare:steam-protondb-plugin

Conversation

@cecilia-sanare
Copy link
Copy Markdown

@cecilia-sanare cecilia-sanare commented Mar 15, 2026

ProtonDB Badges

Adds ProtonDB badges to the individual Store and Library pages!

Store Library
Badge shown on the store page for a game Badge shown on the library page for a game

Task Checklist

Developer

  • I am the original author or an authorized maintainer of this plugin.
  • I have complied with all license requirements for the libraries used, including providing appropriate notices where necessary.
  • My plugin is fully open source and does not depend on any external paid services, except for widely trusted and well-known platforms. Additionally, neither I nor anyone associated with me profits from any such services.

Plugin Functionality

  • I have tested the plugin on both the Stable and Beta Steam update channels.
  • My plugin is unique, or provides additional or alternative functionality to plugins already on the store.

Backend Configuration

  • Yes: I use a standard Millennium lua backend in my plugin.
  • No: I use custom binaries that or rely on other FOSS projects that aren't written directly using Millennium's python backend.

Community Contribution

  • I have tested and left feedback on two other plugin pull requests.
  • I have added links to those feedback comments in this PR.

Testing Instructions

  • Verified by a third party on Steam Client Stable.
  • Verified by a third party on Steam Client Beta.

@cecilia-sanare cecilia-sanare marked this pull request as ready for review March 15, 2026 23:19
@shdwmtr
Copy link
Copy Markdown
Member

shdwmtr commented Mar 16, 2026

Doesn't this do the same thing? (I don't know much about proton-db, so I could be wrong)

image image

@cecilia-sanare
Copy link
Copy Markdown
Author

cecilia-sanare commented Mar 16, 2026

The primary difference is where the information comes from actually!

The "Steam Deck Compatibility" is coming from Valve themselves
whereas the ProtonDB information is fed by community reports!

This leads to ProtonDB being more up to date then the Steam Deck Compatibility information.
In addition ProtonDB is just generally incredibly useful on linux since it'll also tend to have workarounds even for games that aren't as well supported.

@shdwmtr
Copy link
Copy Markdown
Member

shdwmtr commented Mar 17, 2026

Everything sounds good then! I'll just need a third party to test and report back here. You can likely find someone on our discord server.

@cecilia-sanare
Copy link
Copy Markdown
Author

I really appreciate your help!

I'll shoot a message in the plugin-and-theme-dev channel tonight when I have a bit more time unless someone happens to stumble across it first and validate it while I'm working.

@cecilia-sanare cecilia-sanare force-pushed the steam-protondb-plugin branch from e2f4e98 to 392a8f6 Compare March 17, 2026 22:02
@cecilia-sanare cecilia-sanare force-pushed the steam-protondb-plugin branch from 392a8f6 to 2d95341 Compare March 22, 2026 04:03
@shdwmtr
Copy link
Copy Markdown
Member

shdwmtr commented Mar 22, 2026

We strictly depend on GitHub.com in hundreds of places across Millennium, the website, the plugin database etc. It's understandable if you don't like GitHub for whatever reason, but I literally can't merge this if its not on GitHub!

@shdwmtr shdwmtr mentioned this pull request Mar 22, 2026
@cecilia-sanare
Copy link
Copy Markdown
Author

Honestly I was already debating on not including my plugin as part of the database anyways. This is mostly because I've done work for other projects similar to this one (runelite, curseforge, and dalamud to name a few) where deploying an update is always a manual process. I inevitably get burned out by the process when I just want to focus on writing cool shit that can benefit people.

I prefer to automate my deployments so I don't have to deal with that busy work and to reduce the number of errors I could possibly introduce into the process.

Regardless I totally get why the PluginDatabase exists (discoverability) and why y'all need to review changes before (effectively) officially endorsing them, but I'm going to take a lesson from my own past and close this PR.

I wish y'all the best and will still be around to contribute changes here and there on the various projects~ ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants