You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following .reg file can be used as an example for how URI Handlers can be created in Windows. Replace HKEY_CURRENT_USER with HKEY_LOCAL_MACHINE for machine-wide installations, and absolut executable location with the actual location to the executable.
When launched via a URI, the full URI is passed to the program in the 0th item in argv (specified as %1 in the following file)
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Classes\adastral-osprey]
@="URL:Adastral Launcher (Osprey)"
"URL Protocol"=""
[HKEY_CURRENT_USER\SOFTWARE\Classes\adastral-osprey\DefaultIcon]
@="\"C:\\Windows\\System32\\calc.exe\",1"
[HKEY_CURRENT_USER\SOFTWARE\Classes\adastral-osprey\shell]
[HKEY_CURRENT_USER\SOFTWARE\Classes\adastral-osprey\shell\open]
[HKEY_CURRENT_USER\SOFTWARE\Classes\adastral-osprey\shell\open\command]
@="\"absolute executable location\" \"%1\""
This is (most likely) not all the things that are required, since I'm going through some old projects that used a custom URI provider and this is one out of 3 registry keys added, and the launcher would have to be made a single-instance application and some sort of IPC to make sure that URIs get processed by the application. (I'd be willing to help out with this feature btw)
Just a handler that's of the form
adastral://[run,verify,install]/[game_id]
that allows direct links into Adastral.The text was updated successfully, but these errors were encountered: