Request for Shareable Per-Game Profiles #111
Labels
No labels
???
bug
docs
enhancement
help wanted
indev
question
research
tbr
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: NG-SD-Plugins/PowerTools#111
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Please confirm
Describe what you'd like to be able to do
I am interested in the implementation of a functionality enabling the sharing and retrieval of community profiles specific to each Game.
The current tool possesses a user-friendly interface that allows for straightforward customization of settings. However, similar to the concept of controller layouts, it would be highly desirable to incorporate the capability of sharing and downloading settings from other users.
While I remain uncertain about the feasibility of this proposal, I firmly believe that integrating such a feature would significantly enhance the accessibility and usability of the tool, particularly for novice users.
Describe alternatives you've considered
In the event that achieving the same level of streamlined functionality as Controller Layouts proves to be unattainable, an alternative solution could involve the generation of a shareable file format that can be imported into the existing tools. While this approach may not offer the same level of convenience as an integrated search feature within the tool interface, it would still serve as a viable means for users to exchange and utilize profiles.
Anything else?
No response
I do agree this would be nice. The alternative is actually already achievable since the config files are stored in a well-documented and user-writeable location.
Unfortunately creating a web service for sharing requires some expertise that I do not have, so it's unlikely to happen soon if at all.
Hm, maybe then a simple "Import Settings" in the UI itself would be sufficient? Or is exploring files from the menu in Game Mode too much a hassle?
@NGnius I came across this issue by chance, my deck is coming soon, I like the idea to save time (btw it involves a CRUD of profiles per game since there will be mutiple profiles).
I can help you create the web service but I'm not sure if that's necessary. I don't know how steamOS works, in particular, is there a unique ID for each game? If so, why not create a new repo containing a folder for each ID and inside the profiles in JSON format?
I guess I never replied to this, sorry.
Decky has a file picker, but I don't see why that would be worth using over Dolphin in Desktop mode. Dolphin is already like 10 years ahead of Windows Explorer so it's doesn't get much better than that.
But to the respond to the ping:
Any help would be appreciated, but the actual part that I need help with is the UI. The work is twofold: a SteamOS Gamemode UI (Decky does this by injecting React JS code) as well as a web-facing UI (preferably not JS -- Rust has a few wasm frameworks which are a lot less hassle).
Each game has two unique IDs (game ID and app ID); either is fine for games on the Steam store. Non-steam games also have the same two unique ID system, but I'm pretty sure they're not consistent between Steam clients so that can't be relied on. It'll probably be best to use the game's title to group profiles for non-Steam games, which is definitely a bad solution, but probably the least bad solution. If users can search by profile name and game name (not necessarily at the same time), it'll be actually good. I've explored the back-end side of this idea before, so I'm confident I can do it and that it'll be pretty simple.
GitHub is not a database. I'd also rather self-host it (I've got the hardware) and not give MS more AI training data or internet traffic than they already have. I've already transitioned most of my smaller git projects away and the rest of my projects will be soon to follow.
508c6ceb9e
622f161560
2ec89ee1eb
9dedebb234