Excelsior

Is there a timer on crafting or something? Every time I craft I get disconnected after a certain period of time.

Are you using razor? there is an occasional problem where you'll get dc'd because of gump errors i believe

It's an antimacro code.

I had similar issues when filling bods with a script. Because the script was running too fast compared to manual filling/crafting i got disconnected after certain amount of completed bods. Very annoying and i truly hope it gets removed one day soon.

You have to implement longer waits in your script If you are using one and hope this will pass the check for this antimacro code.

It's not really anti-macro code, it's how the server works and probably if you do a macro this happens more often.

Each player has a limit of 512 open gumps (a gump is an in-game window, such as the crafting menu). Once you open 500 gumps, or well if you craft 500 items, the limit is reached and the server disconnects you. It's also because each gump that you have open, consumes memory on the server. So in order to avoid one player filling up too much memory, there is a limit.

Now, as you click a button the gump is considered closed and can be discarded from the server's memory. But somehow, sometimes if you click something the gump isn't removed from the server's memory. I don't know if this happens only if you macro too fast with razor, or if this would happen if you would be manually clicking. One way you can find out i suppose, is if you craft 512 items manually by clicking (to be sure, rather round this number up a bit, to let's say 530).

It routinely disconnects even without a macro running. For a long time I have been getting frequent disconnects during my crafting sessions without macros. I tend to fill about 100-200 bods at a time, so I hit that 500 gumps a lot. Now I can have an idea of when to expect the disconnect.

Isaac Newton

Thanks for the info +Coli!
I'll see if i can play with it and find a workaround when filling bods.

Hmm, ok thanks for the info. The problem was actually with EasyUO, a cooking macro, but I suppose that would cause the same issue.