|
|
Post by paladiex on Dec 21, 2016 19:27:49 GMT
Maybe after I develop the rune evaluation system. Ive mostly just compiled the communities work. I would feel bad for accepting donations for other people's material. Thanks though  Edit 1: I have done a TON of "trimming" and drastically decreased the start time of the bot. Testing everything now to make sure it works. Going to do some more "trimming", and move some stuff around. Hoping for an update tomorrow if things go well. Edit 2: After trimming and moving everything around I have got it as lean as I can get it. I broke the language detection, region scanning, half res, and rift farming. I will be updating a beta of this script soon hopefully. I need to confirm it is working for multiple devices before I start working on the ratio options. Edit 3: Seems like it is working for me, I will be leaving it on over night to see the results. This is probably a downgrade for most users but it is leaner and easier for me to improve, I will post it up for feedback but keep the older version up for now. i will be waiting for it . thx for your hard work I have posted my script version. It is 150 lines vs the 316 lines prior. It also uses 18 images instead of the 70-75 prior. For now it may not actually be any faster than Anku's because it's scanning in a 2560 ratio environment and will take longer to find the images. It's also not going to run on everyone phone. I encourage anyone who has a phone that runs 2560 native to try it out though, I need testers/feedback. I will be tweaking it some more when I get home. This one will be much easier for me to update and maintain. Edit1: I come back to my device and it randomly decides to go back to my island. Gotta pinpoint where this is happening. Im sure this will be riddled with bugs so I left the older version up for now. |
|
|
|
Post by wssn on Dec 22, 2016 8:03:03 GMT
i will be waiting for it . thx for your hard work I have posted my script version. It is 150 lines vs the 316 lines prior. It also uses 18 images instead of the 70-75 prior. For now it may not actually be any faster than Anku's because it's scanning in a 2560 ratio environment and will take longer to find the images. It's also not going to run on everyone phone. I encourage anyone who has a phone that runs 2560 native to try it out though, I need testers/feedback. I will be tweaking it some more when I get home. This one will be much easier for me to update and maintain. Edit1: I come back to my device and it randomly decides to go back to my island. Gotta pinpoint where this is happening. Im sure this will be riddled with bugs so I left the older version up for now. is not easier to put order like this if exist in this locations click ? does that fix resolution problem for all device ? and i am gonna test this now after update my sw data |
|
|
|
Post by paladiex on Dec 22, 2016 16:17:08 GMT
I have posted my script version. It is 150 lines vs the 316 lines prior. It also uses 18 images instead of the 70-75 prior. For now it may not actually be any faster than Anku's because it's scanning in a 2560 ratio environment and will take longer to find the images. It's also not going to run on everyone phone. I encourage anyone who has a phone that runs 2560 native to try it out though, I need testers/feedback. I will be tweaking it some more when I get home. This one will be much easier for me to update and maintain. Edit1: I come back to my device and it randomly decides to go back to my island. Gotta pinpoint where this is happening. Im sure this will be riddled with bugs so I left the older version up for now. is not easier to put order like this if exist in this locations click ? does that fix resolution problem for all device ? and i am gonna test this now after update my sw data I'm going to go towards that direction with location. Basically, when it looks for a certain picture it will search in a box around that location based on locations I input. The issue with this is that the location data has to be a variable that is dependent on the ratio. IE if I define a box that is (800, 0, 800, 0) in 2560 it needs to be (400, 0, 400, 0) in 1280. So I would need to set it as (800*n, 0*n, 800*n, 0*n) where n=(selected ratio)/2560. Currently I am not having luck with this, it will be added but I am more focused on debugging what I currently have at the moment so I can release a version that works as successfully as Anku's. Then I will scale it for multiple ratios, then I will speed it up using location data. After all that I will work on adding back in the next area option. After everything is working as good as Anku's, I will work on the gb10 beta rune evaluation system; I am very worried that if it works on 2560 it will break when scaled down. No way to know for sure without testing though. Edit 1: Also, I will be adding back in the network dialog fix. I haven't forgotten about that. lol |
|
|
|
Post by deathwardens on Dec 22, 2016 16:30:48 GMT
Tried your latest but it can't work as predicted as my device is 1080. I'm using a xiaiming redmi note 3. Will try the script on my tablet over the weekend to see if that works. But I must say, whatever u r doing is good. The start of the script is much faster than previous ones. Only after that, it can't detect and press d buttons probably due to the screen ratios.
|
|
|
|
Post by paladiex on Dec 22, 2016 16:40:54 GMT
Tried your latest but it can't work as predicted as my device is 1080. I'm using a xiaiming redmi note 3. Will try the script on my tablet over the weekend to see if that works. But I must say, whatever u r doing is good. The start of the script is much faster than previous ones. Only after that, it can't detect and press d buttons probably due to the screen ratios. I have been debugging the past few days. The section involved with recharging energy or waiting for energy to recharge is giving me trouble. Once I get this debugged I will be posting a password protected version with the compatibility options. Is it correct to assume you are playing in 1920x1080? if so I think the 1920 version will work. Edit 1: Aha! Found the culprit. I will start the compatibilty option and release an updated password protection version. |
|
|
|
Post by wssn on Dec 22, 2016 17:03:29 GMT
is not easier to put order like this if exist in this locations click ? does that fix resolution problem for all device ? and i am gonna test this now after update my sw data I'm going to go towards that direction with location. Basically, when it looks for a certain picture it will search in a box around that location based on locations I input. The issue with this is that the location data has to be a variable that is dependent on the ratio. IE if I define a box that is (800, 0, 800, 0) in 2560 it needs to be (400, 0, 400, 0) in 1280. So I would need to set it as (800*n, 0*n, 800*n, 0*n) where n=(selected ratio)/2560. Currently I am not having luck with this, it will be added but I am more focused on debugging what I currently have at the moment so I can release a version that works as successfully as Anku's. Then I will scale it for multiple ratios, then I will speed it up using location data. After all that I will work on adding back in the next area option. After everything is working as good as Anku's, I will work on the gb10 beta rune evaluation system; I am very worried that if it works on 2560 it will break when scaled down. No way to know for sure without testing though. Edit 1: Also, I will be adding back in the network dialog fix. I haven't forgotten about that. lol the script start faster and that is nice 1st things i try was limit your rune future and i got errore then i try wothout and work fine except when finish rune it is go to world map some time and give me error and sometime rerune the dungen ( i was farming sd dungen ) i will try to upload scrreshot right now but internet is slow so u have to wait why not build a 1 ver of script the we change ratio in every copy ex: ver2.2 for 2540 download here and another ver ex : ver 2.2 for1280 download here and like that i don't thinks u have to rewrite all code only change the number of resolution or location inside the script ? correct me of i am wrong ? and thx for your hard work |
|
|
|
Post by paladiex on Dec 22, 2016 17:11:55 GMT
I'm going to go towards that direction with location. Basically, when it looks for a certain picture it will search in a box around that location based on locations I input. The issue with this is that the location data has to be a variable that is dependent on the ratio. IE if I define a box that is (800, 0, 800, 0) in 2560 it needs to be (400, 0, 400, 0) in 1280. So I would need to set it as (800*n, 0*n, 800*n, 0*n) where n=(selected ratio)/2560. Currently I am not having luck with this, it will be added but I am more focused on debugging what I currently have at the moment so I can release a version that works as successfully as Anku's. Then I will scale it for multiple ratios, then I will speed it up using location data. After all that I will work on adding back in the next area option. After everything is working as good as Anku's, I will work on the gb10 beta rune evaluation system; I am very worried that if it works on 2560 it will break when scaled down. No way to know for sure without testing though. Edit 1: Also, I will be adding back in the network dialog fix. I haven't forgotten about that. lol the script start faster and that is nice 1st things i try was limit your rune future and i got errore then i try wothout and work fine except when finish rune it is go to world map some time and give me error and sometime rerune the dungen ( i was farming sd dungen ) i will try to upload scrreshot right now but internet is slow so u have to wait why not build a 1 ver of script the we change ratio in every copy ex: ver2.2 for 2540 download here and another ver ex : ver 2.2 for1280 download here and like that i don't thinks u have to rewrite all code only change the number of resolution or location inside the script ? correct me of i am wrong ? and thx for your hard work I am programming this as you typed your comment. The pictures are being converted now Ultimately that was one of the purposes of rewriting the script. If I start at a super high ratio (2560) I can scale the images down and they will be high quality. The issue before was the 70+ pictures, I need a copy of every picture in every ratio. By limiting the pictures I am lowering the file size of the bot and the amount of re-scaling I have to do for every ratio I choose to support. Edit 1: Testing now Edit 2: Released compatiblity mode, seems like selecting a lower resolution speeds up the bot too. Edit 3: Forgot to include the ability to remove the on screen navigation bar. Quickly updated it. |
|
|
|
Post by wssn on Dec 22, 2016 20:05:35 GMT
Limit your run is not working
With palbot last ver and ver1
Same error
Something abouy nil vale
It did not even asking me about number of run
|
|
|
|
Post by paladiex on Dec 22, 2016 21:38:31 GMT
Limit your run is not working With palbot last ver and ver1 Same error Something abouy nil vale It did not even asking me about number of run Thanks! Adding it now! Edit 1: It should be fixed now, I will release it with the next update. I am utilizing region data to shorten search times for all versions. I will release it all once when I finish tonight. Edit 2: Testing the new image finding. Edit 3: Fixed run limits, added the regions to every image BUT for now it is not usable. I cannot figure out how to assign the region to each image in a variable. Sadly I haven't been able to get it to work. I will need to do some research. |
|
jprem
Junior Member
Posts: 76
|
Post by jprem on Dec 23, 2016 3:34:40 GMT
Thanks! Adding it now! Edit 1: It should be fixed now, I will release it with the next update. I am utilizing region data to shorten search times for all versions. I will release it all once when I finish tonight. Edit 2: Testing the new image finding. Edit 3: Fixed run limits, added the regions to every image BUT for now it is not usable. I cannot figure out how to assign the region to each image in a variable. Sadly I haven't been able to get it to work. I will need to do some research. Well done mate, I'm really glad that you're 'putting your name on it', so to speak. I'm on a Moto G (2013) that has 720*1280 resolution, I hope you'll support this soon. Would it be possible to add an, "Supports only resolution(s)" section under Palbot's known issues? Once again, great work! |
|
|
|
Post by paladiex on Dec 23, 2016 5:06:44 GMT
Thanks! Adding it now! Edit 1: It should be fixed now, I will release it with the next update. I am utilizing region data to shorten search times for all versions. I will release it all once when I finish tonight. Edit 2: Testing the new image finding. Edit 3: Fixed run limits, added the regions to every image BUT for now it is not usable. I cannot figure out how to assign the region to each image in a variable. Sadly I haven't been able to get it to work. I will need to do some research. Well done mate, I'm really glad that you're 'putting your name on it', so to speak. I'm on a Moto G (2013) that has 720*1280 resolution, I hope you'll support this soon. Would it be possible to add an, "Supports only resolution(s)" section under Palbot's known issues? Once again, great work! I can actually add a bunch more resolutions quickly. I'll see if I can't get an update up within the hour. Also, tons of bug fixes edit 1: Try running it with compatibility mode, 1280 is an option. ALSO, it should work if your native resolution is close to whatever option you pick in compatibility. Just try all 4 until 1 works. edit 2: Threw up 1.1.3 ~~ Bug fixes galore |
|
|
|
Post by wssn on Dec 23, 2016 8:06:02 GMT
Still testing the last ver U fix the bugs that happend to me last night about limit rune and all slot are taken bug , the script want to take 5 monster intead of 4 . One of thing i have found was no rune keep count also no win loss count when i stop the script Also network error is still not fixed All that not needed to be fixed now Resolution fix is most important Still testing Thx for your work |
|
|
|
Post by paladiex on Dec 23, 2016 13:28:04 GMT
Still testing the last ver U fix the bugs that happend to me last night about limit rune and all slot are taken bug , the script want to take 5 monster intead of 4 . One of thing i have found was no rune keep count also no win loss count when i stop the script Also network error is still not fixed All that not needed to be fixed now Resolution fix is most important Still testing Thx for your work The script wanted to take 5 monster instead of 4? Odd, I never experienced that. But you said it is no longer occuring; right? I'll check the win/loss and rune count thing. I will start adding in network, and next area when the bot is stable. Happy to work on it. Edit 1: Found the issue with win/loss ratios. I added in print commands, however the log at the end will be long. I will either post the update tonight, or later with the network connection thing. |
|
|
|
Post by wssn on Dec 23, 2016 17:34:49 GMT
Still testing the last ver U fix the bugs that happend to me last night about limit rune and all slot are taken bug , the script want to take 5 monster intead of 4 . One of thing i have found was no rune keep count also no win loss count when i stop the script Also network error is still not fixed All that not needed to be fixed now Resolution fix is most important Still testing Thx for your work The script wanted to take 5 monster instead of 4? Odd, I never experienced that. But you said it is no longer occuring; right? I'll check the win/loss and rune count thing. I will start adding in network, and next area when the bot is stable. Happy to work on it. It is no longer occuring But i got errore when i select limit my run sometime not always In monster screen select that happend Runtime error:com.appautomatic.ankulua.f: Cant find P (smallflash.png) s:0.9 Stack traceback C in function click ? In function click Palbot v1.1.3.... In function replay Palbot ............ In main chunk |
|
|
|
Post by paladiex on Dec 24, 2016 2:42:23 GMT
The script wanted to take 5 monster instead of 4? Odd, I never experienced that. But you said it is no longer occuring; right? I'll check the win/loss and rune count thing. I will start adding in network, and next area when the bot is stable. Happy to work on it. It is no longer occuring But i got errore when i select limit my run sometime not always In monster screen select that happend Runtime error:com.appautomatic.ankulua.f: Cant find P (smallflash.png) s:0.9 Stack traceback C in function click ? In function click Palbot v1.1.3.... In function replay Palbot ............ In main chunk Ty, I will make changes accordingly. Edit 1: Decided to post the update, my bot error-ed out while I was at work. It was only happening to me while i was in compatibility mode. Keep the feedback coming guys! I am super grateful. Edit 2: Sorry, seems to error out immediately now. I'll fix it. Edit 3: Okay, I'm eating dinner now. A working fix is posted in op now Edit 4: Noticed energy refill using crystals isn't working as planned. Testing a fix now. Edit 5: Updated OP with a new version Edit 6: Posted another fix! Hoping to get the bugs squashed so I can work on more relevant upgrades soon. |
|
