[SOLVED]Failed to generate world with sno: 71150 ??? (mooege)

[itsmetoo]

SOLVED - See Posting #4

Hi there!

Since a lot of hours my mooege server runs fine.
So i can login, create my char and so on.
But if I click start and it starts to loading the world mooege tells me:

[05.04.2012 04:55:22.278] [Error] [WorldGenerator]: Can't find a valid world definition for sno: 71150
[05.04.2012 04:55:22.278] [ Warn] [Game]: Failed to generate world with sno: 71150
[05.04.2012 04:55:22.302] [Debug] [Server]: ReceiveCallback - [Exception] System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

google-translate:
"Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." = "Object reference not set to an object instance."
I'm using german windows 8 consumer Preview 8250 on 64 bit - mooege v1.8896.4471.36009 - Diablo 3 up-to-date on beta 8896 in german language.

After the message appears in CMD of mooege the loading screen of D3 is not freezed, but it loads and loads and loads and....loads... -.-"
So i have to exit D3.

I've been since hours in searching for an solution but i can't find anything about that.
Ok, some threads are about 71150, but unfortunately nothing helps me further.

Can you help me?

Thank you very much!


Greetz, itsmetoo


EDIT:
Something new i found just right now. Maybe that explains my problem???
Look here: https://github.com/raistlinthewiz/mo.../Games/Game.cs
At line: 134

this.StartingWorldSNOId = 71150; // FIXME: This must be set according to the game settings (start quest/act). Better yet, track the player's save point and toss this stuff.

I don't know what that means, but i can't play right now....still

[Fenris89]

I got exactly the same error(

[itsmetoo]

Hey Fenris89!

You got the german or an english version of the client?
I'm interested in that, so we could say it depends not in different languages of the client.

Greetz...

[itsmetoo]

Soooo, i got it - after days of reading in the internet about my problem!

It seems mooege needs the entire updates of before up-to-date Diablo 3 Beta!!!

So in this case you NEED "madcow" for it for downloading all needed MPQs!

If you start Madcow, go to "Help" and then check all boxes! (i didn't checked "client data" - don't ask me why ^_^)
After downloading, check if the MPQs there in the needed folder. (yes, you have to read about that where you copy them )

In MY SPECIAL case, i close madcow and start my mooege (Release_mooege-f092160) and let the server run. Now all MPQs will be read and tell you the server is ready.
Now just start D3 Beta (in my case Diablo 3 beta 8896 in german language!), login in and...YEAH...have fun!
NO 71150 failure anymore and WOHA....This Game Is GrEaT !!!

Thread solved !!!

Greetz, itsmetoo

[EchoX]

I don't think this is SOLVED!

I used madcow and synced both my game and mooege client to latest 9359. I can connect but cDiablo cleint hangs up forever on loading screen with this error on Mooege server!

Anyone has another idea? I've searched the codebase and as commented before, there is a FIXME tag mentioning save points or act numbers. Anyone knows where to get these?

[cyxxap]

Same error here. Bump

[terandolus]

Also here. MadCow MPQ`S doesent help.

[petter7252]

Madcow doesn't run on my system :S for some weird reason, so this is not a fix.

[beatnological]

Got same error. Nothing so far fixes it. If anyone has any other ideas pls share.

[filipko22]

Try to reinstall Diablo 3 using US Client. I got this error in GB version of Diablo 3, but after reinstalling to US version it worked fine.

[redzak]

Easy way to fix this if you are using madcow .. go to help and download mpq .. even if you have them all tick all and download this solved my problam