Read a PUBG knock, revive and elimination timeline
Direct answer
Build a chronological view before calculating kills. Distinguish damage, incapacitation, revival and elimination using the event types documented for your payload. Keep unknown transitions visible; a missing transition does not justify inventing an elimination or a revive.
Resolve one participant
Identify the participant against the match roster and retain events involving that identity. Keep timestamp, original array position, event type and the relevant attacker, victim and assistant fields. Do not collapse them into a single actor column. Include surrounding state events, otherwise an isolated damage row loses the information needed to interpret it. Retain the parser revision alongside the original payload.
Allow an unknown state
Active, incapacitated, revived and eliminated can form a working model, but this is your interpretation of documented events. If the first observed event involves an already incapacitated player, begin with uncertainty. Keep unfamiliar event schemas intact for inspection instead of feeding them through an older handler. A damage event alone is insufficient evidence that the victim was eliminated by that attacker.
Compare two different sequences
Consider one sequence with damage, a knock, a revival and later combat. Compare another with damage, a knock and final elimination. Both contain a knock; only later events establish the outcome. Show each transition separately. Grouping by victim and selecting the last attacker can misattribute results. These are hypothetical parser examples, not a replay of matches tested by this publication.
Reconcile without rewriting evidence
Use match-level participant statistics as a cross-check. When totals disagree, investigate event version handling, ingestion duplication and missing coverage before changing any interpretation. Produce a discrepancy report with original array positions. A timeline cannot reveal intent, communication or what the player saw. Separate observed transitions from tactical interpretation, and link a permitted recording when you need to examine screen-level decisions.
Sources and scope
Source-informed editorial procedure; not a claim of hands-on testing. Check your installed version. Historical patch notes are labelled by version. This page was authored in English and Simplified Chinese; additional translations are not presented as independently researched articles.
These steps are editorial procedures, not a report of testing this game. A source publication version is not automatically your installed version.
Continue with:Review the related foundation guide · All guides