Sandbox for Legion Beta

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



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.

[moogletimes]

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

Firstly, WHAT? At least 10-11 of the last pages of this thread have been mostly filled with posts about people having issues with this exact problem. Almost everyone has the same exceptions id 7 & 5 error and it is currently THE TROUBLE that almost everyone is currently experiencing. Its a new issue that appeared with the 21691 version.

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.

Secondly, just out of interest, where would these .dat files be if they were created? in wow folder or sandbox folder? because there isnt one in either of these on my end.

[rovatok]

Hi King!

Any chance to get something with the win 7 issue?

[DavidTwo2009]

Anyone got a morph ID list or an updated teleportation list

[HAZJ]

Firstly, WHAT? At least 10-11 of the last pages of this thread have been mostly filled with posts about people having issues with this exact problem. Almost everyone has the same exceptions id 7 & 5 error and it is currently THE TROUBLE that almost everyone is currently experiencing. Its a new issue that appeared with the 21691 version.

Again, it's not related, these are all over the place even when everything it's ok, these exceptions just means that the server has no function in place to answer to these request, which are obviously not needed for the desired behaviour of the sandbox, as that's how it was coded.

Secondly, just out of interest, where would these .dat files be if they were created? in wow folder or sandbox folder? because there isnt one in either of these on my end.

They would be in the same place as you have the sandbox stored, which should be the wow beta root folder of course.