2 .NA lost "Report lost items"
5 The lost command displays all lost items currently in the
6 database for your country.
8 All lost items are timestamped at the time they were lost. If
9 you had a previously lost item in the database, and then build a
10 new item of the same type with the same id, or regain an item of the
11 same type with the same
12 id, it is removed from the database. This is done because the new item
13 will now show up in the other dump commands, and is no longer lost.
15 Lost items are kept in the database for 48 hours (default) but may
16 be kept longer at the deity's discretion. Also, issuing the lost
17 command does not remove items from the database. That is where the
18 timestamp functionality becomes important.
20 While the lost command does not take any arguments, it does
21 take the standard syntax for selecting information.
22 (see \*Qinfo Selector\*U).
24 A typical usage might be:
25 .EX lost ?timestamp>854954677
26 which would list data for all lost items timestamped after
27 854954677. (Timestamps are kept in system seconds.)
29 A lost command lists all the lost items headed by:
31 Sun Feb 9 22:16:37 1997
32 DUMP LOST ITEMS 855544597
35 The first line is the date. The second line is the
36 "DUMP LOST ITEMS <timestamp>" where the <timestamp> field is the current
37 timestamp. The third line is the columns which are output.
39 These columns represent:
41 .in \w'timestamp\0\0'u
43 The type of lost item. They are as follows:
50 The # of the ship, plane, land unit or nuke. All of these items
51 are identified by id. Sectors are identified by x and y.
53 The x coordinate of the lost item when it was lost.
55 The y coordinate of the lost item when it was lost.
57 The timestamp of when the item was lost.
60 .SA "xdump, dump, ldump, sdump, ndump, pdump, Ships, Planes, Nukes, LandUnits, Sectors, Clients"