[GHW_Chronic]

• Allows all clients in server to enable whichever hacks they want on themselves. While a hack is active on them, they will glow red if on T and blue if on CT.

Commands:

• say /aimbot

• say /esp

• say /speed

• say /norecoil

CVARs:

• aimbot_on
  • 1=on 0=off (Default: 1)

• esp_on
  • 1=on 0=off (Default: 1)

• speed_on
  • 1=on 0=off (Default: 1)

• recoil_on
  • 1=on 0=off (Default: 1)

• speedhack_speed
  • Speed of Speedhack (Default: 500.0)

Note: Not changing the plugin to be admin only, so do not even ask.
Note: ESP gives possibility to take up all of the hud channels disallowing other plugins to show HUD messages.
Note: Hacks will not work as good as a client-side hack would work because of lag and HL's interp. There is nothing I can do about this.

Requires CHR_Engine Stocks. (So download .amxx file instead of using the "Get Plugin" link.)
_

[Da_sk8rboy]

Sexy.
im trying it now.
+Karma.

I like it.

• Is it possible to change the settings of the speed your going when you use /speed ?
• possible to change when you press use key that when you press backwards it allows you to go backwards?

Everything elso so far is good.

[GHW_Chronic]

I fixed a couple things since your post. If you keep the plugin on your server you should download the latest one.

[Da_sk8rboy]

Alright

[GHW_Chronic]

a. I don't believe adding backwards ability is necessary. Just turn your mouse.
b. there is a speed CVAR, I just didn't have it on the post :O

[GHW_Chronic]

haha, now that u said that you are going to get 100 IMs a day from newbs asking for you to give them the edited admin only .sma

[XxAvalanchexX]

public hack3(id)
{
    if(get_pcvar_num(speed_on_pcvar))
    {
        if(!esp[id])
        {

Wrong variable?

EDIT:
I'd suggest condensing your if statements. For example, in FM_PreThink, instead of having an is_user_alive check at the top, and including the rest of your code in its braces, just check if they are NOT alive, and if so, return.

You can also turn things like this:

        if(esp[id])
        {
            if(get_pcvar_num(esp_on_pcvar))
            {

Into this:

        if(esp[id] && get_pcvar_num(esp_on_pcvar))
        {

It won't add any overhead from get_pcvar_num, because if esp[id] is false, the rest of the if statement isn't checked.

[GHW_Chronic]

good catch, fixed.

[soccdoodcss]

Sounds sweet, will probably try soon.

[GHW_Chronic]

        if(esp[id])
        {
            if(get_pcvar_num(esp_on_pcvar))
            {
                //
            }
            else
            {
                //
            }
        }

As you can see, it is either this or your way with 2 different redundant checks for esp[id]:

        if(esp[id] && get_pcvar_num(esp_on_pcvar))
        {
            //
        else if(esp[id] && !get_pcvar_num(esp_on_pcvar))
        {
            //
        }

And I simply added everything into the is_user_alive if statement because I figured checking for alive and not alive is the same amount efficient. Is it not? The effect is the exact same, if id is not alive the function ends, and in your way, if id is not alive, the function ends, however it also has to return something that won't be checked by anything.