Sandbox for Legion Beta

[rovatok]

It says:

{"inputs":[{"input_id":"account_name","label":"Battle.net email","max_length":320,"type":"text"},{"input_id":"password","label":"Password" ,"max_length":16,"type":"password"},{"input_id":"log_in_submit","label":"Log in to Battle.net","max_length":0,"type":"submit"}],"type":"LOGIN_FORM"}

Thats ok?

[rovatok]

In the earlier versions the connection patcher made changes the files in the ProgramData\Blizzard, Battlenet folder, the recent dosent. The problem is in the sandbox or in the client side what do you think?

[doityourself]

In the earlier versions the connection patcher made changes the files in the ProgramData\Blizzard, Battlenet folder, the recent dosent. The problem is in the sandbox or in the client side what do you think?

The new auth method doesn't need to make changes there.

[rovatok]

So there is no problem with the port, thats certain.

There is an agent.log perhaps it says something to you:

5/22 20:44:31.346 AgentCommunicator::Initialize(): uid = 'wow_beta'
5/22 20:44:31.346 Reading agent.dat file to determine agent port.

5/22 20:44:31.346 Reading agent.dat file to determine agent port.

5/22 20:44:31.346 Agent communicator initialized. Agent path: 'C:/ProgramData/Battle.net/Agent/Agent.exe' URL: '127.0.0.1'
5/22 20:44:50.420 Connecting to agent on port 1120
5/22 20:44:51.422 Starting agent, attempt 1
5/22 20:44:51.805 Reading agent.dat file to determine agent port.

5/22 20:44:51.805 WARNING: AgentConnection::Work() took 382.7295ms

5/22 20:44:51.828 Connecting to agent on port 1120
5/22 20:44:57.431 Starting agent, attempt 2
5/22 20:44:57.431 Reading agent.dat file to determine agent port.

5/22 20:44:57.431 WARNING: AgentConnection::Work() took 1.4533ms

5/22 20:44:57.441 Connecting to agent on port 1120
5/22 20:44:57.441 Successfully sent message 1 to agent
5/22 20:44:57.463 Received response. MSG 1, response code 200
5/22 20:44:57.463 Connecting to agent on port 1120
5/22 20:44:57.473 Successfully sent message 16 to agent
5/22 20:44:57.473 Received response. MSG 16, response code 200
5/22 20:44:57.473 Connecting to agent on port 1120
5/22 20:44:57.491 Successfully sent message 10 to agent
5/22 20:44:57.502 Received response. MSG 10, response code 200
5/22 20:44:57.502 Connecting to agent on port 1120
5/22 20:44:57.502 Successfully sent message 12 to agent
5/22 20:44:57.522 Received response. MSG 12, response code 200
5/22 20:44:57.522 Connecting to agent on port 1120
5/22 20:44:57.522 Successfully sent message 15 to agent
5/22 20:44:57.540 Received response. MSG 15, response code 200
5/22 20:44:57.540 Connecting to agent on port 1120
5/22 20:44:57.540 Successfully sent message 12 to agent
5/22 20:44:57.558 Received response. MSG 12, response code 200
5/22 20:44:57.558 Connecting to agent on port 1120
5/22 20:44:57.576 Successfully sent message 15 to agent
5/22 20:44:57.586 Received response. MSG 15, response code 200
5/22 20:44:57.586 Connecting to agent on port 1120
5/22 20:44:57.586 Successfully sent message 14 to agent
5/22 20:44:57.605 Received response. MSG 14, response code 200
5/22 20:44:57.605 Connecting to agent on port 1120
5/22 20:44:57.615 Successfully sent message 10 to agent
5/22 20:44:57.615 Received response. MSG 10, response code 200
5/22 20:44:57.615 Backfill complete, detaching from agent.
5/22 20:44:57.638 Connecting to agent on port 1120
5/22 20:44:57.647 Successfully sent message 2 to agent
5/22 20:44:57.647 Received response. MSG 2, response code 200
5/22 20:45:17.397 AgentCommunicator::Shutdown()


Have you any hint where the connection goes wrong?

