[PurposeLessx]

Hello guys,
I need to block using status command because of it's showing player steamid etc.
I know it's not client-side so I believe we can block it with amxx.

Not blocked with register_clcmd.

Thanks for helping

[HamletEagle]

You don't need to block status. Just make your server steam only if you are bothered by steamid changing exploits.

[fysiks]

This violates Valve's Policy of Truth which this community abides by. Also, before asking a question on the forums, search first. This question has been asked before.

[PurposeLessx]

I have not ever seen the answer of this problem.

**There is a rocket game and in the end players are dying.
And Players are dying with queue of status

PHP Code:

get_players(players, inum)
for(new i=0; i<inum; i++) 


I don't want anyone to show who is last in the status. So am I not able to disable it ?
Thx for helping

[OciXCrom]

**There is a rocket game and in the end players are dying. And Players are dying with queue of status

What?!

[PurposeLessx]

I don't know what am I able to explain it to you with my poor English. I will try to explain.
I am using that command "amx_rocket @T" and I rocket Terorrists.
They are jumping from high place and falling down not to die.

PHP Code:

status
#1 PurposeLess blabla...
#2 Colditz blabla...
#3 Alliedmodders blabla...
#4 Forums.alliedmodders blabla...
#5 PurposeLessx blabla...
#6 nick blabla...
#7 OciX blablaa. 


The last person in the status (the #7 in my example) is going to die last.
They are going to die by turns. I want them not to learn who is the last so I want to disable status.
I should disable status even if I cannot block it. I really need this plugin.

[Relaxing]

Originally Posted by PurposeLessx I don't know what am I able to explain it to you with my poor English. I will try to explain. I am using that command "amx_rocket @T" and I rocket Terorrists. They are jumping from high place and falling down not to die. PHP Code: status #1 PurposeLess blabla... #2 Colditz blabla... #3 Alliedmodders blabla... #4 Forums.alliedmodders blabla... #5 PurposeLessx blabla... #6 nick blabla... #7 OciX blablaa.  The last person in the status (the #7 in my example) is going to die last. They are going to die by turns. I want them not to learn who is the last so I want to disable status. I should disable status even if I cannot block it. I really need this plugin.

You can't block this clcmd but you can check if players are listed in a ascending or descending form based on their id's. If they are so you can "rocket" the player with the highest/lowest id.

[PurposeLessx]

Can you make it as you say?
That is plugin I have.

Spoiler

PHP Code:

public rocket_terrorists()
{
    new players[32], inum;
    static Uid;
    get_players(players, inum, "a")
    for(new i; i < inum; i++) {
        Uid = players[i];
        if(get_user_team(Uid) == 1) {
            emit_sound(Uid, CHAN_WEAPON ,"weapons/rocketfire1.wav", 1.0, ATTN_NORM, 0, PITCH_NORM)
            fm_set_user_maxspeed(Uid, 0.01)
            set_task(1.2, "rocket_liftoff", Uid)
        }
    }
}

public rocket_liftoff(victim)
{
    if(!is_user_connected(victim) || !is_user_alive(victim)) return
    
    fm_set_user_gravity(victim, -0.50)
    client_cmd(victim, "+jump;wait;wait;-jump")
    emit_sound(victim, CHAN_VOICE, "weapons/rocket1.wav", 1.0, 0.5, 0, PITCH_NORM)
    rocket_effects(victim)
}

public rocket_effects(victim)
{
    if(!is_user_connected(victim) || !is_user_alive(victim)) return
    
    get_user_origin(victim, vorigin)
    
    message_begin(MSG_ONE, get_user_msgid("Damage"), {0,0,0}, victim)
    write_byte(30)
    write_byte(30)
    write_long(1<<16)
    write_coord(vorigin[0])
    write_coord(vorigin[1])
    write_coord(vorigin[2])
    message_end()
    
    if(rocket_z[victim] == vorigin[2]) {
        rocket_explode(victim)
    }
    
    rocket_z[victim] = vorigin[2]
    
    message_begin(MSG_BROADCAST, SVC_TEMPENTITY)
    write_byte(15)
    write_coord(vorigin[0])
    write_coord(vorigin[1])
    write_coord(vorigin[2])
    write_coord(vorigin[0])
    write_coord(vorigin[1])
    write_coord(vorigin[2] - 30)
    write_short(blueflare2)
    write_byte(5)
    write_byte(1)
    write_byte(1)
    write_byte(10)
    write_byte(5)
    message_end()
    
    message_begin(MSG_BROADCAST, SVC_TEMPENTITY)
    write_byte(17)
    write_coord(vorigin[0])
    write_coord(vorigin[1])
    write_coord(vorigin[2] - 30)
    write_short(mflash)
    write_byte(15)
    write_byte(255)
    message_end()
    
    set_task(0.2, "rocket_effects", victim)
}

public rocket_explode(victim)
{
    if(!is_user_connected(victim) || !is_user_alive(victim)) return
    
    get_user_origin(victim, vec1)
    
    message_begin(MSG_BROADCAST, SVC_TEMPENTITY, vec1)
    write_byte(21)
    write_coord(vec1[0])
    write_coord(vec1[1])
    write_coord(vec1[2] - 10)
    write_coord(vec1[0])
    write_coord(vec1[1])
    write_coord(vec1[2] + 1910)
    write_short(white)
    write_byte(0)
    write_byte(0)
    write_byte(2)
    write_byte(16)
    write_byte(0)
    write_byte(188)
    write_byte(220)
    write_byte(255)
    write_byte(255)
    write_byte(0)
    message_end()
    
    message_begin(MSG_BROADCAST, SVC_TEMPENTITY)
    write_byte(12)
    write_coord(vec1[0])
    write_coord(vec1[1])
    write_coord(vec1[2])
    write_byte(188)
    write_byte(10)
    message_end()
    
    message_begin(MSG_BROADCAST, SVC_TEMPENTITY, vec1)
    write_byte(5)
    write_coord(vec1[0])
    write_coord(vec1[1])
    write_coord(vec1[2])
    write_short(smoke)
    write_byte(2)
    write_byte(10)
    message_end()
    
    user_kill(victim, 1)
    
    emit_sound(victim, CHAN_VOICE, "weapons/rocket1.wav", 0.0, 0.0, (1<<5), PITCH_NORM)
    fm_set_user_maxspeed(victim, 1.0)
    fm_set_user_gravity(victim, 1.00)
} 


[fysiks]

It looks like everybody is affected nearly simultaneously so I'm not sure why the order matters.

You probably need to fix the glitch that is allowing them to not die instead. That would be the correct way to go about this. My first guess is that sending the jump command doesn't work because if you are falling then you can't jump.

So, you'd likely replace sending the jump command with something else like setting their z velocity or something like that.

[klippy]

Originally Posted by fysiks It looks like everybody is affected nearly simultaneously so I'm not sure why the order matters.

I think the issue OP has is that the last player in "status" will die last because player frames (and deaths) are processed that way, if they all die within the same tick.
Hiding of the "status" command is surely not the right way to tackle this, but this was clearly going towards XY problem (if the OP didn't reveal what the real intention is).

I think the best would be to know what should actually happen if they all ought to die at the same time?