Recently returned to UO after taking a break in ‘14. Back then I had no issue setting a macro to select the nearest hostile then attack it. Today this same macro crashes the client. I can do without the macro but it adds several minutes onto the time it takes to do a champion spawn. I have tried this same macro in EC and it works flawlessly, however I play UO for the nostalgia and do not like to switch to EC whenever I do a champion spawn. Has anybody else experienced this crashing? There was 0 issue with the same macro 5 years ago? What happened?
Regards,
I am asking that a game function not crash the client when used. I’m not asking for anything game changing or hypothetical nonsense. I would just like to have the in-client macro not crash the client when in use.
Macro: Line 1, Select nearest-> Hostile. Line 2, AttackSelectedTarget
Press this button at a champion spawn and you lock up and crash on the classic client. I’m at max play window and resoloution available and I play in windowed mode. I wouldn’t need this if the game code would automatically initiate combat with the closest hostile when in war mode. You know UO though... surrounded by litches? Cool the skeleton 4 tiles away flagged and is your current target so have fun playing double clicky now or die a horrible death and run all the way out of deceit to find a healer. Ya bummer... you can literally hold down one button in EC and just run around in circles. I just want this macro for when im surrounded and dont want to play double clicky or die.
As a EC player I just want to say NO it doesn't work flawlessly. We don't crash but we have our own issues with that macro. Ghosts for one (its been dead for an hour but we still target it) I could go on but I'm off topic.
I will take a look into this issue. There are several client crash fixes in Pub 104.