[##:##] Command : lost
The lost command displays all lost items currently in the database for your country.
All lost items are timestamped at the time they were lost. If you had a previously lost item in the database, and then build a new item of the same type with the same id, or regain an item of the same type with the same id, it is removed from the database. This is done because the new item will now show up in the other dump commands, and is no longer lost.
Lost items are kept in the database for 48 hours (default) but may be kept longer at the deity's discretion. Also, issuing the lost command does not remove items from the database. That is where the timestamp functionality becomes important.
While the lost command does not take any arguments, it does take the standard syntax for selecting information. (see info Selector).
A typical usage might be:
[##:##] Command : lost ?timestamp>854954677
which would list data for all lost items timestamped after 854954677. (Timestamps are kept in system seconds.)
A lost command lists all the lost items headed by:
Sun Feb 9 22:16:37 1997 DUMP LOST ITEMS 855544597 type id x y timestamp
The first line is the date. The second line is the "DUMP LOST ITEMS <timestamp>" where the <timestamp> field is the current timestamp. The third line is the columns which are output.
These columns represent:
The type of lost item. They are as follows: 0 - Sector 1 - Ship 2 - Plane 3 - Land unit 4 - Nuclear stockpile
The # of the ship, plane, land unit or nuke. All of these items are identified by id. Sectors are identified by x and y.
The x coordinate of the lost item when it was lost.
The y coordinate of the lost item when it was lost.
The timestamp of when the item was lost.
See also : xdump , dump , ldump , sdump , ndump , pdump , Ships , Planes , Nukes , LandUnits , Sectors , Clients