[GWA2] (+ [OmniApi]) Update 2023 ?

Page 3 of 5 12 3 45
05/17/2024 15:46 aracno974#31
The 007 error is so fucking random...it's really weird...
05/17/2024 16:45 arahant#32
Quote:
Originally Posted by AlienMan9696 View Post
What Pvp zone are you trying to enter? That very well could have something to do with it. It's obviously a problem with headers then but not sure why you're receiving the error and I'm not. It will help me understand more If I know where you're trying to enter so I can go and try there myself.
Here's an example: I took the latest GWA˛ shared by Zilvereyes on this thread and created a bot that simply calls EnterChallenge and waits. I tested it in JQ, HA, and even PvE missions like Vizunah Square (Local Quarter).
05/17/2024 17:14 Marco9494#33
Quote:
Originally Posted by arahant View Post
Here's an example: I took the latest GWA˛ shared by Zilvereyes on this thread and created a bot that simply calls EnterChallenge and waits. I tested it in JQ, HA, and even PvE missions like Vizunah Square (Local Quarter).
It still performs the crash (007). Try codex and see
05/17/2024 17:18 arahant#34
Quote:
Originally Posted by Marco9494 View Post
It still performs the crash (007). Try codex and see
Of course it does. I just wrote this example to demonstrate that the EnterChallenge function causes the disconnect.
05/17/2024 17:22 Marco9494#35
I really can't figure out the problem, the header looks the same
05/17/2024 17:26 AlienMan9696#36
You’ve tried using different gwa2_headers as well? Or just the ones from this thread?
05/17/2024 17:28 Marco9494#37
the header should be the same on all gwa2 files, since it never changed. You found one that had a different header for enterchallenge()?
05/17/2024 17:40 Underavelvetmoon#38
Stephen from ArenaNet updated the wiki recently to say that Toolbox is permitted but ONLY outside of PvP lobbies, perhaps he has implemented some back end to combat PvP bots entering into a lobby? Not sure.
05/17/2024 17:53 Marco9494#39
Quote:
Originally Posted by arahant View Post
We're all using this header:

Code:
Global Const $HEADER_MISSION_ENTER = 0xA3
I would lean toward the header being broken, but if it works for some and not for others, it could also be OS-related. I'm using Windows 11.
It doesn't work for everyone, the enter is like random. 50% goes through, 50% fail :/

Quote:
Originally Posted by Underavelvetmoon View Post
Stephen from ArenaNet updated the wiki recently to say that Toolbox is permitted but ONLY outside of PvP lobbies, perhaps he has implemented some back end to combat PvP bots entering into a lobby? Not sure.
that's what I suspect as well.
05/20/2024 10:14 B u l l a#40
Well it doesnt only causes 007 in PvP Arenas. You can check every PvE Mission where it has the enter mission button. It causes also 007...
05/24/2024 11:57 gwbotcrazy123#41
Anyone can help for 007?
05/24/2024 15:51 apoguita#42
Quote:
Originally Posted by arahant View Post
Here's an example: I took the latest GWA˛ shared by Zilvereyes on this thread and created a bot that simply calls EnterChallenge and waits. I tested it in JQ, HA, and even PvE missions like Vizunah Square (Local Quarter).
for the ones figuring out about disconnect with code 007.

recently anti cheat added, it causes disconnects when sending packets from suspuciosly flagged accounts, it is more frequent in PvP areas but also happens in other server handling functions like pressing the "enter mission" button.

i had the same problem in my toolbox plugin, as time pases, this disconnects will be more frequent.

i have no idea if the issue can be debugged from AutoIt, most safe solution is stop using cTos msgs.

until Anet finish doing the backend changes they are doing i would refrain from entering any pvp area with a bot active.
05/24/2024 20:03 AlienMan9696#43
Quote:
Originally Posted by apoguita View Post
for the ones figuring out about disconnect with code 007.

recently anti cheat added, it causes disconnects when sending packets from suspuciosly flagged accounts, it is more frequent in PvP areas but also happens in other server handling functions like pressing the "enter mission" button.

i had the same problem in my toolbox plugin, as time pases, this disconnects will be more frequent.

i have no idea (most likely it cant) if the issue can be debugged from AutoIt, most safe solution is stop using cTos msgs.

until Anet finish doing the backend changes they are doing i would refrain from entering any pvp area with a bot active.

They must be flagging all brand new accounts brought from their store to then. I just bought a few different accounts all using different payment methods, emails and so forth. I still recieve the issue, do you have any proof of this being the actual problem?
05/24/2024 20:12 apoguita#44
Quote:
Originally Posted by AlienMan9696 View Post
They must be flagging all brand new accounts brought from their store to then. I just bought a few different accounts all using different payment methods, emails and so forth. I still recieve the issue, do you have any proof of this being the actual problem?
yes if you get caught sending forbidden packets you get flagged even if youre on a new account.

only anet have proof of that, but i have tested around 20 accounts and only the ones that ever used a bot had the problem.

removed cTos packets from my project and everything fixed itself.

you can test my proyect, first version has 007, last version dont

thats all the prof someone can give you.
05/24/2024 21:27 JimRaynerd#45
Quote:
Originally Posted by apoguita View Post
removed cTos packets from my project and everything fixed itself.
How does a non tech savy person tackle this?
Page 3 of 5 12 3 45