[spunkster21]

Hi,

I’m very new to SourceMod scripting and I’m trying to wrap my head around some basics regarding events.

Using the examples in this tutorial http://wiki.alliedmods.net/Events_%2...d_Scripting%29 I am trying to block the item_pickup event. I’m not trying to do anything fancy, just trying to understand the difference between pre and post hooks.

Here’s my code:

PHP Code:

public OnPluginStart()
 {
              HookEvent("item_pickup", Event_ItemPickup, EventHookMode_Pre);
}
   
public Action:Event_ItemPickup (Handle:event, const String:name[], bool:dontBroadcast)
{
              return Plugin_Handled;
} 


This doesn’t prevent me from picking up anything in CS:Source, which is what I was expecting. No doubt my lack of understanding is the problem, so I would appreciate some feedback and guidance.

Thanks.

[cmptrwz]

Blocking the event does not mean blocking the action. In this case, blocking the notifications of the action is most likely all you are doing.

I don't do anything with CS:Source, so I don't know how to go about doing what you want to do though.

[spunkster21]

Well, that explains why I'm still able to pick things up ;)

I'm not so much trying to block items being picked up as I'm trying to understand what the different hooking modes are used for.

Clearly I've misunderstood the above link. I'll re-read and see if it makes more sense a second time around.

[BrutalGoerge]

post= after event fires so you can use its information
pre = before event fires so you can block the message
post_nocopy = after, and doesn't copy any of the event information, so you can use the event to just trigger a function

if no method is specified, i believe it uses post

[spunkster21]

Originally Posted by BrutalGoerge post= after event fires so you can use its information pre = before event fires so you can block the message post_nocopy = after, and doesn't copy any of the event information, so you can use the event to just trigger a function if no method is specified, i believe it uses post

Thank you, that's helped make hooking much clearer.

[olj]

post = after event fires so you can use its information.

I believe in pre hooks the game already knows all key values beforehand. At least i used keyvalues in pre hooks and they were all correct.

[cmptrwz]

I believe the intent was "You don't care about blocking or changing the event, but want to react to what was finally sent."

Because pre-hooks might change or block the event, and that might change what you want to do after it actually gets sent.

[BrutalGoerge]

yeah i didnt mean to insinuate that pre doesn't copy the event kv's