(08-20-2016, 07:59 PM)quickpurchase Wrote: confirmed.
If you want to use the command ["timeout"] it will need to be set to use lowpriority. Doesn't seem to work well with high or normal priority. Tested with a wind shard/crystal script with no set min or max start/end times.
Hey Devs, anyway this functionality can be added? or is it not possible? The timeout function is just too good. And with some HW (and most likely Stormblood's) node locations the max scan of 120 is not cutting it so we have to create multiple entries for single nodes. Adding timeout command to normal and high or increasing the max radius a bit should fix the issue.
EDT: However the maxtime command does work on highpriority and normal. But if you need to gather more than 3 that require you to move locations because the scan does not pick it up, you'll have a problem.