"Launch as <status>" - Githubissues

Vencord / plugin-requests

Vencord plugin requests. Open the link below to create a request

https://github.com/Vencord/plugin-requests/issues/new?template=request.yml

26 stars 3 forks source link

"Launch as <status>" #918

Open Vap0r1ze opened 1 month ago

Vap0r1ze commented 1 month ago

Plugin Description

Would add a CLI flag for specifying the status to send in your initial IDENTIFY gateway packet's presence property.

If you got a DM from your boss or something and wanted to open Discord without them knowing: this would let you do that with something like --initial-status=invisible so you don't have to flash as "online" to set yourself as invisible.

Some QoL settings could be added like creating shortcut files (eg: .lnk or .desktop) for easy access to launching as a certain status, or on Windows adding a Task to the Discord app like VSCode has in the screenshot below for specific statuses.

Discord_mABTBDBDG0

Existing Plugin for other mod

No response

Request Agreement

[X] I read the above and made sure my plugin is possible and allowed
[X] I checked the existing plugins and made sure my plugin doesn't already exist
[X] I searched the existing issues and made sure a similar request doesn't already exist

Vap0r1ze commented 1 month ago

FYI I plan on making this into a PR, just opened it to track the idea

Scyye commented 1 month ago

Seems very niche & why/how would a plugin add a CLI flag?

Vap0r1ze commented 1 month ago

Why: CLI flags makes it very easy for user to communicate a value to a plugin per-launch. Honestly thinking about it, this might be better as a built-in Vencord feature for creating launchable profiles of settings-overrides. How: DiscordNative.processUtils.getMainArgvSync()

Also, the CLI part is mainly just so theres a common interface everwhere. More user-friendly options for making things launchable can be done like I showed in the screenshot on Windows and Linux .desktop

Sqaaakoi commented 1 month ago

Why: CLI flags makes it very easy for user to communicate a value to a plugin per-launch. Honestly thinking about it, this might be better as a built-in Vencord feature for creating launchable profiles of settings-overrides. How: DiscordNative.processUtils.getMainArgvSync()

Also, the CLI part is mainly just so theres a common interface everwhere. More user-friendly options for making things launchable can be done like I showed in the screenshot on Windows and Linux .desktop

I would honestly use this, however please consider how this would work on Vesktop under Linux due to a few complications

This would require considering if the desktop file is a symlink and converting it to a regular file automatically (because there is a decent chance it is a symlink due to Flatpak) if it is something that needs to be regularly updated by Vencord itself
Vesktop needs to have a system to delegate in-app actions first (shortcuts triggered by command line), and a standard to provide argv to the renderer