NFive

NFive

  • Docs
  • Help
  • API
  • Plugins
  • GitHub
  • Languages iconEnglish
    • Čeština
    • Español
    • Norsk
    • Português (Brasil)
    • Help Translate

›Server Side

Getting Started

  • Overview
  • Components
  • Database Setup
  • Server Setup
  • Installing Plugins
  • Administration
  • Troubleshooting

Plugin Manager

  • Overview
  • Command Reference

Plugin Development

  • Overview
  • Setup
  • Hub
  • Definition
  • Server Side

    • Life Cycle
    • Controller
    • Configurable Controller
    • Dependency Injection
    • Database Access
    • RCON

    Client Side

    • Life Cycle
    • Service
Edit

Life Cycle

Server side NFive plugins must contain one or more classes inheriting from the Controller class, however most plugins will only consist of one. When starting up, the NFive server will create an instance of each compatible controller class it finds in the main server plugin assemblies.

Sever Plugin Life Cycle

  1. Plugin controllers are constructed early in the NFive startup process and the order plugins are loaded cannot be guaranteed, so you should not use the constructor for any plugin runtime logic.
  2. Immediately after the plugin's constructor is called, NFive invokes the plugin's Loaded() method.
  3. Once all plugins are loaded, all controllers' Started() methods are invoked in parallel asynchronously.
  4. The server fires off internal events signalling that it has finished loading.
Last updated on 5/14/2019
← PreviousController →
  • Sever Plugin Life Cycle
NFive
Docs
Getting StartedPlugin ManagerAPI Reference
Community
Getting HelpProject ChatDiscord NFive chat
More
Plugin HubGitHubNFive stargazers on GitHub