Macro issue #42

Quote : "I used to be able to put 2 digging actions in the action queue.
But now It will only execute the last action on the macro.
Shortcut 3 is a careplan action and shorcut 1 is the extract action.
This used to work.
So now only the last action is added to the action queue.
This is for digging, and I've dug like this for years.
And since last year just before the Atysmas update this has stopped working".

Quote : "I used to be able to put 2 digging actions in the action queue. But now It will only execute the last action on the macro. Shortcut 3 is a careplan action and shorcut 1 is the extract action. This used to work. So now only the last action is added to the action queue. This is for digging, and I've dug like this for years. And since last year just before the Atysmas update this has stopped working". ![Clipboard_-_January_24__2022_12_08_PM](/uploads/af099876be784f09a85bfc05dc71ba91/Clipboard_-_January_24__2022_12_08_PM.png)

assigned to @nimetu

moved from ryzom/bugs/misc#48

changed the description

It might be caused by commit 591ea6869e

I'm pretty sure the commit is correct, as it caused client and server become out of sync when tracking what action is queued.

I'll see if I can figure out better fix that does not break the macro.

It might be caused by commit https://gitlab.com/ryzom/ryzom-core/-/commit/591ea6869e6d0b375365bd0a7c90257cf5fac0cf I'm pretty sure the commit is correct, as it caused client and server become out of sync when tracking what action is queued. I'll see if I can figure out better fix that does not break the macro.

There seems to be key detail missing: macro fails on character that does careplanning. It works fine on who does extracting.

I believe this macro also failed previously when target was far and character had to run to (player probably just activated macro again after target was reached).

591ea686 commit is not at fault here.

What seems to be a bug, if target is close, careplan should continue to run even if next action (extraction) is rejected.

What is not a bug, if target is far, then extraction is correctly overwriting careplan action.

Solution for player, use different macros for extracting and careplanning.

There seems to be key detail missing: macro fails on character that does careplanning. It works fine on who does extracting. I believe this macro also failed previously when target was far and character had to run to (player probably just activated macro again after target was reached). 591ea686 commit is not at fault here. What seems to be a bug, if target is close, careplan should continue to run even if next action (extraction) is rejected. What is not a bug, if target is far, then extraction is correctly overwriting careplan action. Solution for player, use different macros for extracting and careplanning.

assigned to @nimetu

Labels Milestones

Macro issue #42