Forum

Unless I'm blind or dumb (which is possible) I don't see that option anywhere in Assist or Assist's various UScript files' settings. Must be something they added, which should make it a cheat or untracked server, at least I think...

This might be a function that might be used to detect Early 203(or GP).

Code: [Select]

Function Spamprotect()
{
local Projectile DisableProj;

foreach Level.DynamicActors(Class'Projectile',DisableProj)
{
if ( (DisableProj.Instigator == None) || (DisableProj.Instigator.PlayerReplicationInfo == None) || (DisableProj.Damage == 0) )
{
continue;
}
else
{
DisableProj.Damaage = 0.0;
DoWarning("203 Shot at spawn", p);
}
}
}
Not tested the code, but I think it might work without much change.
Might have to check class of the projectile to be accurate. But if we merge the two, we should be able to add an optional(Server Owner) spawn protection.

So question is if we should add it, and what punishment, at the moment it just makes the projectile and grenade to cause no injury.

Its weard hey that clans must puth in a mod ore a change by closing slots in server to stop rpg. so far I see in this poll people shout clearly that rpg is not ther wish. Hope the reaction to those voters will be correct.  and we not only must look trough a glass plate waiting till something happened.   21-09-2016  I see 26 for and 6 aganst
Looks like a honest poll this time.  ( FEELINGS) 

Do you mean that there's no option for it yet, but it could be made to be possible that you could kind of introduce a variable and value for it at ini file and use that as global variable inside the function? Or is it something server based custom configuration where serveradmin would edit uscript file to change the value from hardcoded to variable?

"why aren't you coding it already"

cool if we're about to have the feature available some day would it affect on other violation shortbans such as excessive prone shooting etc as well or do they have their own functions to execute the ban?

IGC has now server message pointing updated rule out, hopefully now the rule is seen. Realised again how important it is to use servermessage.cfg with correct encoding, needed to restart the server like ten times to get it working right lol