

Unforunatly I wanted to be able to use those zones as rooms instead of having to do the rooms through Lua (which I consider slower to loop through rooms on the

But that's not a dealbreaker.

In that case, I suggest adding these two commands:


This will make sure the players are close AND do not have a raycast wall between them and the position.
The
typeparameter can be used to specify if the players should be considered in range either raycasting everything (walls and obstacles) or only walls (obstacles won't count).
Another nice addition would be

All of these are easily done with Lua, but that means they're also slower.
Currently, in order to achieve the same result, it's non practical in Lua, at least for heavy servers such as mine.
EDIT:

Will close a player's menu, and call the menu hook with button 0 (cancel).
EDIT:
An option to enable pistol auto-fire when


EDIT:
Can we have some kind of


There's many reasons to have that, one of which is that the

Also, there's more benefits to the


There's a few more reasons, but if any of the developers are interested, I can explain the rest through PM/DM.
EDIT:





And possibly player rotation and position, to make the hook more efficient.
returns:


Why?
There's no way to receive a projectile ID using the

EDIT:


If that's too complicated, perhaps

And, perhaps,


1
2
3
4
2
3
4
{ [1] = 99153, [2] = '76561198087950619' }
And then, using the respective functions, it would be possible to get the rest of the data, depending on what is needed.
edited 11×, last 20.07.21 05:31:27 pm