Smelt when bags are full, than mail bars. Is this possible? I searched and couldn't find one in existence. Would make life easier. Thanks.
P.S. even a one button push to make the bot go to a forge and smelt bars would be awesome enough.
(For the following two informations, you can just give us the exact mailbox location, the unit's location)
- A Forge Location (use DevTools)
- A Mailbox Location (use DevTools)
- What you want to be smelt -> There's a decent workaround, maybe I won't need this information.
- MailRecipient to be set up in the Settings.
I use two separate forge/mailboxes
Location #1
Forge Location: 3012.453, -538.493, 248.0801
Mailbox Location: 3033.967, -545.5035, 248.1075
Location #2
Forge Location: 3039.785, 1241.686, 654.2108
Mailbox Location: 3109.033, 1236.609, 654.1478
Smelting Ghost Iron Ore into Ghost Iron Bars
Thank you much for your interest![]()
Those coordinates are unit location? or player location while around the object?
1 - Check if bags are full, if so, step 2
2 - Select the nearest forge/mailbox combo, move to the forge first
3 - Turn ore into bars
4 - Moving to nearest mailbox
5 - (attempt to?) Mail fresh bars to MailRecipient
Alright, needs testing tho, tell me what goes wrong (compiled at first attempt, but I can't test it)
What it'll do :
GLHF
I haven't tried the second version you have posted, and I am unsre if the issue I faced is the error you discovered but just in case I attached a log.
WOW client would stop responding and would crash to desktop once HB started when the SmeltingBuddy Plugin was active.
I will test the second plugin tomorrow. Thanks again for all your help and hardwork![]()
Alright I went and tested the plugin and there is a pretty serious issue. Whenever the bags get full, the bot says some sort of script in /say. Not very incognito. Due to this I was unable to test the bot any further to see if the smelting plugin works. Attached is the log and a screenshot of the message.
View attachment 116539
View attachment 116540
P.S. Some real life stuff has come up and I will be out of town until Jan. 13th. Once I get back, I'll come back and peek in the thread to see where we are at![]()
[18:22:45.473 D] Could not generate path from {3213.187, -825.848, 592.3151} to {3014.496, -541.4175, 251.5835} (time used: 0 milliseconds) @ FindStartPoly
ProfessionBuddy is already part of the bot, why not trying to use this?
U'll have a lot of possibilities around Professions with this, and profiles (more or less professional) can be generated by drag/drop, click and save
This line is the main reason why you try to smelt something in the air
I also forgot to put the last commit for LUA calls, now fixed and tested on my own gatherer, should work.
I added a check to keep generating paths if the toon can't reach any other. (May cause endless loop, in this case I'll have to ask Chinajade why.) but no more LUA call in /say, and should wait to be in range of interaction with Forge/Mailboxes (hopefully)
Attempted smelting plugin (most recent plugin that you posted) next to forge with full bags and LUA call in /say occurred again. Unfortunately, there were several people around when this occured so I am assuming at least one of them may report me. I will have to lay low before I test any future plugins. Thank you for your time though- I do appreciate it.
In case you wanted it, I attached the newest log..
Lemme know what happens when you're back![]()
I ran the latest plugin next to a forge with full bags and once again it the LUA call in /say. I stopped the bot immediately afterwards since several players came up on me after the message in /say. Most likely one of them will report me so I need to lay low on testing anymore plugins. Thank you though for your time- I do appreciate it. I attached a log though in case you wanted to fix this for any other member who may be interested in a smelting plugin.
P.S. it was the same exact LUA call in /say as it was in the screen shot I posted in an earlier post.
Well i am a dummy.... Just went back through my files and realized I put the newest plugin in the wrong folder, I was testing the plugin that you fixed.. Still going to have to be a bit though before I test it.![]()