paroxysm

Rather than buy a tank and have no control who it goes to, how about a succeeding menu following the tank purchase confirmation menu to select which team member you want the tank to go to? Might prevent the very frustrating situation where a newb gets control of the tank and ..., everyone knows what follows. More homework for Jackie once he figures out how to control who gets a tank

Sk suggested that the stat plugins are the source of the crashes, asserting that when they were not there it rarely crashed.

Exactly Jerk, that's exactly what I had in mind when I wrote this post.

It's not pre-selecting, it's just a faster way to select your class. Depending on which class you ghost as, rather than cycling multiple times, you would press like say, 5 if chargers were mapped to 5, or 4 for hunters or 3 for spitters etc. This menu will also tell how many of that class are selected. So if all the chargers are taken, it displays something like 2/2, where 2 is the max chargers you can spawn.

That could be an easy solution to fireworks spamming, randomize the horde such that there are alot of fire resistant zombies in there.

I think we could use a new algorithm for infected class selection. Rather than having to fumble through class 1 by 1, how about a persistent menu which shows each class and its limit and index number which starts at 1...n, n = max number of contro-able classes ignoring tank. That way, you simply press the corresponding number to select the class. This will speed up the ability to select the right class when it's needed because I've noticed having to cycle through these classes takes too long when trying to hold choke points. This algorithm may have been there before, but I may be confusing this server w/ zombiegcc

The incentive of winning by doing these things has always been there but obviously hasn't been working. As for the chain hunting, the victim has to be not incapacitated. The purpose of the chain hunters is to incapacitate him or severely weaken him. I meant interval spitters who spit, then drop and die or suicide on survivors, they may opt to claw the survivor before dying. Healing the survivor after pickup window has to be really small such that if you want the points, you have to pick up and heal him right away.

I had an idea to create and use new achievements that promote teamwork such as : Survivors : If you pick up a surv and heal him w/ a kit within a few seconds, you get extra points If you shove a boomer that is later killed and noone gets biled, you get extra points. If you shoot a boomer that biles survivors, you get negative points proportional to survivors biled or that boomer gets extra points. - Should promote proper boomer handling. Healing a black n white survivor gives you extra points Infected : Death charging a smoked/jockied survivor extra points for both the smoker and charger Spit that hits pinned survivors tick for a higher point rate or get an achievement after certain accumulated damage. High pouncing a survivor who had a charger release him or a jockied/smoked survivor gets a bonus Hunters that high pounce a survivor picking up or healing another survivor get points. Chargers that charge '' '' '' ''... Jockies that lunge '' '' '' ''... Smokers that pull '' '' '' ''... Chain high pouncing a specific survivor gives extra points. Jockies/Smokers that cause ledge grabs get points For any SI that interrupt a revive by clawing a survivor being picked up get points, perhaps put this on a cool-down so that it can't be spammed by say, a bunch of spitters that are interval spitting. While I know a lot these will/can be tough to implement( at least Jackie won't get bored), I believe it will serve it's purpose w/o straying from the simplicity that we've come to enjoy about this server( i.e. no SI abilities are modified) By implementing these as achievements, it them from being repeatedly farmed in the same round. All criticism/praise is welcome.

Ok, but you can't do that in places where you can't reach the tank, such as any roof camping tank. i.e dark carny concert, swamp finale, etc.

Perhaps, or perhaps make it so that the buyer can place the witch at their cursor's facing instead of some random location. However, I'd rather have Jackie focus on fixing the crashes first before implementing new features. No sense in trying to upgrade a broken product.

If you let tanks steam roll you because your team refuses to focus on the tanks then it's your fault what happens next. Your team needs to handle that tank quickly and efficiently to prevent them from multiplying. Nearly all the games I've played, the team ignores the tank unless it rushes them. Very few teams actually chase the tank. Fireworks price is fine because they lack the benefits of molo such as long range, accuracy and modular ( easy to switch out moly to shoot or heal, you have to hold fireworks the whole time). Not to mention, some people have a bad habit of taking/shooting crates that don't belong them. The server isn't supposed to spoon feed people that can't take real world versus.

BUMP : Can we get an update of whether this is getting looked into? I don't think most players would mind the stats plugins being disabled if there's a possibility that it will fix these crashes.

I agree with Nightling, this is pointless small talk.

Lately, the frequency of crashes has increased to a point where it's not just playable since we can't even finish a campaign without it crashing. I'm taking a break until they get resolved or significantly minimized. I firmly believe that the plugins are causing crashes, disabling them 1 by 1 and observing the stability might help pin-point which plugin(s) are causing them.

The overhead here is for the most part negligible. If your plugin is lagging, such an optimization would do very little to help. I assume, ofc, that FindConVar function doesn't require loads of cpu cycles to return such as querying an external server.

No, it happened just that one time.

Quit, hi-jacking ffs, Jackie, lock this thread please.

Yes, the only problem w/ that is that you're calling FindConVar twice, 1 too many times. But, the night which you said this will take effect, the next round, it started doing the random swaps that it had done in the past.

Yeah..

Prepare your cheeks, coz this server will tear you a new one.

Looks like it should work to me.

Perhaps, replace scramble with the shuffle for some time see how it turns out, and by that I mean !votescramble would shuffle instead.

Sounds fine to me.

That sounds pretty complicated, but the problem is as well.

Stop hijacking my thread!