[Ryuuku]

The anti macro gump sometimes crash me, and when I log back I cant answer it anymore, so I have to wait to die.

Should add a command to bring the gump back when that happens.

[Ryuuku]

Really man, that need a fix urgent, I`m tired of dieing because I crashed and cant answer it anymore

[Israfil]

I will have shade or Eru look into it. If anything it wouldn't be available until the next server resatart.

[Shade]

The crash has to do with a third party program either trying to close, move or respond to the gump. Working on a different antimacro system at the moment though. Hopefully it will be up soon.

In the mean time, if you use razor make sure that rewards gump isnt checked in the filter section under the general tab. Also if you use an EasyUO script, make sure it doesn't have a built in gump response as that would do it too.

[Ryuuku]

What about the INX anti macro? the one you had to write the word...

Isnt possible to make a command to show the gump if you close it?

[Eru]

We'll be switching to the CAPTCHA style anti macro gump once we figure out a way to do so. The problem is it uses a SQL database and the computer with the RunUO server needs access to the tables remotely, but the free host we're using only lets you have local access. (only the host's computer can access it)

As for fixing the crash, let me know:

Client version (visible at login screen)
Assist program (Razor? injection? Easy UO?)
Operating System (windows version)
Patching method. (IN Patcher? Full package?)

From the *sound* of things, if you crash every time you get the gump, there may have been an error while you were patching. For instance, if you have a program open that was reading from one of UO's .mul files while you ran the patcher, the patcher may have failed to overwrite that file correctly.

Try manually downloading gumpart.mul and gumpartidx.mul from here:
https://www.dropbox.com/s/dc14xgq51tv44uv

Stick those in the UO directory and see if it keeps happening.

IF it still crashes after that, go to where the patcher is at and delete "Patcher.ini" (Or just the timestamps table inside if you want to be fancy) and press Patch again to force it to re-patch everything. Make sure that everything that might be using UO's files is closed first. (Client.exe Pandora.exe Razor.exe Injection Stealth Etc)

[imported_Taran]

It has nothing to do with the patcher, we had the same problem on IN:X long before the patcher. I can't remember if we found out why it happened though.

[Shade]

This will be fixed next update.