mooege diablo 3 patch 13

[maddogmiller15]

i cant get the gm commands to work with the newest version patch 13 some help would be wonderful

[wetwlly]

try using them from the Console, things like !item and stuff probably wont work for awhile, until Egris and the others figured out the rest of the fixes.

[maddogmiller15]

well some of the commands wont work in the console like !setlevel !spawn

[wetwlly]

Yeah.. things are still broken, as you can possibly see if you've been checking out the Network Graph, Egris and MDZ are working hard to get everything fixed up.. We're waiting on one of our other guys to reverse some things and fix em up, so that I can finally add it into my branch, so I can start fixing up some other things.. like skills and all the other things we've been working on.

[maddogmiller15]

i just downloaded the latest version made today 2/24/12 spawn is now correctly working butt !setlevel inst reason im asking is cause i love using later skills is there a way i can set levels another way or just wait for a new update ?

[wetwlly]

Commands work on a newer update, i think there is another update coming soon that will add in a working !levelup

using later skills is a problem, because only my branch has them and I cant seem to update my branch correctly to work with patch 13. it's going to take me some good amount of time to get my branch up-to-date.

[maddogmiller15]

okay thanks i know in patch 12 not all later skills where working correctly butt most did so keep up good work hope to see this fixed soon so i can get back to using blizzard hehe thanks

[Tester0815]

[Debug] [Game]: Unhandled exception caught: - [Exception] System.ArgumentExcepti
on: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boo
lean add)
   at Mooege.Core.GS.Common.InventoryGrid.AddItem(Item item, Int32 row, Int32 co
lumn)
   at Mooege.Core.GS.Players.Inventory.HandleInventoryRequestMoveMessage(Invento
ryRequestMoveMessage request)
   at Mooege.Core.GS.Players.Inventory.Consume(GameClient client, GameMessage me
ssage)
   at Mooege.Core.GS.Games.Game.Route(GameClient client, GameMessage message)
[Debug] [Game]: Unhandled exception caught: - [Exception] System.ArgumentExcepti
on: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boo
lean add)
   at Mooege.Core.GS.Common.InventoryGrid.AddItem(Item item, Int32 row, Int32 co
lumn)
   at Mooege.Core.GS.Players.Inventory.HandleInventoryRequestMoveMessage(Invento
ryRequestMoveMessage request)
   at Mooege.Core.GS.Players.Inventory.Consume(GameClient client, GameMessage me
ssage)
   at Mooege.Core.GS.Games.Game.Route(GameClient client, GameMessage message)




[Debug] [Server]: ReceiveCallback - [Exception] System.NullReferenceException: O
bject reference not set to an instance of an object.
   at Mooege.Core.GS.Games.GameManager.RemovePlayerFromGame(GameClient gameClien
t)
   at Mooege.Net.GS.ClientManager.OnDisconnect(Object sender, ConnectionEventArg
s e)
   at Mooege.Net.Server.OnClientDisconnect(ConnectionEventArgs e)
   at Mooege.Net.Server.RemoveConnection(Connection connection, Boolean raiseEve
nt)
   at Mooege.Net.Server.ReceiveCallback(IAsyncResult result)

Nullreferences should not happen. This is dirty programming. Check for null more often!

[Tester0815]

[Fatal] [MooNetClient]: OnTSLAuthentication() exception:  - [Exception] OpenSSL.Core.OpenSslException: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HEL
LO:no shared cipher
   at OpenSSL.SslStreamBase.EndRead(IAsyncResult asyncResult)
   at OpenSSL.SslStream.EndRead(IAsyncResult asyncResult)
   at OpenSSL.SslStream.EndAuthenticateAsServer(IAsyncResult ar)
   at Mooege.Net.MooNet.MooNetClient.OnTSLAuthentication(IAsyncResult result)

[wetwlly]

No idea about the first error, something with items (but thats fine since our item coding is messy anyways.. someone give us a hand ;P)

other error, just restart mooege, or log out and back in.. it happens. but shouldnt stop you from logging in. just ignores the error usually.