I forgot. There is also Russian gateway support. This needs testing.
I forgot. There is also Russian gateway support. This needs testing.
So far it seems faster than the old version.
Any chance you will be adding refining soon?
I'd suggest running the script RottenMind has made. It takes care of the bugs quite easily. That in conjunction with APBU or APBi works quite nicely.
AD Refining would make this a complete bot, in my mind. Anything else would be a bonus.
I will wait patiently, as long as it takes. I don't mind having to stop the bot once per day to refine manually. Takes 2 minutes. APBU is still the best option for the NW Gateway by far.
AD refining is the next thing to add.![]()
Bot get lost in a loop to start a new task if we start it ourself during the "starting new task".
It keeps thinking that slot is empty when it's not.
I'll try to provide more details about this if needed.
Any reports should be accompanied by a log. That's why the log is there.
No action should be taken manually by a player while the APBU is running. That can and will interfere with the logic.
So the second part is not a bug. For the first part, of it being stuck in a loop, I need to see a log.
Do you mean that no action should be taken manually by the player within APBU itself or that no action should be taken on the character at all?
I am assuming that you mean the former since I interact with all my toons manually every day from inside the game client (refining, collecting rewards, starting new tasks, etc.) while APBU is running and I haven't suffered any problems. Just want to make sure that I'm not potentially getting into a bad habit that will cause issues in the future.
I'm off now to play with optional assets and re-allocate all of those lower tier guys that I was gonna get around to upgrading "one of these days"![]()
Yes, I mean that once you press start you should not manually do anything on the browser window. If you want to do something manually from APBU's browser, stop it, log in and do it
Any manual actions once it has started, can cause APBU's logic functions not to find things it expects to find when it expects to find them, causing unpredictable behavior, from freezing to messing up your queues.
Is there a way to determine which asset APBU will choose for the non-optional slot in the task?
I have a toon running leadership on 6 slots. 3xFight Off Spellplagued & 3xBattle Undead. All slots were running with Footmen. As soon as I updated to 0.4.1b, I sent 6 Guards to the toon and set APBU to run all tasks with a Guard in the first optional slot. But apparently APBU wants to use a Guard in the non-optional slot for Battle Undead and threw those tasks into a bit of a tizzy. I was able to straighten it out by setting it to use Footmen in the option slot, but this has me scratching my head going forward. Does APBU always choose the lowest tier asset available for the non-optional slot? I seem to recall it using the highest quality asset first when a combination of Uncommon, Rare, & Epic assets are present.
Can someone chime in on how APBU picks what assets to use and if there is a way to force it to use what the player prefers?
APBinfinite works better in my opinion. Only thing it is missing is a kill/restart switch that works if the tasks get stuck due to lag from gateway.
Ultimate takes way to long to finish collecting and starting jobs. With 5-10 chars it might work good but with 50 chars it works terrible.
Just my 5 cents.
I didn't explain properly. The issue is that APBU did NOT do what you are saying it was supposed to do.
Toon has 6 slots available. Set to run 3 x Fight Off Spellplagued (Slots 1-3) and 3 x Battle Undead (Slots 4-6). Running fine under 0.3.9 with 6 Footmen. Updated to 0.4.1. Running fine with 6 Footmen. Sent 6 Guards to use in option slots. Redid Professions configuration. Slots 1-3 loaded Fight Off Spellplagued fine using 1 Footman and 1 Guard each. Slot 4 loaded Battle Undead using 2 Guards. Tried to load slot 5 and failed because it used the only remaining Guard in Required Asset spot and had only 3 Footmen for option spot instead of Guard I had specified. Multiple timeouts, relogged, over and over.
I was able to work around this by changing the optional asset for slots 4-6 to Footman. APBU now automatically selects a Guard for the required asset spot and puts a Footman in the optional spot.
I would include the log for this, but the log does not show these details, just the fact that it is timing out when starting the task.
Obviously, this is not a huge issue since it is easily worked around. It's just that it was contrary to what I expected and thought I understood about how APBU works.