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

[aracno974]

The 007 error is so ******* random...it's really weird...

[arahant]

Originally Posted by AlienMan9696

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).

[Marco9494]

Originally Posted by arahant

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

[arahant]

Originally Posted by Marco9494

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.

[Marco9494]

I really can't figure out the problem, the header looks the same

[AlienMan9696]

You’ve tried using different gwa2_headers as well? Or just the ones from this thread?

[Marco9494]

the header should be the same on all gwa2 files, since it never changed. You found one that had a different header for enterchallenge()?

[Underavelvetmoon]

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.

[Marco9494]

Originally Posted by arahant

We're all using this header:

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 :/

Originally Posted by Underavelvetmoon

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.

[B u l l a]

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...

[gwbotcrazy123]

Anyone can help for 007?

[apoguita]

Originally Posted by arahant

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.

[AlienMan9696]

Originally Posted by apoguita

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?

[apoguita]

Originally Posted by AlienMan9696

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.

[JimRaynerd]

Originally Posted by apoguita

removed cTos packets from my project and everything fixed itself.

How does a non tech savy person tackle this?