Razor

What works

Razor installs fine.

Requires a 32-bit wine prefix to run, attempting to start it under a 64-bit prefix results in an out-of-memory error.

What does not

Most in-memory communication between Razor and the UO client executable is non-functional.

Razor CAN:
- Update the UO window title bar contents, though Razor's option 'Use smart CPU usage reduction' must be turned off (sometimes) for that to happen consistently.

Razor CANNOT:
- Change the login server address. Razor cannot be told not to attempt this, either. So if you set the address manually via the Login.cfg file in the UO client folder, Razor will still try and fail to modify it in memory, garbling something in the process.

- Strip the client encryption. Razor can be told not to touch the encryption, and if you play with an already decrypted client, you are still unable to log in to any player-run shards because it will still insist on tampering with the login server data.

Workarounds

What was not tested

Any and all functionality available after logging in to the game.

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

Tested with UO client v4.0.11c (Mondain's Legacy), as the very latest official client (v7+) is very unstable under wine, to the point of being unplayable. I believe it was completely re-written after Mythic took over development of the franchise.