I'll try to give you a different way to look at them hooks.
In ElkArte code you see for example:
call_integration_hook('integrate_general_mod_settings', array(&$config_vars));
You look at it because you want to add a new setting and you think WTH!
So, I'll tell you, when you see such function in the code, you can "translate" it to:
This_is_my_addond_function(&$config_vars);
This is what the code does. Really. That's all (for what matters *to you*).
A practical example.
In this addon you are adding settings, right?
And you do that with the function "GHF_Settings", correct?
So, in the install file of the addon, you have the string:
'integrate_general_mod_settings' => 'GHF_Settings|SOURCEDIR/addons/GHF.subs.php',
again, WTH?!?!
Let's translate it into an "English-like" thing.
In the code, where there is the
call_integration_hook('integrate_general_mod_settings', array(&$config_vars));
line, ElkArte will do this:
require_once(SOURCEDIR . '/addons/GHF.subs.php');
GHF_Settings(&$config_vars);
If you look at the string in your install file, you see the three pieces:
'integrate_general_mod_settings'
'GHF_Settings
SOURCEDIR/addons/GHF.subs.php',
Dunno if it helps explaining them or just makes things more confused. LOL