Here's another item for the wishlist:
Would it be possible to have APBU check the URL when the 'Start' button is clicked?
I got a little impatient today after maintenance and tried to start it up before the gateway was back online and it locked out at http://gatewaysitedown.playneverwinter.com
Not a big deal to close it out completely and restart from scratch, but it would be nice if APBU could check and make sure it is at either the Character Select screen or http://gateway.playneverwinter.com/ before it starts. Possibly dependent on the setting of the 'AutoLogin' checkbox?
BaseN said this about it:
Not sure why that happens. It' quite possible that QtWebKit is caching the DNS resolve. In that case I can't do much. All the urls are pointing to the proper URL, but when the Gateway is going down for maintenance the DNS target of the gateway changes to redirecting to gatewayisdown. Apparently APBU does try to resolve again so it's constantly hitting that one. I will see if there is a way to fix this.
Thanks for the info, Darxide.
ok got it working wtf did I do? lol
ok now how do I get this to take each toon and invoke?
tommyboy69 you can't use this to invoke, this only uses the gateway to do professions.
From the gateway you can extend the invoke time through the adventure thingie but to do a real invoke you have to start the game afaik.
Is there update about refining AD ?
The apps crash without reasons.
Nom de l’application défaillante APBUltimate.exe, version : 0.0.0.0, horodatage : 0x530e9076
Nom du module défaillant : unknown, version : 0.0.0.0, horodatage : 0x00000000
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000016bebe803c0
ID du processus défaillant : 0x128c
Heure de début de l’application défaillante : 0x01cf66b769889fcc
Chemin d’accès de l’application défaillante : D:\APBUltimate\APBUltimate.exe
Chemin d’accès du module défaillant: unknown
ID de rapport : 0e1f71b6-d2ac-11e3-8090-50e5494198e4
Nom complet du package défaillant*:
ID de l’application relative au package défaillant*:Récipient d’erreurs 81656652221, type 5
Nom d’événement*: BEX64
Réponse*: Non disponible
ID de CAB : 0
Signature du problème :
P1 : APBUltimate.exe
P2 : 0.0.0.0
P3 : 530e9076
P4 : StackHash_9b71
P5 : 0.0.0.0
P6 : 00000000
P7 : PCH_02_FROM_ntdll+0x000000000009B13A
P8 : c0000005
P9 : 0000000000000008
P10 :
Fichiers joints*:
C:\Users\Julien\AppData\Local\Temp\WERD09F.tmp.WERInternalMetadata.xml
C:\Users\Julien\AppData\Local\Temp\WERDC39.tmp.appcompat.txt
C:\Users\Julien\AppData\Local\Temp\WERE15C.tmp.WERDataCollectionFailure.txt
Ces fichiers sont peut-être disponibles ici*:
C:\Users\Julien\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_APBUl timate.exe_f9912b3b73e0e8956456d5f65a5eee315b5627_5959b493_12c2e178
Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 0e1f71b6-d2ac-11e3-8090-50e5494198e4
Statut du rapport : 9
Récipient avec hachage*: 17a3f841c76face350635f52baede426
Is there a way to auto-start the program? A switch/parameter or does it have to be macroed? I'm getting bitten by the memory leak a lot and will even lock up my computer all together. If I could kill the program every 1-2 hours of operation, start it back up and "Start" the bot, it would help alleviate the program running too long and dying. This would also help recover from any page timeouts or situations where the bot just gets stuck on a screen. I will admit it's quite random because the bot could run 24 hours without problems and sometimes it'll start leaking and crashing after just an hour.
It seems to be very slow on collecting rewards. Like 4-5 try and sometimes on 8-9th try.
Also it tries to do stuff before the page is completly loaded and that makes it fail. It seems to be taking more time then the other bots I tried.
But even if it takes longer time I have to check and see if it crashes as often as the others and if it tries to reset when it gets stuck.
Hope you fix the load issue on the collect reward though because it sucks.
Thanks for all the great work.
Also it resets sometimes but do not continue off the login screen. Thus get stuck. I keep to infinite for now since that works better for now.
Lets wait until the patch comes and see how things work then. But you guys should really learn from eachother since Infinite works much better with tasks but have timeout issues that ultimate seems to reset off. Though ultimate get stuck at relog and infinite goes on after relog.
Perhaps do a merge and get a working product?
Infinite and Ultimate needs both timed "kill/restart" script on their current state. I did script what do that because I cant look my remote PC every hours and that PC also do crash several times per day so all Bots must be started automatic after reboot.
Script what does Bot kill/restart, will not take away bugs what they contain, but it make them work weeks or even months without user interactions... OFC, if Bot cant "AutoRefine ADs" its then quite useless left alone...
I still look Ultimate version what do "autorefine" and works efficiently with "short" jobs, there is two good reasons why stay with Greasemonkey or Infinite.
ps. Its good to add that multiple accounts suffers less one Bot failure than if you have one account with multiple character, but if Bot any way restart after one hour then only short jobs efficiency will suffers if bugs occurs.