Does this work with Orion Launcher?
With UOSteam there's no way to mitigate or prevent the assistants players have access to, server-side, so I won't allow usage of this launcher.
With ClassicUO, I can't seem to get the github to compile in visual studio so I can't modify the source code, and it's not working with UltimaLive.
With Razor, players cannot modify the size of the game window, so the usefulness is limited solely for players that have smaller monitors and/or don't care.
With OrionLauncher though, there's generated packets included in the software that controls all aspects of what players can use.
This software will deploy anything that you keep in the server-side deployment root directory; you could even deploy a completely different game if you wished.
Unfortunately this software doesn't have a launch icon or detection set up for Orion, which is something I can look at adding support for.
The IPL does not handle client validation or verification, it has nothing to do with logging in once a player has clicked the relative launch icon for the client or assistant they want to start up.
If you wish to restrict login to specific clients, it must be done outside the bounds of this software.
UOSteam and Razor are assistants that hook the main client.exe and run that, IIRC you can adjust the screen size with Razor if you get an updated version like Razor Enhanced.
ClassicUO should have support for UltimaLive built-in and they recently fixed VS based compiling.
Orion is more like ClassicUO since it's an entirely separate client; the OrionLauncher can likely be left out of your deployment just like the CUO launcher isn't required.
If you have any questions, don't hesitate to ask here (or DM me on Discord)