Combat Log

Normalizes combat-log data from both Source 1 and Source 2 ingestion paths into a unified entry shape.

See also: Using the Combat Log, How Proto Parsing Works

---

Generated API

gem.combatlog.CombatLogProcessor

CombatLogProcessor

class CombatLogProcessor

Parses and dispatches combat log entries.

Source: src/gem/combatlog.py:171

Methods

on_combat_log_entry

Signature: def CombatLogProcessor.on_combat_log_entry(self, handler: CombatLogHandler) -> None

Register a handler to receive decoded CombatLogEntry objects.

Source: src/gem/combatlog.py:181

process_rune_pickup

Signature: def CombatLogProcessor.process_rune_pickup(self, player_slot: int, rune_type: int, tick: int = 0) -> None

Emit a PICKUP_RUNE CombatLogEntry from a CDOTAUserMsg_ChatEvent.

Source: src/gem/combatlog.py:189

process_s1_event

Signature: def CombatLogProcessor.process_s1_event(self, game_event: Any, name_table: Any, tick: int = 0) -> None

Parse a dota_combatlog S1 game event and emit a CombatLogEntry.

Source: src/gem/combatlog.py:214

process_s2_bulk

Signature: def CombatLogProcessor.process_s2_bulk(self, msg: Any, name_table: Any, tick: int = 0) -> None

Parse a CDOTAUserMsg_CombatLogBulkData and emit CombatLogEntry per entry.

Source: src/gem/combatlog.py:259

process_s2_entry

Signature: def CombatLogProcessor.process_s2_entry(self, msg: Any, name_table: Any, tick: int = 0) -> None

Parse a CMsgDOTACombatLogEntry and emit a CombatLogEntry.

Source: src/gem/combatlog.py:271

gem.combatlog.CombatLogEntry

CombatLogEntry

class CombatLogEntry

One decoded combat log entry.

Source: src/gem/combatlog.py:95

Dataclass fields

Name	Type	Default
tick	int	-
log_type	str	-
attacker_name	str	''
target_name	str	''
inflictor_name	str	''
value	int	0
attacker_is_hero	bool	False
target_is_hero	bool	False
attacker_is_illusion	bool	False
target_is_illusion	bool	False
ability_level	int	0
gold_reason	int	0
xp_reason	int	0
value_name	str	''
damage_type	str	''
stun_duration	float	0.0