# 2.2.0 First release since 1.2.5, and the mod has been rewritten. If you are coming from 1.2.5, read the first two sections — the log format changed and the old one is gone. ## Breaking **The log is now JSONL.** 1.2.5 wrote lines like `[19:55:06] IMPORTANT: ...`, with `IMPORTANT` and `CHAT` as the only markers. Every event is now one JSON object per line, with a type and a level: {"t":"19:57:19","lvl":"INFO","type":"kills","msg":"Killed 1x Cow."} {"t":"19:59:48","lvl":"CRITICAL","type":"death","msg":"DIED: shot by Pillager at Y=78."} Anything that parsed the old text format has to be rewritten. In exchange, a reader gets a machine-readable type and a severity instead of having to pattern-match on English sentences. **Three levels instead of one flag.** `INFO` is background, `NOTABLE` is worth mentioning, `CRITICAL` is happening right now. That is what lets a commentator interrupt itself for a creeper and stay quiet through the 200th stone block. ## It actually works in multiplayer now 1.2.5 read the player through `ServerPlayerEntity`, which only exists when your own client is hosting. On any real server it was `null`, so **the mod silently logged nothing at all** — it looked installed and did nothing. Everything now reads client-visible state only. The same code works in singleplayer and on a server, and it still only ever logs your own player. ## New **`player_state.json`**, rewritten every second next to the log. The log says what *happened*; this says what is *true* — vitals, position, biome, dimension, weather, equipment with durability, your whole inventory, status effects and vanilla statistics. It means a reader can answer "what am I holding" without replaying the log from the start. **Death history that survives restarts**, so "how many times have I died to lava" has an answer. **A lot more of the game is tracked.** Danger (hostile mobs closing in, lava, drowning, long falls), combat with kill attribution, mining sessions and first-ore finds, building and containers, what you are looking at, advancements, level ups, scenery and time of day, chat and commands. **Exact kills and damage when you are hosting.** In singleplayer the integrated server runs in the same game, so the mod reads the real damage source and who landed the killing blow instead of guessing. On a remote server it falls back to inference, as before. **Four builds:** | Minecraft | Loader | |---|---| | 26.1.2 | Fabric | | 1.21.11 | Fabric | | 1.21.1 | Fabric | | 1.21.1 | NeoForge 21.1 | 1.2.5 was 1.20.4 only. The NeoForge build as no dependency — it uses NeoForge's own events, so it drops into a modpack without dragging anything else in. ## Fixed **Block and item names were coming out in your language.** 1.2.5 used the translated display name, so on a French client a diamond ore logged as *Minerai de diamant* — and every check the mod did against English names silently never matched. Names now come from the registry, so the log is stable and English whatever the game is set to. **A long fall was announced every four seconds** instead of once, each time with a bigger number. Since `CRITICAL` interrupts whatever the commentator is saying, a single drop could talk over everything else. Now announced once per fall. **Lava was a false alarm with Fire Resistance.** Standing in lava with the potion active is not an emergency; it was shouting `CRITICAL` every five seconds through a potion you drank on purpose. Same for fire, and for a fall with Slow Falling or an elytra. **Nearby mobs flooded the log.** An unchanged group of mobs is no longer restated every few seconds — it repeats only when the threat actually escalates. ## Notes The mod is still **client-side only** and works on any server without the server having it. Files go to `<your minecraft folder>/logs/player_actions/` — `session.log` and `player_state.json`.

