Mooege- The Diablo 3 Emulator - Updated Master Compiles

[wetwlly]

Soo hows it going on the quests they working now or?

Not working on Quests, were working on connecting mooege to the retail client for the moment.
After that, we're brain storming.. we think we're going to have to make a secondary program to help us collect data from Diablo 3 to form a substantial database of information for Mooege to understand whats going on.

[allianz08]

Hi i was able to connect from the server using the given username and password.. my question is how to make my own account? or create new one?

[wetwlly]

Check out the wiki page (listed on the first page I believe). It shows how to make an account in Commands

[SerPiolo]

are there any news for emulation servers?

[kentattitude]

Thank's you

[LULzy]

omg you NOOB beggars, why do you still begging for D3 Beta emu not working? Get a guest pass, play the same as beta legally and where things actually work not static or fail animations, wait 1 month, play Starter without a guest pass legally or buy D3 if you're so big fan of D3 or wait for the far future for some emu, got damn it.

[warp08]

Hello !

The new 1.0.1.9558 D3 Client(final retail) is connecting to battle.net instead to the emu-server. The bnet.Patcher.exe for the new 9558 didnt help(wont work),it says the .dll is patched but the diablo3.exe is not looking to the 127.0.0.1 local host, they connect to battle.net and i can connect the my regular account. the old trick with the -launch -auroraaddress 127.0.0.1:xxxx did not work, and the bnet.Patcher.exe also didnt help.Sorry for my bad english.

[kristo1945]

Hello !

The new 1.0.1.9558 D3 Client(final retail) is connecting to battle.net instead to the emu-server. The bnet.Patcher.exe for the new 9558 didnt help(wont work),it says the .dll is patched but the diablo3.exe is not looking to the 127.0.0.1 local host, they connect to battle.net and i can connect the my regular account. the old trick with the -launch -auroraaddress 127.0.0.1:xxxx did not work, and the bnet.Patcher.exe also didnt help.Sorry for my bad english.

You can redirect the diablo to locahost by adding a line to hosts files (127.0.0.1 eu.actual.battle.net).The patcher refuses to patch my client, and the server never starts (some problems with MPQs i think)

[chaoticd35]

If you change your Config.ini file to this:

 Settings for Bnet server
[MooNet-Server]
BindIP =0.0.0.0
BindIPv6 = ::1
Port = 1345
MOTD = Welcome to mooege development server!

; Settings for game server
[Game-Server]
BindIP = 0.0.0.0
BindIPv6 = ::1
Port = 1999

to

 Settings for Bnet server
[MooNet-Server]
BindIP =127.0.0.1
BindIPv6 = ::1
Port = 1345
MOTD = Welcome to mooege development server!

; Settings for game server
[Game-Server]
BindIP = 127.0.0.1
BindIPv6 = ::1
Port = 1999

Mooege server will run.

[allianz08]

Hi again.. was able to find the command for creating new account..

!account add <email@> <password> <battletag> <owner|admin|gm|user> - Set user-levels for players

can anyone guide me what to set on battletag? and user level?

[warp08]

lol !

i sayed i have done all same as beta client, and also the 127.0.0.1 in all configs and Hosts.ini also. but didnt help, i think in the new D3 9558 Client the battle.net request is hardcoded and not over the -auroraadress 127.0.0.1:xxxx .
Is anybody here that runs Diablo retail 1.0.1.9558 over this Emu here ?
Pls, help !

[wetwlly]

I hope more people start quoting my posts because it never seems that people read them. (You should be reading all of my posts, for I am one of the project overseers of Mooege)

Retail does not run yet.. we have already updated parts of mooege to retail specs but its not everything to login. bnet patcher has been updated. and so has MadCow(which includes the patcher and the new hosts changer which is done instead of using auroraaddress)

I will be announcing on Twitter, Mooege's Forum, and possibly here once we are at a Full Release for retail, BUT in the meantime we aren't.

[volodia]

Hello guys, first of all thank you for creating a possibility to study this type of program security.
My situation is this - a clean beta downloaded brom Bnet. once started it says 0.11.0.9359 for a version. Also the latest MPQ in the dir is 9359. However when I select the executable in MadCow, it says the version is 9558, and the chain expects to get the 9558 MPQ. Is there a conflict and how can I solve it?
Thanks in advance.

#EDIT: I assumed that MadCow would recognise the version, download the needed patcher and run. But I needed to download madcow for 9359, modify a few things manually and then it launched. Just as an idea, maybe there could be a database of files which are needed to run all the different versions of d3, deDE, enUS, patch 20, patch 21 etc, and when running MadCow it would determine the clients version and fetch the needed files for this specific version?

[binhoscc]

Hello friends,
I think there is some problems with my Mooege Emulation..
I could get it to work normaly by following the instructions, but there is something wrong about Gold and Items droped..
Every creep that i kill it drops more than 2k gold and a lot of items (at the beggining of the game), i think that in the original D3 Beta it will not happen!
Anyone try to fix that?
This emulator is easier to play for every one? or just to me?
Thank you

[rips]

Hello,

I cant patching te client. I did excatly like in instruction and cant login



What is wrong ?

thanks

Now i got this message in d3




how to fix it