[xPaw]

PHP Code:

public eSpawn(index)
{
      g_bIsEnraged[index] = false;
      _resetRage(index);
}

public client_disconnect(index)
{
      g_bIsEnraged[index] = false;
      _resetRage(index);
}

public client_connect(index)
{
      g_bIsEnraged[index] = false;
      _resetRage(index);
} 


You're calling the func here without any + 123

[unnyquee]

Yes, because these function aren't called through tasks

[Exolent[jNr]]

RegisterHam(Ham_Spawn, "player", "eSpawn");

You should register it as post hook and check is_user_alive().

[unnyquee]

Solved

[grimvh2]

Start making cvars. so you can almost control evry lil thingy of it.

[Anonymous]

Simple but effective.
+k

[rumbeto]

It would be great if you make this plugin so every utr_ragefrags frags you get raged. For example: every 5 frags you get raged. Or maybe set a cvar to have a choice to do that.

[worldspawn]

yeah it will be cool, and may be make a cvar to choose an effect? (glow or trail, cause glow is not beautiful)

[orange]

this plugin with csdm caused many issues for me when it was first made but i did not save error logs, cool idea tho.

[Exolent[jNr]]

1. If a rage player switches weapons, their speed will be returned to normal.

2. If a player becomes "raged", the next round the player's speed will be put to 250.
That is wrong:
a. If there is freezetime, that player will be able to move.
b. That player could be holding a weapon that has a different speed than 250.
You should just remove the speed setting.

3. Remove the cvar and boolean checks in _setRage.
It is only called when it is needed and those checks are made already before the function is called.

4. You don't need to make every function "public".
Only public functions should be hooks/forwards/handlers.

5. In the health regen task, you should check if player is alive before getting health.

6. The reset rage task requires the player's index + 123 to the function.
You need to add 123 to the player's index when you call the function.

Approval pending on changes.