I don't have any plans to allow multiple events of the same type to be registered. What we were after with armageddon was creating ModLoader, which would load all mods and execute their routines in framework registered events. I'm sure you remember Elgan that we talked about it.
Here is the thread:
http://www.x-null.net/forums/showthr...d-1-12-modding
Each mod would need to have .ini file that our framework would parse, and load settings.
Example case:
MyAwesomeMod.pk3
MyAwesomeMod.ini
Code:
[description]
name=MyAwesomeMod
author=RazoRapiD
version=1.0
description=""
[events]
spawn=myawesomemod/events.scr::spawn
connect=myawesomemod/events.scr::connect
precache=myawesomemod/dmprecache.scr
[misc]
whatever
Now our framework parses files from the list that the engine will provide (or with functions that engine will provide)
It registers it's own events, and does something like:
Code:
spawn local.player:
for(local.i = 0; local.i < local.spawn_events.size; local.i++)
waitexec local.spawn_events local.player
end
This way mods won't need to touch the core events and won't create conflicts.
We can even make additional checks, so for example, if player is NIL or NULL don't execute the events, so it saves time and so on.