Why Would 4.0.1 Break This Macro?

[Ughmahedhurtz]

You can try

/in 2 /run StaticPopup_Hide("PARTY_INVITE")

or some variant of that. I know it works for chat and a few other minor things. Never tried it out of combat on other things.

[Sam DeathWalker]

So delays out of combat are not against the TOS?

[Ughmahedhurtz]

Using the "/in" command is obviously OK as they provide the command for your use. I'd be very wary of extrapolating that to encompass any other delay mechanisms.

[Mercurio]

Well... huh, more confusion.

Here's my latest macro:

/run AcceptGroup();ConfirmSummon();AcceptQuest(); AcceptTrade();RetrieveCorpse();RepopMe();
/click LFDRoleCheckPopupAcceptButton;
/click LFDDungeonReadyDialogEnterDungeonButton;
/in 1 /run StaticPopup_Hide("PARTY_INVITE");

I invited this toon, clicked the macro, and it worked like a charm! I thought great, problem solved, right?

Then I left party and tried it again, just to make sure.... insta-decline - the popup didn't even show up.

After trying this multiple times, when I log into the game the first time it works great, but all other times no matter who invites him until I relog my toon auto-declines. Good grief, I didn't figure an accept macro could be so complex.

[Ughmahedhurtz]

After trying this multiple times, when I log into the game the first time it works great, but all other times no matter who invites him until I relog my toon auto-declines. Good grief, I didn't figure an accept macro could be so complex.

Sounds like you stumbled on a known UI bug. Now that you mention the failure conditions, I remember this happening with a group-invite macro where I just hid the dialog instead of clicking the button. Jamba's code works great so I disabled my macro and let it handle the invites. See if Jafula's suggestion fixes it.

[Mercurio]

Sweet! Yep, that fixed it. All the accept stuff back in one button again

You guys are great.