File /obj/handlers/terrain_track_handler.c

Written by Romanov

Started sometime in August 2006. Comments: The exact same process in basic_room.c for storing a passing player's data in an array is followed. The handler stores all the tracking arrays in a mapping with the terrain room environment variables as a key. If the terrain room gets unloaded, the setup_room() function in handler_base.c restores the array. There is also a timestamped mapping with the keys being the terrain room environment variables. This is updated simultaneously with the above mapping. This mapping is used for housekeeping, ie deleting map keys that are older than a certain time threshold.

Method index

• add_journey(string, int *, int *)
• add_room_track_details(object, object, object, int)
• chime(string, int)
• query_handler_size()
• query_journey(string)
• query_journey_array()
• query_on_path(string, int *)
• restore_track_details(object)

Public Functions

add_journey

void add_journey(string player,
                 int * start_coord,
                 int * end_coord)

add_room_track_details

void add_room_track_details(object env,
                            object target,
                            object to,
                            int level)

chime

void chime(string chime_message,
           int type)

query_handler_size

int query_handler_size()

query_journey

class _wp * query_journey(string player)

query_journey_array

int query_journey_array()

query_on_path

mixed * query_on_path(string player,
                      int * tracker_coord)

restore_track_details

mixed * restore_track_details(object env)