[diamond-optic]

im using an entity i created (throwing rocks) to do dmg and eventually kill clients..
this is how im doing it as of now:

            set_msg_block(get_user_msgid("DeathMsg"), BLOCK_ONCE)
            user_kill(object, 1)
                        
            message_begin(MSG_ALL, get_user_msgid("DeathMsg"), {0, 0, 0}, 0)
            write_byte(owner)
            write_byte(object)
            write_byte(0)
            message_end()
                        
            dod_set_pl_deaths(object, get_user_deaths(object) + 1)
            dod_set_user_kills(owner, get_user_frags(owner) + 1)

the problem im having right now is the user_kill, it creates a suicide log message.. now it probably isnt a big big deal.. but unless im wrong.. wouldnt things like psychostats pick that up as the player killing themself? and i dont want to give ppl suicides when thats not what really happened..

anyway to catch this log message and stop it from actually going to the logs? or is there a better way to do this...

also why isnt there a set_deaths native that isnt mod-specfic.. its the only thing making the plugin dod specific becuase i dont want to be bothered with adding extra stuff to cover both dod & cstrike..

[jtp10181]

there is a plugin called "vehiclekills" that blocks suicide log messages

[teame06]

The vehiclekill plugin only blocks vechilekills suicides. The code below will block message out of the hl logs. I have taken DS method into what diamond-optic wants.

#include <amxmodx>
#include <fakemeta>

new bool:kill[33];
new DeathMsg;

public plugin_init()
{
    register_clcmd("say /slay", "cmdSlay");
    register_forward(FM_AlertMessage, "fm_AlertMessage");
    DeathMsg = get_user_msgid("DeathMsg")
}

public client_connect(id)
{
    kill[id] = false;
}

public cmdSlay(id)
{
    kill[id] = true
    set_msg_block(DeathMsg, BLOCK_ONCE)
    user_kill(id);
}

public fm_AlertMessage(at_type, message[])
{
    if(at_type == 5) // Filter out some messages.
    {
        if(containi(message, ">^" committed suicide with ^"world^"") != -1)
        {
            static dummy[1], userid, index;
            parse_loguser(message, dummy, 0, userid);
            index =  find_player("k", userid)

            if(kill[index])
            {
                kill[index] = false;
                return FMRES_SUPERCEDE;
            }
        }
    }
    return FMRES_IGNORED;
} 

[jtp10181]

never said it was a direct copy/paste, just pointing him where to look.

[spq]

my solution for this is to just block all log messages for the user_kill:

//in plugin_init
register_forward(FM_AlertMessage, "log_block")
//where you need the user_kill(or anything which generates false logs)
set_log_block(true)
user_kill(player)
set_log_block(false)
//anywhere
new bool:log_block_state = false
set_log_block(bool:value)
 log_block_state = value
public log_block(type, msg[])
 return(log_block_state?FMRES_SUPERCEDE:FMRES_IGNORED)

spq

[teame06]

Actually spq way is the easiest way since you know when your going to kill the person after thinking about it for awhile. Checking for the actually player isn't really need.

[diamond-optic]

sweet thanks guys ill give this a try