| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 1 | SYNOPSIS |
| Zesstra | 7ea4a03 | 2019-11-26 20:11:40 +0100 | [diff] [blame] | 2 | Initialization of the master object. |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 3 | |
| Zesstra | 7ea4a03 | 2019-11-26 20:11:40 +0100 | [diff] [blame] | 4 | DESCRIPTION |
| 5 | As the lfuns which are called to initialize objects after a load |
| 6 | are defined through driver hooks, and these hooks are cleared |
| 7 | prior to a master (re)load, the first function called is |
| 8 | inaugurate_master(). It's not very sensible to do anything earlier |
| 9 | as the master is not recognized as such at that time, and so a |
| 10 | number of (important) things would not work. Which lfun is called |
| 11 | during runtime to reset the master also depends on the driverhook |
| 12 | settings. Arbitrary actions may be done on a reset. |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 13 | |
| 14 | SEE ALSO |
| Zesstra | 7ea4a03 | 2019-11-26 20:11:40 +0100 | [diff] [blame] | 15 | inaugurate_master(M) |