5-31-20, 09:29 PM
(5-31-20, 09:26 PM)Demonik1 Wrote: So I'm gonna be making another suggestion on here, this is a big one so I'm gonna give you guys an option to respond about your opinions on it.an extra: admins should investigate certain e2s, with permission or not incase some e2 is suspicious, such as high firerate on a anti-lfs missile launcher
I believe that we should restrict the ("players") string from being allowed inside of the findIncludeClass function. If we find a way to disallow this string from being used with this function, no player should be able to target any players in the first place, and that's what this function does if you include this string.
Another part of this is that you can also use it to target entities and ultimately include every single type of drone or LFS which in all cases will be against the rules. You can do it like this
Spoiler:
If we find a way to restrict the ability to target other players with E2 (unless you're an admin) then we can ultimately put a big stop on abusive E2 until a workaround is found.
I have a second suggestion to this if you guys don't like the first. We could just restrict the ability to spawn in Entities with the sentSpawn function. This will prevent users from being able to spawn in Entities with E2.
Post your opinions or counter suggestions here.
Spoiler:
we should set certain firerates of the e2s to maybe about 1 missile per 5 seconds (or 10 if you guys want)
Feel free to post a poll on what you want, i don't care what your opinions are on how to get certain rules added and some restricted