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
An URI scheme allows special clickable links to be used to launch an application and pre-configure input fields in accordance to the URI parameters.
The otserv:// URI scheme is currently in effect for tibialoader on otservlist.org.
otland IP changer also supports it, however otland ip changer doesn't seem to fully support the protocol the same way tibialoader does, which is dictated by Xinn/otservlist.org
Current structure:
otserv://ip_domain/port/protocol
On client 11+, port is disregarded, and loginWebService is presumed to be ip_domain/login.php. Gameserver port is then loaded from the json http(s) response.
To determine correct protocol, I suggest:
if protocol / 10 in [valid clients]
else if protocol / 100 in [valid clients]
or
if protocol in [valid clients]
else if protocol * 10 in [valid clients]
depending on how OTU client list is stored.
I would consider overwriting the registry if its already configured for tibialoader/otland ip changer to OTU when program starts. (or during installation, or options button).
Not quite sure how the technical implementation is done.
The text was updated successfully, but these errors were encountered:
An URI scheme allows special clickable links to be used to launch an application and pre-configure input fields in accordance to the URI parameters.
The otserv:// URI scheme is currently in effect for tibialoader on otservlist.org.
otland IP changer also supports it, however otland ip changer doesn't seem to fully support the protocol the same way tibialoader does, which is dictated by Xinn/otservlist.org
https://stackoverflow.com/questions/389204/how-do-i-create-my-own-url-protocol-e-g-so
This is added through the registry.
Registering an Application to a URI Scheme
Current structure:
otserv://ip_domain/port/protocol
On client 11+, port is disregarded, and loginWebService is presumed to be ip_domain/login.php. Gameserver port is then loaded from the json http(s) response.
4 samples from otservlist.org:
client 7.4 = 74
client 7.92 = 792
client 10.98 = 1098
client 12.1 = 121
To determine correct protocol, I suggest:
if
protocol / 10 in [valid clients]
else if
protocol / 100 in [valid clients]
or
if
protocol in [valid clients]
else if
protocol * 10 in [valid clients]
depending on how OTU client list is stored.
I would consider overwriting the registry if its already configured for tibialoader/otland ip changer to OTU when program starts. (or during installation, or options button).
Not quite sure how the technical implementation is done.
The text was updated successfully, but these errors were encountered: