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
  3. Greetings Guest, Having Login Issues? Check this thread!
    Dismiss Notice
  4. Hail Guest!,
    Please take a moment to read this post reminding you all of the importance of Account Security.
    Dismiss Notice
  5. Author Wes Locher has teamed up with Stratics for a giveaway of his new book Braving Britannia. This book explores the history and impact of Ultima Online and includes interviews from current and past dev team members as well as many UO and Stratics community members. Click here for more details!
    Dismiss Notice

[BUG] Mouse 4 and Honor macro

Discussion in 'UO Enhanced Client Discussion' started by pgcd, Aug 24, 2009.

  1. pgcd

    pgcd Guest

    For the last couple weeks I've been using mouse button 4 within the "input" page of the user settings, bound to "Target Nearest Enemy". Yesterday I decided to assign it to a macro instead, which goes something like this:

    Target Nearest Enemy
    Honor Virtue
    Wait For Target
    Cursor Target Current

    The macro works, except for the fact that honor gets invoked twice, so I'm left with a target cursor, and I need to press ESC to cancel it. This happens even if I try swapping the first two actions in the macro, but it doesn't happen with a different key binding - am I doing something wrong or is this actually a bug?

    Furthermore, I think that the input page User Settings should be char-bound, instead of shard-bound as they seem to be: sometimes I need to have keys bound to different things for different chars, and I can't seem to do it without using macros (and there's no action for things like "target party member 1", is there?).
  2. pgcd

    pgcd Guest

    After a few tries, I think the problem is the actual button involved, since the same macro seems to work fine with a different hotkey. Possibly it's a matter of drivers - the mouse is a Microsoft Wireless.