# 2.2.0 First release since 1.2.5, and the mod has been rewritten. If you are coming from 1.2.5, read the first two sections — the log format changed and the old one is gone. ## Breaking **The log is now JSONL.** 1.2.5 wrote lines like `[19:55:06] IMPORTANT: ...`, with `IMPORTANT` and `CHAT` as the only markers. Every event is now one JSON object per line, with a type and a level: {"t":"19:57:19","lvl":"INFO","type":"kills","msg":"Killed 1x Cow."} {"t":"19:59:48","lvl":"CRITICAL","type":"death","msg":"DIED: shot by Pillager at Y=78."} Anything that parsed the old text format has to be rewritten. In exchange, a reader gets a machine-readable type and a severity instead of having to pattern-match on English sentences. **Three levels instead of one flag.** `INFO` is background, `NOTABLE` is worth mentioning, `CRITICAL` is happening right now. That is what lets a commentator interrupt itself for a creeper and stay quiet through the 200th stone block. ## It actually works in multiplayer now 1.2.5 read the player through `ServerPlayerEntity`, which only exists when your own client is hosting. On any real server it was `null`, so **the mod silently logged nothing at all** — it looked installed and did nothing. Everything now reads client-visible state only. The same code works in singleplayer and on a server, and it still only ever logs your own player. ## New **`player_state.json`**, rewritten every second next to the log. The log says what *happened*; this says what is *true* — vitals, position, biome, dimension, weather, equipment with durability, your whole inventory, status effects and vanilla statistics. It means a reader can answer "what am I holding" without replaying the log from the start. **Death history that survives restarts**, so "how many times have I died to lava" has an answer. **A lot more of the game is tracked.** Danger (hostile mobs closing in, lava, drowning, long falls), combat with kill attribution, mining sessions and first-ore finds, building and containers, what you are looking at, advancements, level ups, scenery and time of day, chat and commands. **Exact kills and damage when you are hosting.** In singleplayer the integrated server runs in the same game, so the mod reads the real damage source and who landed the killing blow instead of guessing. On a remote server it falls back to inference, as before. **Four builds:** | Minecraft | Loader | |---|---| | 26.1.2 | Fabric | | 1.21.11 | Fabric | | 1.21.1 | Fabric | | 1.21.1 | NeoForge 21.1 | 1.2.5 was 1.20.4 only. The NeoForge build as no dependency — it uses NeoForge's own events, so it drops into a modpack without dragging anything else in. ## Fixed **Block and item names were coming out in your language.** 1.2.5 used the translated display name, so on a French client a diamond ore logged as *Minerai de diamant* — and every check the mod did against English names silently never matched. Names now come from the registry, so the log is stable and English whatever the game is set to. **A long fall was announced every four seconds** instead of once, each time with a bigger number. Since `CRITICAL` interrupts whatever the commentator is saying, a single drop could talk over everything else. Now announced once per fall. **Lava was a false alarm with Fire Resistance.** Standing in lava with the potion active is not an emergency; it was shouting `CRITICAL` every five seconds through a potion you drank on purpose. Same for fire, and for a fall with Slow Falling or an elytra. **Nearby mobs flooded the log.** An unchanged group of mobs is no longer restated every few seconds — it repeats only when the threat actually escalates. ## Notes The mod is still **client-side only** and works on any server without the server having it. Files go to `<your minecraft folder>/logs/player_actions/` — `session.log` and `player_state.json`.

# 2.2.0 First release since 1.2.5, and the mod has been rewritten. If you are coming from 1.2.5, read the first two sections — the log format changed and the old one is gone. ## Breaking **The log is now JSONL.** 1.2.5 wrote lines like `[19:55:06] IMPORTANT: ...`, with `IMPORTANT` and `CHAT` as the only markers. Every event is now one JSON object per line, with a type and a level: {"t":"19:57:19","lvl":"INFO","type":"kills","msg":"Killed 1x Cow."} {"t":"19:59:48","lvl":"CRITICAL","type":"death","msg":"DIED: shot by Pillager at Y=78."} Anything that parsed the old text format has to be rewritten. In exchange, a reader gets a machine-readable type and a severity instead of having to pattern-match on English sentences. **Three levels instead of one flag.** `INFO` is background, `NOTABLE` is worth mentioning, `CRITICAL` is happening right now. That is what lets a commentator interrupt itself for a creeper and stay quiet through the 200th stone block. ## It actually works in multiplayer now 1.2.5 read the player through `ServerPlayerEntity`, which only exists when your own client is hosting. On any real server it was `null`, so **the mod silently logged nothing at all** — it looked installed and did nothing. Everything now reads client-visible state only. The same code works in singleplayer and on a server, and it still only ever logs your own player. ## New **`player_state.json`**, rewritten every second next to the log. The log says what *happened*; this says what is *true* — vitals, position, biome, dimension, weather, equipment with durability, your whole inventory, status effects and vanilla statistics. It means a reader can answer "what am I holding" without replaying the log from the start. **Death history that survives restarts**, so "how many times have I died to lava" has an answer. **A lot more of the game is tracked.** Danger (hostile mobs closing in, lava, drowning, long falls), combat with kill attribution, mining sessions and first-ore finds, building and containers, what you are looking at, advancements, level ups, scenery and time of day, chat and commands. **Exact kills and damage when you are hosting.** In singleplayer the integrated server runs in the same game, so the mod reads the real damage source and who landed the killing blow instead of guessing. On a remote server it falls back to inference, as before. **Four builds:** | Minecraft | Loader | |---|---| | 26.1.2 | Fabric | | 1.21.11 | Fabric | | 1.21.1 | Fabric | | 1.21.1 | NeoForge 21.1 | 1.2.5 was 1.20.4 only. The NeoForge build as no dependency — it uses NeoForge's own events, so it drops into a modpack without dragging anything else in. ## Fixed **Block and item names were coming out in your language.** 1.2.5 used the translated display name, so on a French client a diamond ore logged as *Minerai de diamant* — and every check the mod did against English names silently never matched. Names now come from the registry, so the log is stable and English whatever the game is set to. **A long fall was announced every four seconds** instead of once, each time with a bigger number. Since `CRITICAL` interrupts whatever the commentator is saying, a single drop could talk over everything else. Now announced once per fall. **Lava was a false alarm with Fire Resistance.** Standing in lava with the potion active is not an emergency; it was shouting `CRITICAL` every five seconds through a potion you drank on purpose. Same for fire, and for a fall with Slow Falling or an elytra. **Nearby mobs flooded the log.** An unchanged group of mobs is no longer restated every few seconds — it repeats only when the threat actually escalates. ## Notes The mod is still **client-side only** and works on any server without the server having it. Files go to `<your minecraft folder>/logs/player_actions/` — `session.log` and `player_state.json`.

