Skip to content

Add Steam Captured Activity - #277

Open
gunCannoli wants to merge 1 commit into
SteamClientHomebrew:mainfrom
gunCannoli:add-steam-captured-activity
Open

gunCannoli wants to merge 1 commit into
SteamClientHomebrew:mainfrom
gunCannoli:add-steam-captured-activity

Conversation

@gunCannoli

Copy link
Copy Markdown

Steam Captured Activity

Shows the screenshots and recordings Steam captured in each game's Activity feed, in Steam's own style: one card per day headlined "{your name} captured", as 16:9 cards with clips playable in place, for Steam games and non-Steam shortcuts, on the desktop and in Big Picture. Steam only lists captures in the Activity feed after you upload them to the Steam Community; this plugin shows what is already on your PC. It makes no network requests, and it needs no account or key.

  • Settings: "Steam games support" and "Non-Steam games support" (both on by default).
  • When a screenshot or recording is deleted, its card leaves the feed on the next visit to the game's page (within 5 minutes if the page stays open).
  • It uses Steam's own components for the cards and @steambrew/client components for the settings panel. The backend is a small standard Millennium Lua backend.

How it differs from existing plugins: I found no plugin on the store that puts the user's own captures into the Activity feed (a game's Activity feed otherwise shows only community uploads and Steam events).

Repository: https://github.com/gunCannoli/steam-captured-activity
Version: 0.1.0 (pinned commit 7464fe3)

Screenshots

Captured cards in a non-Steam game's Activity feed

AI disclosure

AI agents were used in this plugin's development, so the generative-AI box below is ticked. I'm a software developer: I set the architecture and the working rules the agents follow, and I review the code and verify its behaviour in the live Steam client. For this plugin that includes the layered design, the architecture decision records, and audits of Steam's internals. I'll maintain the plugin myself and fix it after Steam client updates.

Task Checklist

Developer

  • My plugin complies with the plugin submission guidelines
  • 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.
  • Generative AI was used for most of the plugin's code.

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

  • I use a standard Millennium Lua backend in my plugin.
  • I use custom binaries that or rely on other FOSS projects that aren't written directly using Millennium's Lua 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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant