Extraction ESP is more useful to understand when you separate what each field describes. In Halloween The Game, a name, a type, a status and a distance are not interchangeable pieces of information.
Shxdow’s documented extraction features include Extraction Name, Extraction Type, Extraction Status and Extraction Distance. Together, those names describe several aspects of an extraction point without establishing exactly which values each field can display.
Identity and Type
Extraction Name concerns which extraction point you are looking at. Extraction Type concerns its category. Knowing one does not necessarily answer the other.
That is the first distinction behind Halloween The Game extraction ESP. It is not simply one broad extraction reference; the description separates the point’s identity from its type.
The product description does not give a complete set of possible types. Inventing one would make the explanation less accurate, even if the names sounded plausible.
Status and Distance
Extraction Status is another separate field. It concerns the state associated with the extraction point. The documented feature name does not specify every possible state or the conditions that change it.
Extraction Distance concerns how far away the point is. It should not be treated as a travel-time estimate. Distance alone does not account for the route you would take or anything that could interrupt it.
These distinctions matter when you read the display. A point being nearby is not the same claim as a point being usable. A name identifies it; a distance locates it relative to you; a status concerns its state.
Read the Fields Separately
The documented feature set supports explaining those four subjects. It does not establish an automatic extraction action or a guarantee that reaching a point will end the encounter successfully.
Keep the questions separate: which point is it, what type is it, what status is shown, and how far away is it? That gives each field a clear role.
The extraction features can be described accurately without inventing specific status messages or promising a successful escape. The feature names already provide a useful structure. The important part is not asking one field to answer a question that belongs to another.