Page 2 of 2
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 13, 2020 7:39 am
by cjimaras
Also the autoreaping for the elder beardweed seed (lvl 200 strength) is not working. Anyone knows how to fix it?
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 13, 2020 8:30 am
by orkom
Melkoroth wrote: Fri Apr 10, 2020 8:44 pm
Just found this thread. To fix flaming breath please see
this other post. The pots are bugged anyway and can't be used :/
Thanks, I've updated the uploaded version with the changes.
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 13, 2020 8:36 am
by orkom
cjimaras wrote: Mon Apr 13, 2020 7:39 am
Also the autoreaping for the elder beardweed seed (lvl 200 strength) is not working. Anyone knows how to fix it?
I's working for me.
Are you sure you are using the up to date version of the addon?
Re: [ADDON] Craftvaluetip
Posted: Sun Apr 19, 2020 11:18 pm
by Mathinus
Updated to 1.5.7, Bittersweet Elvish Parsley stopped autoreaping for me, all the other 200 seeds are ok.
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 20, 2020 6:37 am
by orkom
Mathinus wrote: Sun Apr 19, 2020 11:18 pm
Updated to 1.5.7, Bittersweet Elvish Parsley stopped autoreaping for me, all the other 200 seeds are ok.
That is strange, I tested it myself and I had few people running the test and it works.
I suspect the issue you are facing is not directly connected with this version.
Could you please make sure you don't have multiple craftvaluetip in your folder or other addons that have the same functionality, and in the addon list in game you can see Crafting Info Tooltip and the reported version is 1.5.7?
To narrow this down, can you please make a new profile and only run:
- MGRemix
- Libslash
- CraftvalueTip
To see if the addon it's working?
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 20, 2020 11:17 am
by Mathinus
I compared 1.5.6 and 1.5.7 CraftData files and it looks like in 1.5.7 Bittersweet Elvish Parsley ID was reverted back to 83515, changed it back to 83516 and it autoreaps it now.
Re: [ADDON] Craftvaluetip
Posted: Mon Apr 20, 2020 11:27 am
by orkom
Thanks for looking into this, I don't know what happened.
I've updated the mod to 1.5.8 and added the fix