|
|
Post by paladiex on Aug 30, 2017 16:52:12 GMT
Nice work  I was thinking of working on something like this.. but might end up just using this instead. It's open source  if you wanna make any contributions please do so. I'm adding in rune swapping today but the new WoW patch dropped so I am playing that too. Edit 1: I've added new images, so users need to run the imageupdater.lua after updating. The PalPowerUp will now upgrade runes like before, but cycle between all runes. I've added an editable value for "flat stats". It's VERY experimental at the moment. Users can pick a # of flat stats to be on the rune before the bot sells. If the user selects 0, the bot will sell every rune in that category. If the user selects 4 the bot will keep all runes in that category since "flat stats" are only atk+ def+ and hp+. A good example of this feature is with hero runes. If the user selects "2" for flat stats, it will sell all hero runes that have 2 out of the 3 flat stats, IE: 5 stars, Hero, Def % mainstat, atk+ sub, def+ sub, crit rate sub. |
|
|
|
Post by paladiex on Aug 30, 2017 23:54:54 GMT
Video added to OP, bot is rocking now. May need to make minor adjustments to swiping. Make sure to run imageupdater.lua!!!
|
|
|
|
Post by AnkuLua on Aug 31, 2017 1:54:15 GMT
Congratulation for winning two life long Pro2 licenses.
Please PM us the account to authorize the licenses.
It could be authorized and recommended to the same account.
Please register and active the account with Pro2 first.
|
|
|
|
Post by paladiex on Aug 31, 2017 2:00:51 GMT
Congratulation for winning two life long Pro2 licenses. Please PM us the account to authorize the licenses. It could be authorized and recommended to the same account. Please register and active the account with Pro2 first. Is this time sensitive? I wanna ask a few of my buddies  |
|
|
|
Post by zweihaander on Aug 31, 2017 9:58:27 GMT
Hello, First, thank for the amazing job that you have done here. But now, i'm having an issue, i can't power up a single rune. Maybe I'm missing something, dunno. 
Edit 1 : i have looked for "powerUp1.png" image in the folder... and didnt found it. Maybe it comes from here ? edit 2 : OMG, i'm just a big noob. I let run imageupdater for a while (till the end actually ) and that way all the files have been downloaded. I won't delete my post, maybe they are some monkeys like me. Everything is working perfectly. Amazing. |
|
|
|
Post by paladiex on Aug 31, 2017 14:10:06 GMT
Hello, First, thank for the amazing job that you have done here. But now, i'm having an issue, i can't power up a single rune. Maybe I'm missing something, dunno.
Edit 1 : i have looked for "powerUp1.png" image in the folder... and didnt found it. Maybe it comes from here ? edit 2 : OMG, i'm just a big noob. I let run imageupdater for a while (till the end actually ) and that way all the files have been downloaded. I won't delete my post, maybe they are some monkeys like me. Everything is working perfectly. Amazing.Cool Edit 1: Not sure if anyone but me has been testing it, but I noticed that it frequently bugged out after around 10+ minutes of use. I noticed that it had to do with the dragdrop command when swiping the rune list up. I slowed down that process, so that it does not bug out. I also changed the dragging by 4 pixels, this way it should be accurage even if you have 600-700 runes! |
|
|
|
Post by zweihaander on Sept 1, 2017 8:44:04 GMT
When it finds a lvl 15 rune, the bot crashes  |
|
|
|
Post by paladiex on Sept 1, 2017 14:08:57 GMT
When it finds a lvl 15 rune, the bot crashes Mine sees a lot of level 15 runes and doesn't crash What do you have the legendary upgrade set to? |
|
|
|
Post by amidamaru10 on Sept 2, 2017 3:55:58 GMT
When it finds a lvl 15 rune, the bot crashes Mine sees a lot of level 15 runes and doesn't crash What do you have the legendary upgrade set to? same problem here, crash with +15 runes |
|
|
|
Post by paladiex on Sept 2, 2017 4:09:57 GMT
That error references this line of code
while (runeLvl < upgradeLegendaryLmt)
This variable tells me that the bot is having issues with the level of the rune, level 15 runes cost 0 mana and is detectable on my end 100% of the time. Did you put letters in the dialog box where it asks you what you want to upgrade legendary runes to? Otherwise you are getting an error on the bot trying to find the "0" mana image correctly.
Are you having issues exclusively with +15 runes? Or other kinds of runes aswell?
Send me a screenshot of the rune that is giving you issues at the "Rune Power-up page"
Edit 1: Make sure you guys are using the updated version (must update by enabling access to the internet in ankulua), there was an issue with toasts blocking the view of the mana cost and causing that error. But it has since been fixed.
|
|
|
|
Post by rabiddoughnuts on Sept 2, 2017 4:51:30 GMT
I was upgrading runes and I was wondering if you could add different choices for star values as well as slot, I want to keep all choices, just add those. My reasoning is that for odd slots for instance I sell any thing blue with a single flat, I let purple have 1 flat, and legendary I don't care because I can reappraise, at least if its a 6* but for even slots I keep most stuff still for now depending on set etc. Also, I have def been testing, and I do occasionally have crash at +15 runes, but it isn't all runes, if it happens again I will start a log and look for a pattern, send you anything I find.
Edit: just realized, I can kinda do the odd vs even by just controlling that in my manager, though then I have to upgrade runes in two different sets. |
|
|
|
Post by paladiex on Sept 2, 2017 5:50:47 GMT
I was upgrading runes and I was wondering if you could add different choices for star values as well as slot, I want to keep all choices, just add those. My reasoning is that for odd slots for instance I sell any thing blue with a single flat, I let purple have 1 flat, and legendary I don't care because I can reappraise, at least if its a 6* but for even slots I keep most stuff still for now depending on set etc. Also, I have def been testing, and I do occasionally have crash at +15 runes, but it isn't all runes, if it happens again I will start a log and look for a pattern, send you anything I find.
Edit: just realized, I can kinda do the odd vs even by just controlling that in my manager, though then I have to upgrade runes in two different sets. I can add in slot detection relatively easily next patch since I have the method already integrated in Palbot. I've been toying with a method to detect which stat recieved the upgrade on +3 rolls, that way the bot can sell runes that roll into the flat stats. The issue I've been running into is how to setup the dialog box to give users the option to customize everything they want to. I'll look into this more, if you have any ideas feel free to toss those out. A paint or general description works. There was an issue until today where the bot would occasionally sell a rune, then try to click the next rune too quickly, and not be able to proceed because it cannot find the powerup button. This has been patched as of tonight. The only reason a user should get an error on +15 runes in line 531 of the code is that the 0 mana image isn't matching correctly, or the number users put on the front page isn't valid for legendary runes. If the 0 mana image isn't matching correctly then users are either missing the 0 mana image (which is the case in the initial release if users have not opted to enable internet access in ankulua), or users are not playing in 1920x1080, in which case users would experience a lot more errors. I believe that users who have failed to update will bug out on 100% of the 5* +15 runes because the initial image directory was missing that image. Or the error code you had was in regards to the "powerupbutton.png" not being visible, which was patched today. In case I am wrong, I've added multiple lines of code to the latest version that will tell me more specifically why the error is occuring. Tonight is the first night I have been able to run the bot through a full list of 568 runes without recieving an error. I've sold about 50  Edit 1: I actually noticed currently the bot does not scan the last row of images, this is an issue I created when attempting to squash bugs. I will fix it tomorrow morning. Please post bug reports. Screenshot the error, and the screen behind the error after clsoing it. |
|
|
|
Post by dragonscale15 on Sept 2, 2017 9:14:34 GMT
WOw, amazing software Sir! Thanks , will test it out
|
|
|
|
Post by amidamaru10 on Sept 2, 2017 12:42:38 GMT
|
|
|
|
Post by paladiex on Sept 2, 2017 15:03:49 GMT
Pushed a new update that uses more lenient values for determining rune rank (similar to palbot). Let's see if that fixes it. |
|
I was thinking of working on something like this.. but might end up just using this instead.
if you wanna make any contributions please do so. I'm adding in rune swapping today but the new WoW patch dropped so I am playing that too.
