A SWEP that a player can use on a corpse after another player died. Provides information about the death.
Specification
Allows a player to interact with a body dropped from a player death
Does not place an entity at every corpse drop, instead keeps a record of player deaths and displays them as a UI popup when a player possessing the tool approaches the area.
Logs of when players investigate bodies
<Player 1> Investigated the corpse of <Player 2>, killed at <Time of death of Player 2>, at
Interaction yields list of information
the identity of the dead body,
how long ago it happened,
how the death happened,
equipment found on the body
If the player was killed in view of a CCTV camera:
Offer additional information
the job of the murderer(s),
the identity of the murderer(s) (The identity of the disguise used if applicable),
Withhold this information if CCTV systems are down, or the specific camera was destroyed before the murder.
Possible method of implementation:
A list of a fixed length (64, 128, etc) that stores entries created when players due under specific circumstances.
For example, a structure similar to the JSON table below
[
{
"deathLocation": [
"int",
"int",
"int"
],
"timestamp": "int",
"corpseName": "string",
"corpseJobID": "int",
"vwarReg": "string",
"vwarRank": "string",
"causeOfDeath": "string",
"corpseEquipment": [ // A table of the items most recently used by the player on death
"string",
"string",
"string"
],
"killerName": "string",
"killerJobID": "int"
}
]
When generating the entries, the information gained should follow the tables below, with the first being the info gained from the corpse upon investigation, and the second being the information gained on the murderer(s) if done in view of a CCTV camera
As the tool will be mainly used by IA, many death events will go ignored, instead filling up the entry list with unneeded data and clearing valid entries earlier. Ignore the following player death events when generating entries:
A D-Class killing a D-Class
A Foundation Player killing a D-Class
An SCP Killing any player
A CI Killing a CI
A GOC Killing a GOC
Information used when populating the entry should be calculated on death and stored in the table. Each entry should have an expiry timer (e.g. 10 minutes) beyond which it is removed from the list. If the list is at max capacity, the oldest entries should be removed to make room for newer ones.
auburncivilnetworks
commented
3 months ago
Feature description
A SWEP that a player can use on a corpse after another player died. Provides information about the death.
Specification
Possible method of implementation:
A list of a fixed length (64, 128, etc) that stores entries created when players due under specific circumstances. For example, a structure similar to the JSON table below
When generating the entries, the information gained should follow the tables below, with the first being the info gained from the corpse upon investigation, and the second being the information gained on the murderer(s) if done in view of a CCTV camera
As the tool will be mainly used by IA, many death events will go ignored, instead filling up the entry list with unneeded data and clearing valid entries earlier. Ignore the following player death events when generating entries:
Information used when populating the entry should be calculated on death and stored in the table. Each entry should have an expiry timer (e.g. 10 minutes) beyond which it is removed from the list. If the list is at max capacity, the oldest entries should be removed to make room for newer ones.