APB Ultimate

[bankinobi]

Can you change the RU gateway site to English language? If yes then I can just add the Russian gateway and APBU will work as is.

Edit: Because the problem is that I can not maintain strings in different languages nor can I hunt down issues that are due to other languages. Someone else manually patching the strings is not cool either as people would have to download from third party and I can not guarantee the safety of APBU in that case. Anyone could just claim translated version and pack malware on it so that's out of the question.

The normal gateway site can be used in different languages so I beieve the Russian one should also be able to switch to English.

No, RU gateway only with Russian language, and you can't change it.

[electropica]

I have speak about workers to earn time.
Few days ago i had 8 workers not used and it took me few days to see it...

I got this after the 1st start this morning.

07:14:08: Checking slot 6.
07:14:09: Slot 6 is Finished. Collecting Reward.
07:14:22: Checking if slot 6 is now Free.
07:14:28: Slot 6 is Free.
07:14:32: Starting new task on slot 6.
07:14:56: Timeout. Retrying.
07:16:20: Timeout. Retrying.
07:16:57: Timeout. Retrying.
07:17:34: Timeout. Retrying.
07:18:12: Timeout. Retrying.
07:18:13: Max timeout reached. Stopped.
07:18:13: Stopping. Please Wait!
07:18:13: Stopped! Timeout while starting new task after Finished

and an other one. But i turn to "relog" and it looks to help a bit

07:45:24: Slot 3 is Free.
07:45:28: Starting new task on slot 3.
07:45:47: Adding task timed out. Retrying!
07:46:06: Adding task timed out. Slot is in First Possible Mode, switching to next task.
07:46:25: Adding task timed out. Retrying!
07:46:44: Adding task timed out. Slot is in First Possible Mode, switching to next task.
07:47:03: Adding task timed out. Retrying!
07:47:22: Adding task timed out. Slot is in First Possible Mode, switching to next task.
07:47:41: Adding task timed out. Retrying!
07:48:19: Timeout. Retrying.
07:48:56: Timeout. Retrying.
07:49:34: Timeout. Retrying.
07:50:11: Timeout. Retrying.
07:50:12: Max timeout reached. Option set to Relog, waiting for 120secs before relogging

I have 9 tasks with "first possible top -> bottom" mode with a "move to next" in the settings.
So why is it doing this ?

edit : i have check APBI conf and it's 10 retry with a relog to the gateway.
I have put this in APBU.

[Darxide23]

Tailoring and Weaponsmithing are all that's left for the profession data files. I'll finish those in the morning and post all of them.

[alklas]

hello there
i still have issues with leadership, with version 0.3.3b, i have timeouts while starting new tasks.

here is the log :

