[didoWEE]

Which is the best variant to hook touch especially when the players have high speed (sat_user_maxspeed( , >500))

[hornet]

I've tested this before and found that FM_Touch was faster, and engine touch was faster then both of them.

[didoWEE]

Ok, thanks. I'm waiting for more posts
I'll try with Engine

[Backstabnoob]

You should also note that Ham gives you the ability (requirement) to limit the Touch calls by classname directly in the forward registration. It really matters on what you want to use it for as each is better for something else. Though generally speaking, engine calls are the fastest.

[ConnorMcLeod]

Yes, hook Ham_Touch is more efficient than FM_Touch, and by far, dunno what Hornet is talking about.
FM_Touch should NEVER be hooked IMO.

As said, you may prefer register_touch over Ham_Touch, depending on your needs (also supports custom class entities).

[didoWEE]

player touch player
btw which is the first index - the touched or the the toucher

[ConnorMcLeod]

first index is toucheD, always.

But if you use register_think("player", "player", "some_function")

When a touched by b, b is also touched by a, so you gonna have function called twice for sure if you hook FM_Touch or pfn_touch
If you hook with register_think there are some checks made internally to plugin, i couln't say if it is to prevent that but it seems to be something like that, anyway that should be faster to log it from a plugin rather than decript code


About the order touched and toucher, this is how it works :

game engine (not the module) on every frame detects what touchs what, and when an entity is touched it calls pfnTouch function on game dll, which is represented in code whith function name DispatchTouch.

void DispatchTouch( edict_t *pentTouched, edict_t *pentOther )

Spoiler

{
	if ( gTouchDisabled )
		return;

	CBaseEntity *pEntity = (CBaseEntity *)GET_PRIVATE(pentTouched);
	CBaseEntity *pOther = (CBaseEntity *)GET_PRIVATE( pentOther );

	if ( pEntity && pOther && ! ((pEntity->pev->flags | pOther->pev->flags) & FL_KILLME) )
		pEntity->Touch( pOther );
}

So you can see that in DispatchTouch function, if some checks are passed, virtual function ->Touch is passed which results in function CBaseEntity::Touch


If you hook FM_Touch (fakemeta module) or pfn_touch (engine module) or custom forward with register_touch (engine), you are basically hooking when pfnTouch (DispatchTouch) is called by the game engine to the dll engine.
When you hook Ham_Touch (hamsandwich module), you are hooking pEntity->Touch( pOther ); where in your plugin pEntity gonna be the first argument and oPther gonna be the second.


So, do never hook FM_Touch or pfn_touch (or old one vexd_pfntouch which is the same and kept in amxx for compatibility), prefer register_touch or Ham_Touch depending on your needs.

[didoWEE]

Thanks for this good answer