Greasy Fork

Stuck on leadership task (tries more than 3)

Anyone else suddenly seeing this? It runs for a bit, doing only 3 of each task.....then suddenly it gets stuck in a loop trying to add a fourth of that task over and over.

Seems a recent issue. Going to try and update script but I dont think it will help.

Nope, still goes through about 3-4 characters and then gets into a loop. Would prefer to not have to dictate each slot (and therefore create a profile for each task). Certainly strange.

Refresh the page without changing anything in settings, and bam, works fine.

I keep getting this too. It locks up the script. Looking at the console I keep getting this error when it does it. Not sure if it helps but:

"client.js?cb=1465483673000en:1 Uncaught TypeError: Cannot read property '_lastSeen' of null"

This happens to me lately as well. Not often, but enough to notice it when I look sometimes. As a workaround, it seems to help if you just manually insert a task. The script will then fill the remaining tasks just fine, at least for me. I know its not a fix, but its what I do for now.

It is happening to me as well, used to be infrequent but now it is difficult to get it to work long enough to process all toons without manual kicking.

I am coming to the thought that this is not 'lag' but intentional slowness.

Unrelated to this bug I noticed during the summer event I noticed a behavior that tracks with this theory. It was possible to do 2 different jobs during the summer fest, 1 producing sahha mats that didn't require a sunite, and 1 other that did. If I would finish a set and immediately go to the summer page it would often not have the same task available. Some few minutes later, it would reappear. There was no other discernible slowness, and other professions did not display this behavior when I tested.

With this problem I just now was able to observe a full set of refreshed jobs post server maintenance. On the first error due to a 4th duplicate being run I took over manually. I switched to the professions page and saw that the task (escort a wizards seneschal) was indeed still there. Within several seconds it disappeared from the page. I pushed play once again and all proceeded as normal.

This would be an easy way to flush out all those doing repeated jobs via a script. Especially one that repeats a standard number of retries. It would also be rarely seen by human users, due to the small times. If someone can come up with a job max counter to put into the mix.

I confirm the behavior noted by mystixa - the job still shows up in the list of available tasks often for at least 30 seconds, misleading the script to think it should still be selected.

I tried turning up the delay all the way to 3, the max setting. This did not fix the problem. Behaviour continued. I also thought I had found the place in the script code that controlled the number of retries, but apparently not.

If someone can find it, please report back. I would like to turn down the number of retries, preferably to 1. No real reason to keep hammering at this thing.

The same problem has been reported in another fork of this script on github.

I did work out a fix.. but its not perfect so Ill lead you to my notes on it in the following thread, and those who want to can implement a solution how they see fit.
https://greasyfork.org/en/forum/discussion/10210/x