@Fubarberry I've been using a hack to use Decky Loader on Windows and non-Deck Linux, and at the very least it allows me to use themes and add info to the interface. I wonder if Decky Loader 3 has official support for either of these.
Steam Deck
A place to discuss and support all things Steam Deck.
Replacement for r/steamdeck_linux.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to the Steam Deck in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
This is the best summary I could come up with:
The first pre-release is now available for testing, allowing you to give feedback before the final 3.0 release.
Naturally, if you don't want to deal with any breakage, you should wait for the the main 3.0 release.
Along with fixing the newest break in the steam beta, we're proud to announce we're releasing the first prerelease of Decky Loader 3.0, the websocket rewrite!
For users, it means a hopefully more stable experience with better error handling, as well as more in-depth progress indication in Decky and its plugins.
It's also allowed us to fix a bug where Decky would sometimes not start without an internet connection.
For plugin developers, it means a significantly easier to use API (it is now also asynchronous) and an easy way to do backend -> frontend communication.
The original article contains 209 words, the summary contains 132 words. Saved 37%. I'm a bot and I'm open source!