You could try playing with those values in a plugin to see their results, but anyway...
The x & y bounds I believe is 0.1 <--> 1.0 with -1.0 being Centered...
I believe the effects parameter is if you want the HUD Message to flash or not..
the fxtime would be how long the effect lasts..
The channel is different, if for example you display 2 messages at the same time on the same channel, the second message will overwrite the first message, but if you use different channels you can see them both at the same time on screen (need diff x & y values)..
The set_task() function basically executes a function after a certain amount of time which is specified by Float:time.. so if I put:
set_task( 1.5, "MyFunction", 2000 )
Then AMX will execute MyFunction() in 1.5 seconds from when I called set_task()..
The ID parameter is used to identify the actual task, so you could later do:
if( task_exists( 2000 ) )
{
// do something here..
remove_task( 2000 )
}
Lastly, the differences between PLUGIN_HANDLED & PLUGIN_CONTINUE are a little bit tricky... First of all, you only need to return one of those values if the function is called by AMX, like a forward function or a registered function..
An good example would be Hooking Chat like:
Code:
register_clcmd( "say", "HookChat" )
register_clcmd( "say_team", "HookChat" )
Now when someone chats (or team-chats) AMX will call our HookChat function, and if it looks like this:
Code:
public HookChat( id )
{
return PLUGIN_HANDLED
}
Then that means you will NOT see their chat appear on the screen.. PLUGIN_HANDLED basically stops execution and tells AMX that it is done (and to stop other plugins that Hook Chat as well)
However, if it looks like this:
Code:
public HookChat( id )
{
return PLUGIN_CONTINUE
}
Then you WILL see their Chat appear on screen.. PLUGIN_CONTINUE basically means that AMX should return any results by public functions and let other plugins continue also..
I hope that helps!!