Documentation Addition: Stock game logger names

[korgano]

Might be good to have a reference list of stock game logger names to help mod devs and mod users to figure out what loggers to use when troubleshooting:

HBS.Logging logger names:

"Generic"

"CONSOLE"

"VideoPlayer"

"Achievements"

"Achievements.Steam"

"Achievements.GOG"

"AI"

"AI.BehaviorNodes"

"AI.TurnOrder"

"AI.DecisionMaking"

"Analytics"

"Analytics.Log"

"Analytics.Google"

"Analytics.Combat"

"Analytics.Sim"

"AudioEvents"

"AuditUtilities"

"BattleTech.Contract"

"BattleTechServerGameVerification.ClientData"

"BattleTechServerGameVerification.MechData"

"BattleTechServerGameVerification"

"Camera"

"ClientAPI"

"ClientEcounterReadyMessage"

"ClientBeginPlayingMessage"

"ClientBeginLoadingMessage"

"ClientGameSetup"

"CombatLog.AbilitiesAndEffects"

"CombatLog.ActorActivation"

"CombatLog.Attacking"

"CombatLog.Crit"

"CombatLog.Damage"

"CombatLog.Heat"

"CombatLog.Hit"

"CombatLog.HitMin"

"CombatLog.Initialization"

"CombatLog.Injury"

"CombatLog.MechDFASequence"

"CombatLog.MechFallSequence"

"CombatLog.MechImpacts"

"CombatLog.MechImpacts_Debug"

"CombatLog.MechJumpSequence"

"CombatLog.ActorMovementSequence"

"CombatLog.MechMeleeSequence"

"CombatLog.Morale"

"CombatLog.RoundSequence"

"CombatLog.Stability"

"CombatLog.Team"

"ContentStrings"

"Debug.DebugSettings"

"DebugBridge"

"DebugBridge.INTERNAL"

"DictionaryPersistentStore"

"Data.AssetBundleManager"

"Data.ContentpackIndex"

"Data.DataManager"

"Data.DataManager.ContainedLoadRequest"

"Data.DataManager.LoadRequests"

"Data.MemberInfoHelper"

"Data.MethodInfoHelper"

"Data.MetaDataDatabase"

"Data.ResourceLocator"

"DataLoader"

"EncounterLogic"

"EncounterLogic.ContractOverride"

"EncounterLogic.ContractObjective"

"EncounterLogic.Objective"

"EncounterLogic.Dialogue"

"ErrorLog.Pilot"

"FSM.StateMachine"

"FX.FXBank"

"FX.FXGroup"

"FX.FXParticleSystem"

"GameVerificationModule"

"CombatLog.GameLogic"

"GameSetupNetworkMessage"

"CombatLog.InvocationHandler"

"CombatLog.Invocations"

"Logging.View"

"LoggerUpdate"

"MapExport"

"Network.Client"

"Network.Core"

"NetworkRandomCallstacks"

"NetworkRandomValues"

"Network.Server"

"OtherClient"

"PoolManager"

"PreviousRandomReport"

"QNET"

"Serialization"

"Sysinfo"

"Tests"

"UI"

"Unity"

"Utilities"

"VersionManifest"

"SimGame.Events"

"SimGame.Constant.Overrides"

"SimGame.Difficulty"

"CombatLog.StatCollection.Actions"

"S3Manager"

"GameInfo"

"GameInstance"

"CombatLog.AttackDirector"

"CombatLog.AttackSequence"

"Save.SaveManager"

"Save.Core.SaveBlock"

"Save.Core.MultiReadSaveBlock"

"Save.Core.SaveBlockException"

"Save.Core.WriteLocation"

"Save.Core.StandaloneAsyncFile"

"Save.Core.AsyncFile"

"Save.Core.SteamFileOperations"

"Save.Core.StandaloneFileOperations"

"Save.Core.FileOperations"

"Save.Core.DataMigrationTask"

"Save.Core.SaveBlockRequest"

"Save.Core.LoadBlockRequest"

"Save.Core.SaveBytesTask"

"Save.Core.LoadBytesTask"

"Save.Core.ThreadedSaveManagerRequest"

"Save.Core.SaveSystem"

"GameContext"

"Network.Traffic"

"Steam"

"LevelLoader"

"TestGamePayloadManager"

"GameVerificationMessage"

"BattleTech.Services"

"CombatLog.ServerStatsCompare"

"PendingSynchronizedMessages"

"CombatLog.ClientStatsCompare"

"MessageCenter"

"UserSettings"

"CustomUnitsAndLances"

"SpawnableUnit"

"CombatLog.CombatSelectionHandler"

"ActorBurningEffect"

"CombatLog.AbstractActor"

"SerializedReference"

"SerializableReferenceContainer"

"GameObjectTracker"

"TrackedGameObject"

"PilotDef"

"SaveGameStructure"

"OnGameShutdown"

"ItemCollectionDef"

"ModLoader"

"JSONMerger"

[CptMoore]

More ideas:

• RT and BTA have same defaults: what loggers to enable, at which level, what log lines to ignore (to ignore spammy lines)
• presets would be nice, like what kind of area of BT is interesting (AI, Combat, Loading, MechLab, etc..). Might be worth it to check how logging presets can already be switched in the debug menu, and if that can be connected to modtek logging settings