Quote:
|
Originally Posted by peterfopan
Hmm, it looks like i have a big bag of errors, here's my latest log, why so many errors?
|
The WARNINGs are not so concerning. In your case, the many of the ERRORs aren't either.
When there's a sound error, we usually just don't play the sound. Similarly for particles and emotes - we tend just not to show them and they tend not to be critical to gameplay.
When there's a room error about an invalid nav position, we just try to place the item somewhere more appropriate. When you see a couple of those, it took us multiple tries to find one that worked or we tried to put multiple things in the same place. I think. But if you got into the room as did all the NPCs and other clicky items that you needed, it's not a big deal.
UI errors may or may not be problematic. If you can see the UI you need, it's fine. Those vertbar things, for example, just mean we're trying to draw a healthbar outside its boundaries.
The SharedObject errors were pretty alarming to us when we first saw them but they don't seem actually to be causing problems.
I think the Combat errors about the cannons mean there was a timing thing. We tried to draw or fire or something a cannon probably just as it was destroyed.
In any case, you have no ERROR at the end of that log so you either logged out cleanly or the game crashed so badly it couldn't write the ERROR before it died.
One of the things we did in the next big update (1.1.x) was spend some time trying to clean up some of this log spam of warnings and errors. In most cases, that involved fixing whatever bug was generating the error. In some cases, though, it just meant not logging as ERRORs things that aren't a big deal or things that aren't a problem at all. So your logs from that build should be smaller and the info in them should be more helpful to us.
