aboutsummaryrefslogtreecommitdiff
path: root/src/server/shared/Logging/Log.cpp
diff options
context:
space:
mode:
authorclick <click@gonnamakeyou.com>2015-03-08 07:47:17 +0100
committerclick <click@gonnamakeyou.com>2015-03-08 07:47:17 +0100
commit356f3b6bc58327be42994a9eeebc8392377ec895 (patch)
tree5e0c68ad13c17a993395749c29347c94508573b3 /src/server/shared/Logging/Log.cpp
parent0c7c25d6ed05355c1dfd0e1ca1179d8f20602073 (diff)
Core: INFO->ERROR level adjustment in ObjectMgr.cpp
Suggest everyone attempt to remember this: TC_LOG_TRACE = extreme debugging (debuginfo with packetstructures/data) TC_LOG_DEBUG = debugging (detailed activity of functions and activites inside core) TC_LOG_INFO = normal runstate (regular info like logins/logouts/levelups/passwordchanges etc) TC_LOG_WARN = possible issue with config/data etc - things that are not how they should be) TC_LOG_ERROR = actual error that has been either caought or must be fixed at some point TC_LOG_FATAL = crash or data corruption imminent Using the right logmech also helps distinguishing between 'regular runtime info' and stuff that might lead to a pissy situation later on... :)
Diffstat (limited to 'src/server/shared/Logging/Log.cpp')
0 files changed, 0 insertions, 0 deletions