Closed Tysaki closed 2 years ago
just came to my mind, a quick and dirty fix for the issue would be to just add a fixed /wait 3 after the conditial action was executed
can you show me the full macro you were using that you had issues with?
The syntax should be <condition.whatever> <wait.3>
On Sat, Jan 1, 2022 at 2:59 PM Tysaki @.***> wrote:
just came to my mind, a quick and dirty fix for the issue would be to just add a fixed /wait 3 after the conditial action was executed
— Reply to this email directly, view it on GitHub https://github.com/daemitus/SomethingNeedDoing/issues/25#issuecomment-1003609019, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFMTBGFRAMJXYHNE7G2AKLUT5MIJANCNFSM5LCH7TJQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
i tried it again today with the syntax you provided and it seems to work. strange. i was sure i tested that. maybe i had a typo somewhere. sorry
hey, it seems that as soon as a condition is met, for example, the following /ac cant be properly executed because the skill used by the condition has no wait on it.
i tried chaining the condition with wait
but had no luck.
Thank you so much for your work on the plugin, its really great so far.