[rovatok]

Perhaps Win 7 cant handle the 1120 (used by the agent) and the 8000 ports at the same time?

[woxwalt]

tried the sandbox on a win10 virtual environment (vbox) on my win7 host-system

no error, connection established on the first try. unplayable of course because there is only gpu.emulation activ.
my guess is there´s some code missing on win7 (dotnet or some library-shit).

[doityourself]

Could u try this: Zippyshare.com - Arctium WoW Legion Sandbox.exe

there should be a file created named debug.txt after your disconenct error

[rovatok]

Could u try this: Zippyshare.com - Arctium WoW Legion Sandbox.exe

there should be a file created named debug.txt after your disconenct error

I started, but no txt were created.

I searched the whole legion folder.

[doityourself]

I started, but no txt were created.

no debug.txt after you tried to login?

[rovatok]

No. Not in the sandbox folder, not in the core folder and either in the log folder.
I tried two times both with wowb_patched and with patched 64 exes.

[nanoneo]

no debug.txt for me aswell

[semedimais]

Hey king48488 there is a method for add npcs?

[doityourself]

Hey king48488 there is a method for add npcs?

!addnpc #id maybe?

[nanoneo]

Hey semedimais there is a method for making this Sandbox work for me?


Your Asking questions i Wish i Could ask


How did you get it to work?

[semedimais]

!addnpc #id maybe?

Yeah but i was thinking if is possible to start the sandbox with npcs

Hey semedimais there is a method for making this Sandbox work for me?


Your Asking questions i Wish i Could ask


How did you get it to work?

I just followed instructions. Yesterday i had problems but with the new sandbox i solved. I deleted cache, wtf and patched the WowB-64.exe, i set in config.wtf "SET portal "127.0.0.1:8000"" and i had login. I'm using W10 enterprise x64 (sorry for my bad english)

[xJamal]

Yeah but i was thinking if is possible to start the sandbox with npcs



I just followed instructions. Yesterday i had problems but with the new sandbox i solved. I deleted cache, wtf and patched the WowB-64.exe, i set in config.wtf "SET portal "127.0.0.1:8000"" and i had login. I'm using W10 enterprise x64 (sorry for my bad english)

The problem is only for Windows 7 . King any chance to get update for Win7 or ?

[rythualdj]

not debug.txt for me neither

[hurrikaine]

I am still having trouble with "Got unhandled method id for '7' for 'ConnectionService'
Windows 10 x64

[moogletimes]

I'm having the same issue. My WoW client is patch 21737 and ive downloaded the latest sandbox version. Ive tried patching both the 32bit and the 64bit client and none of the patched versions let me login. I just get the same "Got unhandled method id for '7' for 'ConnectionService'" error.

Attachment 25844

I have checked out the resource monitor and it shows me that the sandbox is a ipv4loopback local adress with 8000 on local port and 61909 on remote port. WoWB-64_Patched.exe shows same ipv4loopback local adress but 61909 on local port and 8000 on remote port. So the port is correct.
But i still havent figured out what could be the issue. I've added both applications to firewall exception in advanced settings to keep all ports open on both of em and ive disabled windows defender. Closed every other program that exists on this pc and only have the sandbox, wow, notepad, chrome and resource monitor up. Restart fixed nothing, run as admin fixes nothing. This link https://127.0.0.1:8001/login/?app=wow shows exactly what you said it would.

I just went back to Windows 7 x64 last weekend because Windows 10 was causing me issues with bluetooth and the battle.net agent among others. There is absolutely no way im going back to Windows 10 now. Seeing as some people have the same issue as me but on Windows 10, i guess its not exclusive to windows 7. I can share more files if you want.

[HAZJ]

Neither exceptions (id 5 & 7) are related to the troubles everyone are experiencing.

I have everything running under Win10 x64 and just checked on Win7 x64, Win8 x64 and Win8.1 x64 machines. I'd recommend to delete all generated *.dat files (data.dat, spawndata.dat specifically), every sandbox file and try again, also be sure about your Config.wtf is well set and you should have everything working.

There's no workaround.