Junie-774 / CraftingList

8 stars 4 forks source link

"Ignore <wait.x> and wait intelligently" feature not working #11

Closed lyndistt closed 1 year ago

lyndistt commented 1 year ago

On the latest version, crafting stuff with macros gives this error, regardless of crafts. I've tried with 1 macro recipe, 2 macro recipes, and trained eye recipes, and all of them gives this error below:

https://cdn.discordapp.com/attachments/984006071293214761/1067079937015689226/image.png

I've also tried playing around with the "wait after clicking synthesis/executing macro" timers and different combinations of turning those off and on. The only workaround that seems to fix it for me right now is to turn off "Ignore wait''.

Junie-774 commented 1 year ago

Which type of macro are you using? Can you provide me an image of what happens in /xllog when you do this with the log level set to Debug?

lyndistt commented 1 year ago

image

I used In-Plugin Macros. The first row of error is for this macro, while crafting Rarefied Lemonade:

/ac "Trained Eye" /ac Groundwork /ac Groundwork

The second row of error is this macro, while crafting AR-Caean Velvet:

/ac "Muscle Memory" /ac Manipulation /ac "Waste Not II" /ac Innovation /ac Groundwork /ac "Preparatory Touch" /ac "Preparatory Touch" /ac "Preparatory Touch" /ac Innovation /ac "Preparatory Touch" /ac "Great Strides" /ac "Byregot's Blessing" /ac Groundwork

Let me know if there is any other info or log that you need :)

Junie-774 commented 1 year ago

Hmm, alright. And can you send me an image of your experimental tab?'

Oop, I've done some testing on my end. The fields "WaitForConditionLoop", "AfterWaitForCondition", and "CraftingActionMaxDelay" somehow got sent out with 0 as their default values, which is uhh, very incorrect. I tried sending out a fix that would reset them if they were found to be 0 but that didn't work. For now you can manually change them and they'll save, but that's what's going on. I'll be releasing a (hopefully) working fix for this issue soon

Junie-774 commented 1 year ago

Released a fix that should work, feel free to reopen if it doesn't