Known limitations

EasyUO Reforged is a working, actively tested port, not a finished release. It is based on the last public EasyUO source, which its author described as deprecated, so some features may be missing.

What is verified

The interpreter core, the client data tables and the other logic that does not need a game client are covered by automated tests. Anything that needs a running client is verified by hand, and only as far as testing has reached. Confirmed against a live client so far:

• Detecting and attaching to a running client.
• Script execution: the interpreter, variables, flow control.
• FindItem and the related item commands.
• The variable inspector and VarDump.
• menu windows of the EasyUO 1.5 MENU system: text, buttons, checkboxes, edit fields and images.
• The editor.

Treat anything not listed as unverified, and keep the original EasyUO next to it if you rely on EasyUO for anything important, until you have checked that the scripts and features you need work.

Known gaps

• Client versions. EasyUO Reforged knows the classic client (client.exe) from 2.0.0 up to 7.0.117.1, and two builds of client_beta.exe (7.0.117.1 and 7.0.117.31). A newer client needs its memory offsets added first; see Add a new client.
• Path knows the map files everywhere, but player houses, items players placed, doors and creatures only where your client holds them, around the character. A long route can lead into a house farther away; the walker goes round it once it gets near.
  • It reads the walls and floors of player houses on client.exe 7.0.117.1 and client_beta.exe 7.0.117.31, within about 18 tiles of the character, where the client keeps them. Another build gets this when its signature scan finds where that build keeps them. Where it can’t, the walker learns a house from the client itself (path check) once it is within 12 tiles: a route planned from farther away can still lead toward it.
  • A tile the client hasn’t loaded reads as refused to path check, which is why the walker only asks about the next 12 tiles.
  • The walker doesn’t go into player houses unless told to (path set doors all). Inside a house, the server can refuse tiles the client shows as free. On a build where it can’t read house pieces, it can’t tell a house’s door from any other door, but it learns the floor behind it from the client once the character is within 12 tiles, so routes still go round the house.
  • A link to another facet (a moongate) is not followed: the walk stops there.
  • Client mode (path set mode client) is not the default: on client_beta.exe the client’s own walk keeps ending early or taking its own way, and once left #CharPosX a few tiles off until the next login. There, path stop also can’t stop the client’s walk to the last point it was sent to.
  • Walking has been checked by hand mostly on client_beta.exe. On client.exe: path find, path can, path check, and one walk round a player house.
  • Whether the character walks or runs is up to the client: it runs while Always Run is on, and also whenever your mouse pointer rests away from the character. It reads the real pointer itself, so a script can only steer that by moving your mouse (see Running).
• #MountID, #MountType and #FindLayer read the equip layer where client.exe 7.0.117.1 and 7.0.108.0 and client_beta.exe keep it (read from their code; checked live on client.exe 7.0.117.1 and client_beta.exe 7.0.117.31). On older clients they are unverified.
• Symbol fonts in menus. A menu text, button or checkbox using a symbol font such as Wingdings only shows the intended glyphs if that exact font is installed. Otherwise Windows substitutes another font, as the original did.
• menu Image File reliably loads BMP, PNG, JPEG and GIF. Older formats the original accepted (WMF, EMF, ICO) may not work.
• The MENU Designer reads only the menu lines of a script, and leaves out those with variables and what a running script reads; it designs for the 1.6 MENU system only. See its Limitations.
• EasyUO 1.6’s menu. The 1.6 MENU logic is checked automatically against what EasyUO 1.6.0.337 did in 23 recorded test scripts, and by hand in the editor with test scripts and an example from the ScriptUO tutorial on the 1.6 menu. It has not yet been tried with real 1.6 scripts that play the game.
  • A script runs under one MENU system from start to end, with the files it calls. Reforged picks it from the script’s text when it starts: a 1.6 sub-command that only a variable or a called file supplies is not seen, unless the script sets menu Reforge Mode (or, for called files, menu Reforge IncludeCall).
  • Where EasyUO 1.6 crashed or wrote into the wrong control, Reforged does nothing instead: menu Image drawing commands on a control that is not an image, and menu Show, menu Hide or menu Window after the name form0 was given to another control. It also never moves a control into itself or into one of its own children, and menu Activate skips a control that cannot take the focus.
  • A menu Panel created with a negative size reads back 0, not the number given.
  • menu Image File draws the whole picture; EasyUO 1.6 lost a bitmap’s last column.
  • While a script rebuilds a menu window that is shown, the 1.5 logic holds back repainting until it is done; the 1.6 logic does not, so the window may flicker.
• 64-bit Windows only. EasyUO Reforged itself is 64-bit; it still drives the usual 32-bit UO client.
• uo.dll, the API for external programs, has only been tested by a small Python script (ctypes) on client.exe 7.0.117.1. It selected the client, read variables, and planned and checked with the GetPath, PathCan and PathCheck methods. The rest of its methods have not been tried from an external program.
• EUOUpdater, the tool for new client versions, has had only light testing.

Expect bugs in less common commands and menu features, and please report them.