|
Post by curunoir on Nov 29, 2016 8:27:09 GMT
@sikat : with find battle enabled, the script will check your current gil, can you check if the gold region was correctly highlighted. You might need to watch the script running for a while until it goes into find battle. When the script performs a gil check it will highlight the region with a red box. You might wanna check if that box was correctly highlighted. If you can take a screenshot of that screen so I can take a look. curunoir : the script doesn't recognize French, you should switch the language to English and try again. Thanks that worked. At least for TM farm. I tried Maranda Coast exploration and it says "Can't find Rains position". When I set free farm with left-right directions I see Rain moving but on the up-left and the up-right. Does the script handle all resolutions ? My device has 1366x768 resolution.
|
|
|
Post by Sikat on Dec 2, 2016 2:19:05 GMT
Can I request a feature? Only use energy if it's above 80% or whatever percentage? Also a "no repeat" feature so that it only does one exploration, for example?
Oh and can you separate Network delay and Device delay values? So I can enter higher network delays when departing, but smaller delays when on explorations for example.
|
|
|
Post by hyudra on Dec 16, 2016 12:36:41 GMT
Enchanted Maze is not working.
|
|
|
Post by Sikat on Dec 29, 2016 11:48:17 GMT
Is this still actively being developed?
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Dec 30, 2016 6:39:20 GMT
@sikat : with find battle enabled, the script will check your current gil, can you check if the gold region was correctly highlighted. You might need to watch the script running for a while until it goes into find battle. When the script performs a gil check it will highlight the region with a red box. You might wanna check if that box was correctly highlighted. If you can take a screenshot of that screen so I can take a look. curunoir : the script doesn't recognize French, you should switch the language to English and try again. Thanks that worked. At least for TM farm. I tried Maranda Coast exploration and it says "Can't find Rains position". When I set free farm with left-right directions I see Rain moving but on the up-left and the up-right. Does the script handle all resolutions ? My device has 1366x768 resolution. tinotk , I'm experiencing the issue with "Can't find Rain's position" too, but I'm on a Samsung Galaxy S6 running 1440x2560. App is running in English (only language I can speak ). I don't experience the issue with Rain not moving left/right, but when the script tries to begin stepping, I get swipes instead. It does seem that perhaps the script is not properly aligned with the screen for Maranda Coast for some reason. Here is what my screen looks like upon entry to Maranda:
|
|
|
Post by tinotk on Jan 2, 2017 5:34:08 GMT
Are you experiencing the problem with all explorations or just Maranda Coast?
|
|
|
Post by sageelminster on Jan 2, 2017 6:38:49 GMT
Hi I was wondering if it's possible to edit the script?
I mean for the TM farming I want to speed up some part the loop? There a setting for the lag, but here I have to wait like 5-6 sec to pass to the next step cause there's no lag at all. In the process I can probable speed up the script by 15-20 sec.
Thx in advance and BTW realllllllllllllllllllly nice script you made!!!
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Jan 2, 2017 22:57:19 GMT
Are you experiencing the problem with all explorations or just Maranda Coast? Since my post I have tried other explorations to no luck. It seems to be an image match problem. Certain images seem to match while others do not. For example, the script will find Earth Shrine Exploration and click on it, but it does not seem to be able to match the Next button on the screen that follows. I do some script work myself, though not LUA. If you have a version that is verbose or has some kind of extended debugging I will gladly try running it for you. Any details you need, just let me know. I'll keep an eye on the thread so I can provide you with a timely response. PS - A quick suggestion; you don't need to image-check for Gil amounts. If you look under exviuswiki.com/Maranda_Coast/Exploration "Unit EXP Guide", you can see that there are a fixed number of battles for each zone to reach the Gil amount. Since you already are tracking the number of battles, you simply need to know to move on in each exploration when the battle count for that exploration and zone is reached. Granted, I think that the rare mini cactuar encounters are an extra battle, so maybe those would mess up the count unless you identified that particular battle and discounted it. Otherwise it might allow a battle to occur while moving to the next zone. If you can address that condition however, it might be a more elegant solution than the Gil image check, which will certainly be thrown off by the rare mini cactuar encounters.
|
|
|
Post by tinotk on Jan 3, 2017 19:30:41 GMT
Upon a few test runs with debug on I think I might know the reason. But just to make sure can you do a few runs with this version: www.dropbox.com/s/dx3bb4ambzikxdb/ffbet.zip?dl=0Please check the script folder for 2 files "run.log" and "rain_reg.png" (this file should be inside the image folder). Thanks. Regarding to the gil check suggestion, I did followed their exp guide but when I manually do the battle counts, occasionally the number don't match so that's why I'm afraid that the script might run into endless loop. So I ended up doing both gil check and battle count: if(((i>=30 and i%5==0) or (count>=14 and count<battle_counter)) and checkGold() >= limit) So here I'm assuming lua has a "smart interpreter", when the first condition failed it won't bother checking for the second condition checkGold(). Anyway I don't have enough data for a better solution yet.
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Jan 3, 2017 19:57:32 GMT
Thanks! I can confirm rain_reg.png in the images folder and run.log in the parent directory. Looking at run.log, App Screen size properly returns as 1440x2560. I can see Next_i complete, Depart btn complete, Connection check complete, Explore start compete, then Checking Rain #1, 2, 3, 4, 5, 6, 7, 8, and Rain not found. Visually, I see this (as you can see it's already failed the first check and has moved Rain forward for the next check): Your logic for handling the battles or gil seems like the best solution currently available. If we can get this working, I can try a number of runs and see if it manages to handle the cactuar encounter. I wasn't aware that you were actually converting your gil image match back to an integer value that you can actually run math operations against. Very clever!
|
|
|
Post by tinotk on Jan 3, 2017 20:05:28 GMT
Looks like the the rain region (the red box) is not right in the picture so it can never find Rain , can you attach those files so I can take a look.
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Jan 3, 2017 20:10:51 GMT
Looks like the the rain region (the red box) is not right in the picture so it can never find Rain , can you attach those files so I can take a look. Sure thing. I'll execute again; the script was still running when I hit my home screen so it doesn't have a valid screen grab from the application as rain_reg.png. It does look like it captured the area in the red box though. EDIT - I had to delete rain_reg.png and re-execute as it did not seem to overwrite the file with new captures. It's also noteworthy that while swipes and taps do seem to be in the proper position above, below, or to the sides of Rain, taps seem to register as swipes; ie when you step to the left, a swipe to the left is registered and Rain runs as far to the left as he can go.
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Jan 3, 2017 20:38:13 GMT
I forgot to mention before, but the current version you provided me did properly proceed from the Exploration menu though Next and Depart, wheras the previous build did not (or I wasn't patient enough to wait long enough for it to happen). So, here's rain_reg.png (yes, it is greyscale): Here are the log contents from 3 runs, all aborted after the script began trying to walk Rain around (though again, he always swipes instead of steps for me): App Screen size: 1440x2560 Task: maranda_coast_exploration Find Battle: true Dim: false Refill: false Swipe mode: 2 Step mode: 1 Lagx: 1.5 Tue Jan 3 14:50:22 2017 Next_i 0.94631445407867 Tue Jan 3 14:50:35 2017 Depart btn 0.99124050140381 Tue Jan 3 14:50:51 2017 Connection check Tue Jan 3 14:50:57 2017 Explore start Tue Jan 3 14:51:01 2017 Checking Rain#1 0.94201582670212 Tue Jan 3 14:51:11 2017 Checking Rain#2 0.94201582670212 Tue Jan 3 14:51:20 2017 Checking Rain#3 0.94201582670212 Tue Jan 3 14:51:29 2017 Checking Rain#4 0.94201582670212 Tue Jan 3 14:51:37 2017 Checking Rain#5 0.94201582670212 Tue Jan 3 14:51:46 2017 Checking Rain#6 0.94201582670212 Tue Jan 3 14:51:55 2017 Checking Rain#7 0.94201582670212 Tue Jan 3 14:52:04 2017 Checking Rain#8 0.94201582670212 Tue Jan 3 14:52:13 2017 Rain not found Tue Jan 3 14:52:16 2017 Going down 750ms Tue Jan 3 14:52:16 2017 Checking Rain#1 0.94201582670212 Tue Jan 3 14:52:30 2017 Checking Rain#2 0.94201582670212 Tue Jan 3 14:52:39 2017 Checking Rain#3 0.94201582670212 Tue Jan 3 14:52:47 2017 Checking Rain#4 0.94201582670212 Tue Jan 3 14:52:56 2017 Checking Rain#5 0.94201582670212 Tue Jan 3 14:53:05 2017 Checking Rain#6 0.94201582670212 Tue Jan 3 14:53:13 2017 Checking Rain#7 0.94201582670212 Tue Jan 3 14:53:22 2017 Checking Rain#8 0.94201582670212 Tue Jan 3 14:53:31 2017
App Screen size: 1440x2560 Task: maranda_coast_exploration Find Battle: true Dim: false Refill: false Swipe mode: 2 Step mode: 1 Lagx: 1.5 Tue Jan 3 15:14:16 2017 Next_i 0.94627559185028 Tue Jan 3 15:14:28 2017 Depart btn 0.99124050140381 Tue Jan 3 15:14:42 2017 Connection check Tue Jan 3 15:14:48 2017 Explore start Tue Jan 3 15:14:51 2017 Checking Rain#1 0.93754410743713 Tue Jan 3 15:15:02 2017 Checking Rain#2 0.93754410743713 Tue Jan 3 15:15:10 2017 Checking Rain#3 0.93754410743713 Tue Jan 3 15:15:19 2017 Checking Rain#4 0.93754410743713 Tue Jan 3 15:15:27 2017 Checking Rain#5 0.93754410743713 Tue Jan 3 15:15:36 2017 Checking Rain#6 0.93754410743713 Tue Jan 3 15:15:44 2017 Checking Rain#7 0.93754410743713 Tue Jan 3 15:15:53 2017 Checking Rain#8 0.93754410743713 Tue Jan 3 15:16:06 2017 Rain not found Tue Jan 3 15:16:09 2017 Going down 750ms Tue Jan 3 15:16:09 2017 Checking Rain#1 0.93754410743713 Tue Jan 3 15:16:23 2017 Checking Rain#2 0.93754410743713 Tue Jan 3 15:16:32 2017 Checking Rain#3 0.93754410743713 Tue Jan 3 15:16:40 2017 Checking Rain#4 0.93754410743713 Tue Jan 3 15:16:49 2017 Checking Rain#5 0.93754410743713 Tue Jan 3 15:16:57 2017 Checking Rain#6 0.93754410743713 Tue Jan 3 15:17:06 2017 Checking Rain#7 0.93754410743713 Tue Jan 3 15:17:15 2017 Checking Rain#8 0.93754410743713 Tue Jan 3 15:17:23 2017 Rain not found Tue Jan 3 15:17:26 2017 Going down 12000ms Tue Jan 3 15:17:26 2017 Step #1 of 13 Tue Jan 3 15:17:47 2017 Explore battle start Tue Jan 3 15:18:05 2017 autobtn 0.97871541976929 Tue Jan 3 15:18:10 2017 autobtn 0.9778693318367 Tue Jan 3 15:18:33 2017 Battle done: 1 Tue Jan 3 15:18:37 2017 Step #2 of 13 Tue Jan 3 15:18:40 2017 Step #3 of 13 Tue Jan 3 15:19:03 2017 Step #4 of 13 Tue Jan 3 15:19:26 2017 Step #5 of 13 Tue Jan 3 15:19:48 2017 Step #6 of 13 Tue Jan 3 15:20:11 2017 Step #7 of 13 Tue Jan 3 15:20:33 2017 Step #8 of 13 Tue Jan 3 15:20:55 2017 Step #9 of 13 Tue Jan 3 15:21:18 2017 Step #10 of 13 Tue Jan 3 15:21:40 2017 Step #11 of 13 Tue Jan 3 15:22:03 2017 Step #12 of 13 Tue Jan 3 15:22:25 2017 Step #13 of 13 Tue Jan 3 15:22:48 2017 Going left 7500ms Tue Jan 3 15:23:10 2017 Going down 1500ms Tue Jan 3 15:23:26 2017 Step #1 of 10 Tue Jan 3 15:23:35 2017 Step #2 of 10 Tue Jan 3 15:23:47 2017 Step #3 of 10 Tue Jan 3 15:23:59 2017
App Screen size: 1440x2560 Task: maranda_coast_exploration Find Battle: true Dim: false Refill: false Swipe mode: 2 Step mode: 1 Lagx: 1.5 Tue Jan 3 15:27:32 2017 Next_i 0.94627559185028 Tue Jan 3 15:27:44 2017 Depart btn 0.99124050140381 Tue Jan 3 15:27:59 2017 Connection check Tue Jan 3 15:28:05 2017 Explore start Tue Jan 3 15:28:09 2017 Checking Rain#1 0.93698692321777 Tue Jan 3 15:28:20 2017 Checking Rain#2 0.93698692321777 Tue Jan 3 15:28:28 2017 Checking Rain#3 0.93698692321777 Tue Jan 3 15:28:37 2017 Checking Rain#4 0.93698692321777 Tue Jan 3 15:28:46 2017 Checking Rain#5 0.93698692321777 Tue Jan 3 15:28:54 2017 Checking Rain#6 0.93698692321777 Tue Jan 3 15:29:03 2017 Checking Rain#7 0.93698692321777 Tue Jan 3 15:29:12 2017 Checking Rain#8 0.93698692321777 Tue Jan 3 15:29:21 2017 Rain not found Tue Jan 3 15:29:24 2017 Going down 750ms Tue Jan 3 15:29:24 2017 Checking Rain#1 0.93698692321777 Tue Jan 3 15:29:38 2017 Checking Rain#2 0.93698692321777 Tue Jan 3 15:29:47 2017 Checking Rain#3 0.93698692321777 Tue Jan 3 15:29:56 2017 Checking Rain#4 0.93698692321777 Tue Jan 3 15:30:04 2017 Checking Rain#5 0.93698692321777 Tue Jan 3 15:30:13 2017 Checking Rain#6 0.93698692321777 Tue Jan 3 15:30:22 2017 Checking Rain#7 0.93698692321777 Tue Jan 3 15:30:31 2017 Checking Rain#8 0.93698692321777 Tue Jan 3 15:30:39 2017 Rain not found Tue Jan 3 15:30:42 2017 Going down 12000ms Tue Jan 3 15:30:42 2017 Step #1 of 13 Tue Jan 3 15:31:02 2017 Explore battle start Tue Jan 3 15:31:20 2017 autobtn 0.97871541976929 Tue Jan 3 15:31:25 2017 autobtn 0.9778693318367 Tue Jan 3 15:31:47 2017 Battle done: 1 Tue Jan 3 15:31:52 2017 Step #2 of 13 Tue Jan 3 15:31:55 2017 Step #3 of 13 Tue Jan 3 15:32:17 2017 Step #4 of 13 Tue Jan 3 15:32:40 2017 I have to step away for a little while, but I should be back in about an hour.
|
|
|
Post by tinotk on Jan 3, 2017 22:47:48 GMT
Ok, can you try this version: www.dropbox.com/s/dx3bb4ambzikxdb/ffbet.zip?dl=0Hardcoded region coordinate instead of calculating based on screen sizes. Not sure why region is way off the center in your case. Can you run and let me know, also, let me know what it shows in the run.log file for App screen size, I'll have included a few extra vars. By the way, by default, if it couldn't find Rain it will automactially switch to swiping instead of clicking.
|
|
eleck
New Member
Posts: 20
|
Post by eleck on Jan 4, 2017 1:58:52 GMT
Ok, can you try this version: www.dropbox.com/s/dx3bb4ambzikxdb/ffbet.zip?dl=0Hardcoded region coordinate instead of calculating based on screen sizes. Not sure why region is way off the center in your case. Can you run and let me know, also, let me know what it shows in the run.log file for App screen size, I'll have included a few extra vars. By the way, by default, if it couldn't find Rain it will automactially switch to swiping instead of clicking. You've certainly corrected my issue! I just completed a flawless run. Here's the top of the log file: App Screen size: 1440x2560 r_x: 360 r_y: 640 r_w: 720 r_h: 1280: Task: maranda_coast_exploration Find Battle: true Dim: false Refill: false Swipe mode: 2 Step mode: 1 Lagx: 1.5 Tue Jan 3 19:48:05 2017 Next_i 0.94627559185028 Tue Jan 3 19:48:17 2017 Depart btn 0.99124050140381 Tue Jan 3 19:48:31 2017 Connection check Tue Jan 3 19:48:37 2017 Explore start Tue Jan 3 19:48:41 2017 Checking Rain#1 0.93742567300797 Tue Jan 3 19:48:52 2017 Checking Rain#2 0.93742567300797 Tue Jan 3 19:49:01 2017 Found Rain#2 0.93742567300797 Tue Jan 3 19:49:01 2017 Going down 750ms Tue Jan 3 19:49:03 2017 Checking Rain#1 0.93742567300797 Tue Jan 3 19:49:17 2017 Checking Rain#2 0.93742567300797 Tue Jan 3 19:49:26 2017 Found Rain#2 0.93742567300797 Tue Jan 3 19:49:26 2017 In retrospect, I do recall seeing a message on an earlier build after Rain failed to be found indicating that stepping had been disabled. For some reason I did not put two and two together. Now that this is functioning, I'm going to be jumping right into the fire and try creating a full path (all yellow resource nodes) for Dwarf Exploration. Thanks again!
|
|