Extend modules with plugin / hook functionality

Expected Behavior

In order to increase usability and functionality it would be good if the following two functionalities would exist.

Scheduleable Module functions

Modules define functions to be called as part of automation (in other words: Add selectable options from mdouels to the cron module), e.g.

Release/Unrelease News on defined time
Open/Close forum threads at given time
Trigger backups on schedule
automatically raise reoccurring tasks (e.g. admin tickets for regular checks, cleanup operations)
...?

It may be worth thinking this the other way around and have an interface in the cron module that other modules can use to schedule their actions, so inverse current checks from on-access to on-change.

Hook support

Some of the ideas flying in my head would require to trigger module functions at certain actions in other modules. To keep this coupling optional independent of module selection it would be good to implement function hooks (in a defined format) Points where this could be useful:

Additional actions on user creation
Tournament match ready triggers additional actions as
- Traffic priorisation / move / VLAN change via NOC
- Gameserver spawning
- Voiceserver config
- Newspost on high-profile matches
- ...?

Current Behavior

Interactions between modules are in most cases implicit by direct calls with a few if-cases if the module is not active.

lansuite / lansuite