[PartialCloning]

Originally Posted by addicted2sex You can catch hud messages by catching game messages: MESSAGE_BEGIN with msgtype SVC_TEMPENTITY (23) WRITE_BYTE(TE_TEXTMESSAGE); // TE_TEXTMESSAGE - 29 ... WRITE_STRING(message)

Using register_message? I tried that but it didn't work. It seems the only way to hook it is through orpheu as you can read here:

Originally Posted by ot_207 Yes, connor is right. You need to do the function format file for EngFunc_MessageBegin, EngFunc_MessageEnd, and EngFunc_WriteString. After that you basically hook the 3 functions with orpheu and do all the dirty work.

However I figured I'd try hooking UTIL_HudMessage first to see if that works. I'm trying to create a permanent hud by blocking any hud messages that attempt to replace or use that channel. I feel like that's a better approach than re-sending the hud message every 0.1 seconds to ensure it remains on the player's screen.

[Arkshine]

Hooking 23 with register_event (more register_message for blocking) works, but you won't be able to hook message sent from others plugins.

This might help as well: http://www.amxmodx.org/api/amxmodx/CreateHudSyncObj

[PartialCloning]

Is it possible to hook/block the messages sent from other plugins through orpheu using UTIL_HudMessage? Or can it only be done through the method ot_207 mentions in the quote above?

[insanedude]

Is a fix ever planned for the sockets issue?

[addicted2sex]

Originally Posted by PartialCloning Is it possible to hook/block the messages sent from other plugins through orpheu using UTIL_HudMessage? Or can it only be done through the method ot_207 mentions in the quote above?

Maybe, the most ellegant way is to create a metamod plugin, which catches MessageBegin() to look for (msg) type==23 then catching the second WriteByte() which contains the HUD channel and change it to something else. This way you will prevent sending HUDs through that channel from ALL the metamod plugins (including AMXX itself) and the HUD messages wont be dropped. And before sending your messages make sure they wont be checked and resended through another channel as well.

[PartialCloning]

Doesn't the game constantly send messages to players (developer 1;cl_showmessages 1)? If we're hooking every messagebegin and doing our checks there, then we might as well use a repeating 0.1 task to get the permanent hud effect. It shouldnt be that less efficient, if at all.

Wouldn't you say the most elegant method is for amxx to have a hud message forward? As that only has to be called when it sends the message? While register_message can still be used to hook map/half-life mods hud messages.

[addicted2sex]

Originally Posted by PartialCloning Doesn't the game constantly send messages to players (developer 1;cl_showmessages 1)? If we're hooking every messagebegin and doing our checks there, then we might as well use a repeating 0.1 task to get the permanent hud effect. It shouldnt be that less efficient, if at all. Wouldn't you say the most elegant method is for amxx to have a hud message forward? As that only has to be called when it sends the message? While register_message can still be used to hook map/half-life mods hud messages.

I suppose you havent wrote metamod plugins ? AMXX, for example, is hooking MessageBegin() and the other message forwards (WriteByte, WriteChar, WriteShort, WriteLong, WriteAngle, WriteString, WriteCoord, WriteEntity and MessageEnd) if register_message/register_event exists. What about the AMXX timer functionality, which is using StartFrame() forward, that's called hundred times in a second with so many false if() statements and etc ?!

If you use only AMXX as a third-party metamod plugin you can compile it manually removing that channel from the "random" list, BUT if you use other plugins as well, which send HUD messages, implementing a hud message forward into AMXX will be useless (except if it hooks the game messages as well). As for the repeating 0.1 task - those are 10 more game messages send to a player = total of 320 more messages per second if the server is full. Do you still think that 0.1 task is that efficient rather than hooking MessageBegin() ?

So hooking MessageBegin is not that inefficient (again I am saying if you use other meta plugins except AMXX). If you use AMXX - a forward will be nice, yes, or compile it yourself manually to exclude that channel. But thats my point of view ...

And yes - the game is constantly sending game messages to the connected clients and those hooks are slowing the engine (having in mind that GoldSrc engine is single threaded) but that's the sad truth.

[PartialCloning]

Yeah I haven't wrote/use any metamod plugins other than AMXX. But what you're saying makes a lot of sense. That's why I was trying to avoid using a task at all costs, it just seems like the most inefficient way possible. Then when I thought of how hooking messagebegin would be even more calls, I figured it might possibly be more inefficient or close enough but comparing an amxx plugin to a metamod plugin and something that sends information to something that only receives information and blocks or adjusts it isn't very smart of me.

Since AMXX already hooks messagebegin it would still make more sense to have an amx forward right? Or would it not make a big difference if another metamod plugin hooked it?

[teh ORiON]

Hi,

Having some issues with running the newest version of orpheu on my centos linux server. Im running it together with newest dev amxmodx and newest metamod. The module runs just fine and I can hook functions just fine as well. However when trying to use arguments in the hooked function, only -1 ever gets passed as the first argument instead of the entity index. My signatures and hooking of the functions etc. are solid and well tested.

With a similar setup locally on windows, everything works just fine.

[Arkshine]

If you have SELinux, try to set to disable it or set to permissive to see if it helps.

I vaguely remember someone having a similar issue (maybe posted here?) but can't remember if we found a solution.