[iSpark]

Quote:

Originally Posted by [HLF]Southclaw And I'm not sure he understood you, the answer wasn't really relevant... Anyway, you can control hook order by ordering the hooks themselves. The public will always come last (though ALS can complicate this). Hook function names are compiled to something like `OnGameModeInit@001` where `001` is the hook number, this is incremented each time you include y_hooks - that's how each function gets a new name. Because of this, the hooks are called in that order. There was a way to guarantee a first call but I'm not sure it works any more - it required adding the first public above the first y_hooks include.

Tried that. Putting the public callback above the first hook include. Didn't work.