1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice

"You must wait to perform another action" : how can I address this problem ?

Discussion in 'UHall' started by popps, Feb 1, 2011.

Thread Status:
Not open for further replies.
  1. popps

    popps Always Present
    Stratics Veteran Stratics Legend

    Joined:
    Feb 27, 2004
    Messages:
    13,445
    Likes Received:
    461
    When working with Lobster traps, I learned that the timing of pulling out of the water the trap, empty it and deploy it back into the water is essential to be ready to address another trao that *bobs* and avoid it to sink, if possible.

    Now, to expedite my actions, I usually do the following.

    - Double click the deployed trap in the water;
    - Double click trap in my backpack to empty it;
    - Use my last object macro to get the cross hair cursor to deploy trap back into the water.

    I usually have no problems with the first 2 actions, the problem comes with the third one.

    Very often, way too often to my liking, when I hit my last object macro I get the client error message "You must wait to perform another action".

    This wastes me sometimes crucial seconds which prevent me from getting to another trap which has just bobbed and often, because of this, I loose more traps than I should (and with them the preciou load of named crabs/lobsters....).

    I would really love to get rid of this problem and no longer get this error message but how ?

    Anyone has any good advice on how I can avoid the client to tell me that I have to wait before I can use my last object macro ?

    Thanks.
     
  2. Tazar

    Tazar Guest

    It is not an error.
    It was put into the game ages ago as a measure to fight scripting.
    Any method to "avoid" it would be an exploit.

    This thread is being locked to prevent such exploit measures from being discussed.
     
Thread Status:
Not open for further replies.