Finally it's here. Final changelog: Changes from RC1 to RC2
[Core]
[ADD] UOExt now can read client launch params and use it like IP/Port (I.E: client.exe 127.0.0.1:2593 will force client to connect to this IP/Port. Razor will be overrided).
[ADD] If normal connect won't answer as needed during ...

RC2 is on the test stage...

Changes from RC1 to RC2
[Core]
[ADD] UOExt now can read client launch params and use it like IP/Port (I.E: client.exe 127.0.0.1:2593 will fore client to connect to this IP/Port. Razor will be overrided).
[ADD] If normal connect won't answer as needed during Update ...

Why dangerous? It's fully client side library.

Right now I'm testing it on 6 and 7-th clients. Main answer is: When 0xEF comes. I can add support of previous clients (after 2.0.3, I think... Or I need to add second cypher method and complex version detection), but is it really need?

You can just try. Basic integration is: Handle custom 0xEF packet and send special packet backward... And that's all. This packet will tell UOExt that there is standalone update server and all UOExt-specific work will be done with that server. Standalone server comes with 0.1.0 RC1 version.

UOExt ...

Today I'm proud to represent my new project: UOExt .

Current version is 0.1.0 RC1.

Let me explain what it is..

This tool developing for shard owners, alloing them to ship their code to client, run it and communicate with client and protocol.
Right now it can: Automatically update, download ...