The line where is kicks you is RndSleep(GetPing() * 6). For me a multiplier of * 3 is usually quite stable, but I set to * 6 to try account for slower connections. If you increase that value to 8, 10, 12, 14... you should eventually reach a state where it doesn't kick you, but obviously each time you slow your script down a bit. If using with a bot though then that extra few seconds wont hurt
If people who test this can post which values are stable for them, that would be helpful, thanks!
I've tested multiple things so far and played around a lot with different timings, unfortunately without success. Even when there is a real long pause between salvaging items (3-4 sec or more), there will always be a point where it disconnects me. Especially if I'm salvaging whole stacks of items.
Quote:
Originally Posted by list comprehension
Yep, this is the best way to fix it in the current gwa2 available to the public. The 100% bullet proof way would be to hook the GameServer -> Client Decryption function to only move on when the client receives back the finished salvage packets like gwca does.
The big question is: how did gwca or toolbox implement it? Maybe someone with decent C++ knowledge can help?
This is a working CoF dungeon farm bot with a monk and 2 heros to clear the dungeon.
You will need DP removal Pcons like Four-leaf clovers or what you want.
Stuff is explained in the zip file
Cheers
I followed the file that explains in the zip and it still fails on the first group. Can you post your exact gear? I would like to see if I am misunderstanding something.
EDIT: It ended up being how the bot loaded heroes, I set them up backwards so the +3's were on the wrong hero. Now that I fixed that it is running smoother.
I've tested multiple things so far and played around a lot with different timings, unfortunately without success. Even when there is a real long pause between salvaging items (3-4 sec or more), there will always be a point where it disconnects me. Especially if I'm salvaging whole stacks of items.
The big question is: how did gwca or toolbox implement it? Maybe someone with decent C++ knowledge can help?
Toolbox is only using SendPackets. Obviously u cant do it just like that with GWA2.
Because if u send the packet your client is not prepared to accept the Server packets and it will crash or disconnect u with code 007.
So toolbox is just blocking the incoming packets for the salvaging and just reading the data from the packets and respond to them.
You can see it here:
I've tested multiple things so far and played around a lot with different timings, unfortunately without success. Even when there is a real long pause between salvaging items (3-4 sec or more), there will always be a point where it disconnects me. Especially if I'm salvaging whole stacks of items.
The big question is: how did gwca or toolbox implement it? Maybe someone with decent C++ knowledge can help?
Interesting, I don't have this issue when salvaging mods only, I usually don't salvage materials.
What func can I write to get a bot to pick up a bundle? Trying to fix the old SSLB Bot and it wont pick up the rune
One simple but not 100% certain way is to get to the nearest position of the tome. After that you can use the "targetNearestItem()", "ActionInteract()" and "DropBundle()" function.
As mentioned, it is not 100% certain, but it worked for me every time and i never had any problems with that.
Smart store: stores all usable items (tomes, pcons), materials, dyes, trophies, into storage, adding to existing stacks if possible. Full stacks and items where no stack was found will be placed into first available storage slot.
For now Smart Store does not give an option of which items to move or keep. This will probably come in next release.
It does however obey the $USE_BAGS, so if you dont want items in bag 4 moved then set $USE_BAGS = 3.
It is recommended to keep storage pane 1 open to easily see which items made full stacks and which didn't find stacks, to be able to rearrange items easily from there.
If there is something that you feel definitely needs to have an option to move/not move and putting things in bag 4 is not enough, please leave some feedback and I'll try to work it in.
Thank you very much for this, works fantastically and was very easy to integrate with other bots!
I'm having strange effects for some bots while the rendering is disabled.
CoF: keeps dying while render disabled. Sometimes the game crashes. Works perfectly when render enabled.
Vaetire: Foes don't drop any items while render disabled and crashes after a while. Also works perfectly when render enabled.
Kilroy, kabob & dragon moss: work fine with render enabled or disabled.
Im not sure if thats a problem of the render mechanism or the bot itself since it occures only on certain bots. Anyone had some similar observations?
I'm having strange effects for some bots while the rendering is disabled.
CoF: keeps dying while render disabled. Sometimes the game crashes. Works perfectly when render enabled.
Vaetire: Foes don't drop any items while render disabled and crashes after a while. Also works perfectly when render enabled.
Kilroy, kabob & dragon moss: work fine with render enabled or disabled.
Im not sure if thats a problem of the render mechanism or the bot itself since it occures only on certain bots. Anyone had some similar observations?
Some things don't update when rendering is disabled and has been a long term problem. Sometimes it is possible to get the values and actions from a different section of memory that does update while rendering is disabled. Best thing to do is to find what functions fail with rendering disabled and find alternatives or creative work arounds such as timers or other flags for each particular bot.
v1.1b Updated 08.16.20 (RiflemanX)
;~Updated GWA2 to current public version (Logicdoor/Zvend)
;~Adjustments made to outpost pathing to prevent getting stuck
Info:
Prior post has been updated
~RiflemanX
If the bot sells the items at the Merchant, nothing happens and the bot no longer reacts to anything.
Yeah noticed sometimes it would get stuck salvaging an item and just sit there, I ended up just putting a 2 minute timer on the salvage to exit if not done in that time to avoid that, hopefully with this new update it will not need that check .
Hello, any idea why the luxon bot don’t take the buff at the priest? There are 2 dialog to take it, but it stop at the first one and begin the VQ ?
I’m rank 2 luxon, already finished the game, in a Luxon guild ?
Thank you
You need to make sure that you have enough progress in the Luxon title to receive the blessing. Try completing Elder Rhea's mission and obtain 10,000 unspent points. "Elder Rhea will not consider you a friend of the Luxons until you prove your worth by doing tasks for the Luxons."
Befriending the Luxons
Given by Elder Rhea
in Cavalon
Objectives
Accumulate 10,000 unspent Luxon faction points.
See Elder Rhea for your reward.
Reward
10,000 Experience
700 Gold
Your Luxon faction cap limit is increased by 10,000 points
This increase is only applied once per account. To receive this reward, you must either complete the quest (if none of your characters has done so), or log in with a character in your account that has done the quest.
I've tested multiple things so far and played around a lot with different timings, unfortunately without success. Even when there is a real long pause between salvaging items (3-4 sec or more), there will always be a point where it disconnects me. Especially if I'm salvaging whole stacks of items.
The big question is: how did gwca or toolbox implement it? Maybe someone with decent C++ knowledge can help?
Quote:
Originally Posted by RiflemanX
You need to make sure that you have enough progress in the Luxon title to receive the blessing. Try completing Elder Rhea's mission and obtain 10,000 unspent points. "Elder Rhea will not consider you a friend of the Luxons until you prove your worth by doing tasks for the Luxons."
Befriending the Luxons
Given by Elder Rhea
in Cavalon
Objectives
Accumulate 10,000 unspent Luxon faction points.
See Elder Rhea for your reward.
Reward
10,000 Experience
700 Gold
Your Luxon faction cap limit is increased by 10,000 points
This increase is only applied once per account. To receive this reward, you must either complete the quest (if none of your characters has done so), or log in with a character in your account that has done the quest.