08:04:07: Logging in.
08:04:14: Please enter your One Time code.
08:04:16: Please enter your One Time code.
08:04:18: Please enter your One Time code.
08:04:20: Please enter your One Time code.
08:04:22: Please enter your One Time code.
08:04:24: Please enter your One Time code.
08:04:26: Please enter your One Time code.
08:04:28: Please enter your One Time code.
08:04:30: Please enter your One Time code.
08:04:32: Please enter your One Time code.
08:04:46: Waiting for Character Select to load...
08:04:46: Switching to character -----
08:04:50: Checking slot 1.
08:04:51: Slot 1 is Running.
08:04:51: Checking slot 2.
08:04:52: Slot 2 is Running.
08:04:52: Checking slot 3.
08:04:53: Slot 3 is Running.
08:04:53: Checking slot 4.
08:04:54: Slot 4 is Running.
08:04:54: Checking slot 5.
08:04:55: Slot 5 is Running.
08:04:55: Checking slot 6.
08:04:59: Slot 6 is Free. Starting new task.
08:05:18: Adding task timed out. Retrying!
08:05:37: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:05:56: Adding task timed out. Retrying!
08:06:15: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:06:35: Adding task timed out. Retrying!
08:06:54: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:07:10: New task started.
08:07:10: Switching to character ----
08:07:13: Checking slot 1.
08:07:14: Slot 1 is Finished. Collecting Reward.
08:07:27: Checking if slot 1 is now Free.
08:07:34: Slot 1 is Free.
08:07:38: Starting new task on slot 1.
08:07:57: Adding task timed out. Retrying!
08:08:19: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:08:38: Adding task timed out. Retrying!
08:08:57: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:09:16: Adding task timed out. Retrying!
08:09:35: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:09:51: New task started.
08:09:51: Checking slot 2.
08:09:52: Slot 2 is Finished. Collecting Reward.
08:10:05: Checking if slot 2 is now Free.
08:10:12: Slot 2 is Free.
08:10:17: Starting new task on slot 2.
08:10:33: New task started.
08:10:33: Checking slot 3.
08:10:34: Slot 3 is Finished. Collecting Reward.
08:10:47: Checking if slot 3 is now Free.
08:10:54: Slot 3 is Free.
08:10:58: Starting new task on slot 3.
08:11:14: New task started.
08:11:14: Checking slot 4.
08:11:15: Slot 4 is Finished. Collecting Reward.
08:11:28: Checking if slot 4 is now Free.
08:11:35: Slot 4 is Free.
08:11:39: Starting new task on slot 4.
08:11:55: New task started.
08:11:55: Checking slot 5.
08:11:56: Slot 5 is Finished. Collecting Reward.
08:12:09: Checking if slot 5 is now Free.
08:12:15: Slot 5 is Free.
08:12:19: Starting new task on slot 5.
08:12:38: Adding task timed out. Retrying!
08:12:57: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:13:16: Adding task timed out. Retrying!
08:13:35: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:13:54: Adding task timed out. Retrying!
08:14:13: Adding task timed out. Slot is in First Possible Mode, switching to next task.
08:14:29: New task started.
08:14:29: Checking slot 6.
08:14:31: Slot 6 is Finished. Collecting Reward.
08:14:44: Checking if slot 6 is now Free.
08:14:51: Slot 6 is Free.
08:14:55: Starting new task on slot 6.
08:15:14: Adding task timed out. Retrying!
08:15:38: Timeout. Retrying.
08:16:17: Timeout. Retrying.
08:16:54: Timeout. Retrying.
08:17:31: Timeout. Retrying.
08:17:32: Max timeout reached. Stopped.
08:17:32: Stopping. Please Wait!
08:17:32: Stopped! Timeout while starting new task after Finished

[Darxide23]

So why is it doing this ?

08:14:55: Starting new task on slot 6.
08:15:14: Adding task timed out. Retrying!
08:15:38: Timeout. Retrying.
08:16:17: Timeout. Retrying.
08:16:54: Timeout. Retrying.
08:17:31: Timeout. Retrying.
08:17:32: Max timeout reached. Stopped.
08:17:32: Stopping. Please Wait!
08:17:32: Stopped! Timeout while starting new task after Finished

They both just look like the Gateway crapping out. It's been bad lately. It's not a problem with the bot.

[Rhendanwan]

Open a command prompt and do a "tracert gateway.playneverwinter.com" and paste the output of traceroute here.

this?


1 <1 ms <1 ms <1 ms
2 19 ms 19 ms 19 ms
3 18 ms 20 ms 22 ms
4 23 ms 30 ms 22 ms
5 24 ms 202 ms 204 ms

6 36 ms 28 ms 30 ms

7 42 ms 48 ms 34 ms

8 40 ms 40 ms 79 ms

9 304 ms 332 ms 76 ms

10 84 ms 59 ms 93 ms

11 141 ms 128 ms 130 ms

12 152 ms 128 ms 160 ms

13 127 ms 155 ms 128 ms

14 127 ms 128 ms 134 ms

[BaseN]

@electropica/alklas: It is what Darxide23 said. Gateway is not responding see:

08:14:55: Starting new task on slot 6.
08:15:14: Adding task timed out. Retrying!

That's 19 seconds spent waiting for the page with the start button for the task to load but it never happened. Subsequent retries which reload that url also failed. Means gateway is crapping out. These situations are outside my control. Relog on timeout option will keep the bot running though as it will keep relogging until gateway starts replying properly again. The relog option is the only true defense against overloaded/crapping out gateway or bad network conditions (it could be that your route to the gateway is not clean..meaning some router between you and the gateway.playneverwinter.com is eating packets for a brief duration--see answer to Rhendanwan below).

