#I am get an error null in client reading packet
8 messages · Page 1 of 1 (latest)
Ah I see the ServerManager logging was actually changed and not the ClientManager logging. If you open the ClientManager.cs line 634 and change it printing e.Message to simply e you should be able to see the full exception and be able to trace its source
Yep, that looks like the line
A las question, When i compile, i see that directive DEVELOMENT is disabled, here is a way to let enabled when compiles?
It should depend on whether you have development mode enabled or not in your build