5-31-20, 10:41 PM
(This post was last modified: 5-31-20, 10:45 PM by child beater 9k. Edited 1 time in total.)
(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.To be honest, I don't know if enough people actually use findIncludeClass("player") to actually warrant restricting it, not to mention its often used for small things like alarms and clickable egp screens and the such, which aren't super important but are still nice to have. sentSpawn is used for a lot of different things, and since ATGMs and the other explosives have been restricted, there shouldn't be a need to block sentSpawn.
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 all players from being able to spawn in Entities with E2.
Post your opinions or counter suggestions here.
Spoiler:
EDIT:
As to what russian said, I joined Tokos and some other servers today to take a look, and I've seen a few people already move from LFG to Tokos or other servers like Apoc or BLU3 and wherever else. I know it might not be a huge dip in playercount, but these are a few of the more active users or members. Again, there doesn't seem to be much of a reason left to block findIncludeClass("player") or sentSpawn now that the things that utilized them were restricted, considering they're used for so much else.