# 2.2.0 First release since 1.2.5, and the mod has been rewritten. If you are coming from 1.2.5, read the first two sections — the log format changed and the old one is gone. ## Breaking **The log is now JSONL.** 1.2.5 wrote lines like `[19:55:06] IMPORTANT: ...`, with `IMPORTANT` and `CHAT` as the only markers. Every event is now one JSON object per line, with a type and a level: {"t":"19:57:19","lvl":"INFO","type":"kills","msg":"Killed 1x Cow."} {"t":"19:59:48","lvl":"CRITICAL","type":"death","msg":"DIED: shot by Pillager at Y=78."} Anything that parsed the old text format has to be rewritten. In exchange, a reader gets a machine-readable type and a severity instead of having to pattern-match on English sentences. **Three levels instead of one flag.** `INFO` is background, `NOTABLE` is worth mentioning, `CRITICAL` is happening right now. That is what lets a commentator interrupt itself for a creeper and stay quiet through the 200th stone block. ## It actually works in multiplayer now 1.2.5 read the player through `ServerPlayerEntity`, which only exists when your own client is hosting. On any real server it was `null`, so **the mod silently logged nothing at all** — it looked installed and did nothing. Everything now reads client-visible state only. The same code works in singleplayer and on a server, and it still only ever logs your own player. ## New **`player_state.json`**, rewritten every second next to the log. The log says what *happened*; this says what is *true* — vitals, position, biome, dimension, weather, equipment with durability, your whole inventory, status effects and vanilla statistics. It means a reader can answer "what am I holding" without replaying the log from the start. **Death history that survives restarts**, so "how many times have I died to lava" has an answer. **A lot more of the game is tracked.** Danger (hostile mobs closing in, lava, drowning, long falls), combat with kill attribution, mining sessions and first-ore finds, building and containers, what you are looking at, advancements, level ups, scenery and time of day, chat and commands. **Exact kills and damage when you are hosting.** In singleplayer the integrated server runs in the same game, so the mod reads the real damage source and who landed the killing blow instead of guessing. On a remote server it falls back to inference, as before. **Four builds:** | Minecraft | Loader | |---|---| | 26.1.2 | Fabric | | 1.21.11 | Fabric | | 1.21.1 | Fabric | | 1.21.1 | NeoForge 21.1 | 1.2.5 was 1.20.4 only. The NeoForge build as no dependency — it uses NeoForge's own events, so it drops into a modpack without dragging anything else in. ## Fixed **Block and item names were coming out in your language.** 1.2.5 used the translated display name, so on a French client a diamond ore logged as *Minerai de diamant* — and every check the mod did against English names silently never matched. Names now come from the registry, so the log is stable and English whatever the game is set to. **A long fall was announced every four seconds** instead of once, each time with a bigger number. Since `CRITICAL` interrupts whatever the commentator is saying, a single drop could talk over everything else. Now announced once per fall. **Lava was a false alarm with Fire Resistance.** Standing in lava with the potion active is not an emergency; it was shouting `CRITICAL` every five seconds through a potion you drank on purpose. Same for fire, and for a fall with Slow Falling or an elytra. **Nearby mobs flooded the log.** An unchanged group of mobs is no longer restated every few seconds — it repeats only when the threat actually escalates. ## Notes The mod is still **client-side only** and works on any server without the server having it. Files go to `<your minecraft folder>/logs/player_actions/` — `session.log` and `player_state.json`.

more information complemantary python script and source code on https://github.com/gigachadfr/PAL/tree/main