blob: 2cf612b8c0b18de4d41805b415472a67f8fdd379 [file] [log] [blame]
MG Mud User88f12472016-06-24 23:31:02 +02001SYNOPSIS
Zesstra7ea4a032019-11-26 20:11:40 +01002 void inaugurate_master(int arg)
MG Mud User88f12472016-06-24 23:31:02 +02003
4DESCRIPTION
Zesstra7ea4a032019-11-26 20:11:40 +01005 This function is called in the master object after it has been
6 created and is fully functional. Note that the create()
7 function is of little use in the master object, because at the
8 time it is called there is no simul_efun object yet, and the
9 interpreter does not know anything about the user-ids and
10 access permissions.
MG Mud User88f12472016-06-24 23:31:02 +020011
Zesstra7ea4a032019-11-26 20:11:40 +010012 The argument <arg> denotes why this function is called:
13 arg = 0: the mud just started, this is the first master of all.
14 = 1: the master was destructed and then reactivated
15 (because a new one couldn't be loaded).
16 = 2: the master was destructed and then reactivated, but
17 additionally lost all variable contents.
18 = 3: this is a reloaded master.
MG Mud User88f12472016-06-24 23:31:02 +020019
Zesstra7ea4a032019-11-26 20:11:40 +010020 This function has to at least set up the driverhooks to use
21 (in 3.2.1). Also, any mudwho or wizlist handling has to be
22 initialized here.
MG Mud User88f12472016-06-24 23:31:02 +020023
Zesstra7ea4a032019-11-26 20:11:40 +010024 Besides that, do whatever you feel you need to do,
25 e.g. set_auto_include_string(), or give the master a decent euid.
MG Mud User88f12472016-06-24 23:31:02 +020026
27SEE ALSO
Zesstra7ea4a032019-11-26 20:11:40 +010028 initialisation(M), create(A), simul_efun(C), get_master_uid(M),
29 flag(M), reactivate_destructed_master(M)