Jump to content

Looking for a model/saber spamming fix


Recommended Posts

Posted

As the title says. I've banned this guy for overflowing everyone out but the problem is it's spreading like fleas.

 

I don't know if any mods out there have this but I'm looking for a fix without an extra mod. I've no idea how it might work, like a DLL change or something >.<

Posted

Is this the one with the ja+ sabers mixed with some models make people who see the combination crash? If so just remove those sabers from the server.

  • 5 weeks later...
Posted

I think linuxjampded has protection against this. You'll need a mod like JA+/JA++/base_enhanced or a proxy mod like JASS, JMPProxy to protect against it on Windows servers.

Posted
@Tiger that seems to be what's shown only if you manually spammed rather than used a cfg or script. I thought Gamall's only protected against Force and /aaaaaa. Hm.
Manual spamming and spamming in a script (.cfg) fall under the same flood protection, user info change spams are fixed in lugormod and I am pretty sure Gamall's base has this fixed too (I read somewhere on Gamall's site) or perhaps base_enhanced does as suggested by Razish.
Posted

Have yet to read up on anything due to the holidays :P

 

Would help if I knew how to do the spamming myself, but too bad I don't.

 

Otherwise I'm snailing towards a custom fix since I have a billion dlls, got one done for model crash over the last few days.

Posted
Have yet to read up on anything due to the holidays :P

 

Would help if I knew how to do the spamming myself, but too bad I don't.

 

Otherwise I'm snailing towards a custom fix since I have a billion dlls, got one done for model crash over the last few days.

bind z "model hazardtrooper;model howler"

bind x "model protocol;model rancor"

and then spam z and x.

 

Doesn't have to be those binds, also could probably be a cfg and afaik it works with any models. Also it might of had some wait's in it, not 100% sure now.

 

Was effective in crashing clients off of lugormod servers prior the userinfo max changes per x-amount of time patch. I am guessing this is the issue on base.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...