@Rhendanwan:
See hops: 5 and 9:

4 23 ms 30 ms 22 ms
5 24 ms 202 ms 204 ms

6 36 ms 28 ms 30 ms

and

8 40 ms 40 ms 79 ms

9 304 ms 332 ms 76 ms

10 84 ms 59 ms 93 ms

On the first example, hop 5 is in the range of 20-30ms. for a network packet to go through but you see out of 3 packets sent only the first packet took 24ms. The other two packets did 202 and 204ms. This shows an unstable router in your routing to the gateway. This particular router is probably dropping packets entirely everynow and then causing you timeouts. Subsequent traceroutes may at some point show asterisks instead of ms values which means dropped packet. When that happens you have no connection to the gateway as packets are being dropped.
Hop 9, also shows the same thing, normal range for that hop is 40-90ms yet 2 packets return with 304ms and 332ms. Since hop 9 is after hop 5 and packets go through hop 5 to reach 9, it may as well be that hop 5 is causing the issue you see on hop 9 as well (packets sent to 9 are delayed at 5) or it's also possible that 9 is also misbehaving (5% chance on that -- usually there's only one point of failure).
Unfortunately this is the nature of the internet and large WAN type networks in general, routers can misbehave, malfunction or go under a DOS attack..usually these things are addressed fast enough by the administrators of the routers. But if you see the issue continuing then you should copy/paste several traceroutes and email your ISP about it, attaching them to you emails, so they can apply some pressure to the admins of said routers in order to fix them. Usually the first hops are in your ISP's network (you can see that from the DNS names/IP addresses on those hops. If 5 is a router that belongs to your ISP they are responsible for it and should fix it themselves and you may as well pester them right now about it.

[packetlossc]

@electropica/alklas: It is what Darxide23 said. Gateway is not responding see:


That's 19 seconds spent waiting for the page with the start button for the task to load but it never happened. Subsequent retries which reload that url also failed. Means gateway is crapping out. These situations are outside my control. Relog on timeout option will keep the bot running though as it will keep relogging until gateway starts replying properly again. The relog option is the only true defense against overloaded/crapping out gateway or bad network conditions (it could be that your route to the gateway is not clean..meaning some router between you and the gateway.playneverwinter.com is eating packets for a brief duration--see answer to Rhendanwan below).

I actually had this issue today on one out of 4 accounts I had the bot running on. I doubt it's a router/packetloss issue as 3 worked fine and it did present the login page repeatedly on the 4th one.

Interestingly enough, hitting stop and having it try to login did not work (it brought up the login page but failed to login). I had to close the application, relaunch and then it worked.

Is there perhaps something additional that can/needs to be done to completely flush a url before attempting a relogin (i.e. closer to closing out the application and relaunching)? I did try it 3 times and all 3 times it failed to login (despite it loading up the login page) before I just closed the app and relaunched.

I guess what I'm saying is this is very likely a GATEWAY issue, but the regular autologin doesn't seem to fix it, rather you need to reload the app. Perhaps there is a way around requiring that you relaunch the app.

[BaseN]

Well it's not a APBU issue for sure. An APBU issue would constitute not retrying, or retrying the wrong thing. As long as log shows a huge timeout in seconds with subsequent retries failing it is either a gateway or a network conditions issue. That's 2000% certain.

Now regarding the relogin matter. That's entirely unrelated with the issue these guys were experiencing. To further elaborate:
What happens when you timeout and relogin is that the browser loading is stopped, the session is dropped, initial SSL login page is loaded, same worker thread sleeping method for x seconds then the equivalent of pressing the start button is done. IF this process fails it could be only because of one reason which I'll explain.

There are two conditions that can trigger the relog:
a) After timeout when the option is set to relog.
b) When gateway just killed your session.

Option a should never fail to relog. And I say should because being absolute about anything is stupid (although the first paragraph of this post is absolute lol)

Now option b, relies on me detecting when that happens and effectively escaping all loops and conditional flags so I can trigger the relog procedure. This is possible to fail if I have missed a location in the logic where this may happen and have not handled it properly. This is what happened to you. If login fails it is only because some loop is still running and the main thread is stuck at doing that so it never processes the signal fired to relog (prssing the start button will not work either for the same reason). In order for me to fix this I need the log where this happened so I can locate where in the code this situation is not handled properly. That's it.

