Functions

messages.inc

amxmodx 1.8.2 hg65

Function Type Description
emessage_begin native These are the same as above, except that the messages sent
are also sent to all other plugins and Metamod plugins.
This means that if you send one of these messages, other plugins will
be notified, which was previously impossible.
BE CAREFUL! Using these incorrectly, or not for their intended purpose,
could cause infinite recursion or something just as bad.
NOTE! These natives are experimental.
emessage_end native This function has no description.
ewrite_angle native This function has no description.
ewrite_byte native This function has no description.
ewrite_char native This function has no description.
ewrite_coord native This function has no description.
ewrite_entity native This function has no description.
ewrite_long native This function has no description.
ewrite_short native This function has no description.
ewrite_string native This function has no description.
get_msg_arg_float native This function has no description.
get_msg_arg_int native Gets the value of argn.
get_msg_arg_string native This function has no description.
get_msg_args native Gets number of arguments that were passed to this message
get_msg_argtype native Gets the argument type of argument argn
get_msg_block native This function has no description.
get_msg_origin native Gets the origin of a message
message_begin native These functinos are used to generate client messages.
You may generate menu, smoke, shockwaves, thunderlights,
intermission and many many others messages.
See HL SDK for more examples.
message_end native This function has no description.
register_message native Lets you directly hook a message in the engine!
You can overwrite the message before anything happens and either let the message continue
or fully block it. Here is how it works:
If you hook a message, the message is stored but not sent. You have the opportunity to
not only execute code, but to get/set the contents of the message, before you choose to
either block it or let it go on its way. The hooked function will be passed a msg_id, msg_dest, and entity index.
The return value can be passed to unregister_message() to stop the message from being hooked
set_msg_arg_float native This function has no description.
set_msg_arg_int native sets the value of argn.
set_msg_arg_string native This function has no description.
set_msg_block native Sets/Gets what engine messages are blocked.
unregister_message native Unregisters a message hook previously created with register_message
You must pass the proper message id, and return value from the message to unregister the message successfully.
write_angle native This function has no description.
write_byte native This function has no description.
write_char native This function has no description.
write_coord native This function has no description.
write_entity native This function has no description.
write_long native This function has no description.
write_short native This function has no description.
write_string native This function has no description.