A target lock and a knocked-player filter address different aspects of a PUBG aimbot’s behavior. One concerns retaining a selected target, while the other concerns whether a knocked player should be considered.
Shxdow’s PUBG description explicitly names Lock Target and Ignore Knocked Players. These features belong in the same explanation, but they should not be treated as one rule or presented as proof of a particular processing order.
What Target Lock Concerns
Lock Target refers to retaining the selected target rather than treating every moment as an entirely unrelated selection. That is the core idea behind target lock in PUBG aimbot cheats.
The feature name does not establish how long a lock persists in every circumstance. It also does not specify every condition that releases the lock. Those details require a fuller description than the feature name alone provides.
A lock should not be described as a guarantee that every shot will land. Target retention and the outcome of an individual shot are separate questions.
What the Knocked-Player Filter Concerns
Ignore Knocked Players is a separate documented option. Its purpose is to determine whether knocked players are excluded from consideration.
That is different from selecting a target among otherwise eligible players. Instead, it concerns a specific player state and whether that state affects eligibility.
The distinction is useful in a simple hypothetical situation: a selected target becomes knocked while other players remain nearby. The two feature names are relevant to understanding the available settings, but they do not establish exactly which internal rule is evaluated first.
Do Not Invent the Order of Events
The available description does not publish the interaction between Lock Target and Ignore Knocked Players for every circumstance. It would therefore be misleading to promise an instant switch, a fixed delay, or an unbreakable lock.
Instead, the supported roles should remain clear. Lock Target concerns target retention, while Ignore Knocked Players concerns excluding a particular player state.
For PUBG, this is the most accurate way to describe the pair without adding unsupported technical details. You can explain why the features are distinct without inventing timings or guaranteeing what happens in every encounter.
A named lock and a named filter are specific features; neither one provides a complete specification of the aimbot’s entire decision-making process.