API: Startup: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
#Server.InitLibrary | #Server.InitLibrary | ||
##Reads command-line switches and sets up path and logging | ##Reads command-line switches, and sets up path and logging | ||
##''Logger.Logged'' | ##''Logger.Logged'' | ||
#Server.InitServer | #Server.InitServer | ||
Latest revision as of 21:03, 20 August 2012
To start the server, fCraft front-ends should call Server.InitLibrary(), Server.InitServer(), and Server.StartServer() in the right order. The following sequence of events takes place (raised events are in italics). fCraft tools usually only call InitLibrary and selected methods from InitServer(). For instance, ConfigGUI calls InitLibrary and Config.Load().
- Server.InitLibrary
- Reads command-line switches, and sets up path and logging
- Logger.Logged
- Server.InitServer
- Activates plugins (0.700+)
- PluginManager.PluginAdded
- PluginManager.PluginActivated
- Server.Initializing
- Loads config
- Config.KeyChanging
- Config.KeyChanged
- Loads PlayerDB
- Loads IPBanList
- Prepares commands
- CommandManager.CommandRegistering
- CommandManager.CommandRegistered
- Loads AutoRank settings
- Server.Initialized
- Activates plugins (0.700+)
- Server.StartServer
- Sets Server.StartTime
- Server.Starting
- Creates Player.Console and Player.AutoRank
- Loads world list
- WorldManager.WorldCreating
- WorldManager.WorldCreated
- Sets up networking (sets Port, InternalIP, and ExternalIP)
- Starts listening for connections
- Starts IRC
- Starts Heartbeat
- Starts AutoRank
- Starts Scheduler
- Server.Started