File /secure/login.c

Includes

Class Index

• state
  This structure holds a single state.

Method index

• debug_log(string, mixed args)
• enter_state(string)
• main_random_name_menu(string)
• mxp_enable()
• query_delete_player_file_name(string)
  This method returns the path to the deleted player file.
• query_login_ob()
  This method determines if the object is a login object.
• query_player_file_name(string)
  This method returns the path to the player file.
• quit(string)

Public Functions

These are functions that everyone can access.

.

debug_log

void debug_log(string fmt,
               mixed args ...)

enter_state

void enter_state(string new_state)

main_random_name_menu

mixed main_random_name_menu(string event)

mxp_enable

void mxp_enable()

query_delete_player_file_name

string query_delete_player_file_name(string name)


This method returns the path to the deleted player file. This is the deleted player files actual normal location, it was written to allow moving the player files aruond easier.

• Parameters:
  name - the name of hte player whose file to find
• See also:
  test_user() and query_delete_player_file_name()

query_login_ob

int query_login_ob()


This method determines if the object is a login object.

• Returns:
  always returns 1
  query_player_file_name

  string query_player_file_name(string name)
  

  
  This method returns the path to the player file. This is the player files actual normal location, it was written to allow moving the player files aruond easier.
  
  • Parameters:
    name - the name of hte player whose file to find
  • See also:
    test_user() and query_delete_player_file_name()
    quit

    mixed quit(string event)
    

    Classes

    These are nice data types for dealing with... Data!
    • state

      class state {
                    string name;
                    string action;
                    string write;
                    int noecho;
                    mapping events;
      }
      
      

      
      This structure holds a single state. A state has a name, an action or write and a set of events.
      The name is used to identify the state and must be unique within the state table. An action is a function to call while a write is a string or file to be written to the screen. The events mapping is made of event and new-state. The event is the trigger and new-state is the new state the machine should enter.

      An event is a string of the form "type-data" where type is either "input" or "return" indicating user input or the return from an action function. Thus "return-ok" would be triggered if the action function in this state returned "ok" while "input-y" would be triggered if the user typed in "y". The special event "input" will trigger on any user input while the event "default" will trigger on any input or return value.