Notice that this b situation is not handled at all on APBI. This is when APBI just gets stuck on retrying. The difference in the code and web browser engine is what makes APBU showing the login page, showing you exactly what happened (dropped session) while APBI just gets stuck.

EDIT: Have in mind gateway is currently having serious issues. If you try to login in the game via the client you will see this:

The website is experiencing technical difficulties. Normal game play is not affected.

[electropica]

Here is tracert.

1 <1 ms <1 ms <1 ms
2 7 ms 6 ms 6 ms
3 9 ms 9 ms 8 ms
4 13 ms 10 ms 11 ms
5 12 ms 11 ms 11 ms
6 17 ms 20 ms 19 ms
7 19 ms 20 ms 19 ms
8 17 ms 17 ms 18 ms
9 17 ms 18 ms 18 ms
10 18 ms 17 ms 17 ms
11 18 ms 21 ms 21 ms
12 23 ms 23 ms 23 ms
13 40 ms 23 ms 24 ms
14 92 ms 92 ms 92 ms ae3.cr1.lga5.us.above.net [64.125.21.205]
15 141 ms 112 ms 104 ms xe-2-1-0.mpr3.bos2.us.above.net [64.125.24.105]
16 99 ms 102 ms 100 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
17 110 ms 106 ms 108 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
18 125 ms 109 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
19 109 ms 109 ms 108 ms gateway.playneverwinter.com [208.95.185.59]

[BaseN]

Here is tracert.

That's clean. In your case it's just gateway crapping out.

[alklas]

the issue i see is that on the same computer, i have 5 APBI running fine, and 3 APBU doing timeouts...
so for now, the new is not yet better than the old one.

[Methuselas]

I'm actually curious as to which jobs you guys are running, 'cos I'm having the exact OPPOSITE effect. APBI is timing out constantly, but APBU isn't. I'm running all long leadership jobs, except one toon and the only thing he's running different is artificing, 'cos I can't run either bot to do alchemy. I never get timeouts with APBU and if I did, the bot resets, but I'm still getting timeouts and java script errors causing timeouts with APBI.



EDIT - Found this on the Launcher, when I was patching the new updates.

The website is experiencing technical difficulties. Normal game play is not affected.

I wonder if there's some under the hood stuff they've been meaning to do and are still working on it?

[BaseN]

Well I also see APBI doing timeouts as well, non-recoverable ones (stuck on retrying..funny you are not getting that..maybe because you restart them very often due to the leak?).

While APBU always recovers on my network with relog option set I had not have it failing once. If I had I would have fixed what caused it. But thing is APBU is not failing for me..Today I had my two instances running. a 0.2.x version for 5 days failing due to gateway shutting down. So unless you show me a log showing something other than a timeout caused by the gateway or network conditions I can not do anything about it. I can not fix something what I can not reproduce. This is why I keep leaving older versions running for as long as they can so I can see if they fail, how they fail and where.

Since you are not using the relog feature, try setting the timeout value to 10 until I separate the option for the internal loops. But that is still not going to do anything if gateway is not responding.

I'll upload another version in a bit that adds additional logging to the part you are failing and we'll see exactly what's going on.

[packetlossc]

There are two conditions that can trigger the relog:
a) After timeout when the option is set to relog.
b) When gateway just killed your session.

Option a should never fail to relog. And I say should because being absolute about anything is stupid (although the first paragraph of this post is absolute lol)

Now option b, relies on me detecting when that happens and effectively escaping all loops and conditional flags so I can trigger the relog procedure. This is possible to fail if I have missed a location in the logic where this may happen and have not handled it properly. This is what happened to you. If login fails it is only because some loop is still running and the main thread is stuck at doing that so it never processes the signal fired to relog (prssing the start button will not work either for the same reason). In order for me to fix this I need the log where this happened so I can locate where in the code this situation is not handled properly. That's it.

I have seen "disconnected from the gateway" messages periodically in the past with APBI so I'm guessing then that it was b. Next time I see it, I will try manually enter in the login information and clicking on the buttons on the browser session. I'm guessing it should work if the issue you listed above is what is causing it to fail to log back in for option b.