question about hook.Add

[MrPresident]

I know how to use this..

hook.Add("function to hook", "your name for this hook", function_you_are_hooking)


However I was looking through some ULX code and I noticed you guys have an extra parameter in there..

ex: hook.Add( "PlayerSpawnedEffect", "ULXLogEffectSpawn", effectSpawn, 20 )

What is this number at the end for? I've looked on the wiki but it doesn't list there being a 4th parameter to the hook command.

[JamminR]

http://ulyssesmod.net/docs/files/lua/ULib/server/hook-lua.html
Allows developers to write hooks that take precedence over/under other hooks of same name.
Garry's default 'if anything is returned from an in game hook then all other scripts using that same hook stop executing' method is just a pain in the rear.

[MrPresident]

So this allows hooks with the same unique name to be run together but in priority chains?

if so, thats interesting...

[JamminR]

This allows hooks using the same event to continue running it's unique hooks if that particular event's functions returns anything, not the same unique name. (Right Megiddo?)
For example, without ULib, if a script using "GM:PlayerSay" to hook returns anything, Gmod stops executing all other hooks using that event whether it be within that same author's script or not. (at least it did when ULib's hook system was written)
Using ULib's hook.Add, and setting a higher priority than 0 (default), would allow ULib to continue performing the unique hooks that use GM:PlayerSay instead of dying.

[Megiddo]

You should still have unique names for each hook, MrPresident. The objectives with ULib's modified hooks are as follows:
1. Gives a "pre-hook" (-20) and "post-hook" (20) functionality. Pre hooks are guaranteed to always be called when the hook is used because they are called before any other hooks, and are not allowed to return any values themselves (read-only). Post hooks are likewise called after all other hooks have modified whatever is in question. Post hooks are useful for things like spawn loggers because you know that anything that could have modified the player's ability to spawn the object has already been resolved.

So, it calls in order from -20 and 20, where -20 and 20 are 'read-only'. Anything that doesn't pass in a number is set to 0.

Does that answer your questions?

[MrPresident]

Yes it does! =) Thanks.