I need a list of all issues in the current version of Pro Mod

[.]

As some of you may know, I've been less involved in the development of pro mod for the past 6 months or so. I've been busy, but also been bombarded by bad news back to back over this time. It's been hard for me to stay motivated to get anything done, not even just talking about pro mod. I'm not here to rant about that though. I just wanted to let you guys know that I plan on making one last update. I know I've talked about stepping down before, and I've even done it a couple times (then come back 2 weeks later) but I've finally reached the point where I realize I need to finally step down. I'm just being selfish by wanting to keep my name on the project, while not creating any new content. It's not fair to the other people working on the config, or to the community.

I want a list of all the issues remaining in 4.5.2. I plan on fixing all of these issues, and finishing as many of the passion projects I had remaining for the config as I can. I will then release them in one final update in the near future. I will be looking for someone to continue working on the config if they want to, but my goal is to make a release that is good enough to justify being the final one if it does end up being that. And even if it isn't the final update, I want to put out an update good enough to leave the community with a good impression. I want to be remembered for the good stuff, not the times I've gotten in arguments with people, put out a buggy update, or rage quit. I want to apologize for all of that.

After I step down it's hard to say how much involvement I will have in the community. I will continue working on passion projects and probably post them as individual plugin releases on the forums when I finish them, but aside from that I really don't know how active I will be. Anyways, please post any issues you know about here so I can fix them. I don't want to rush this update, so I will probably not be releasing it before April. For the other people working on the config with me, I don't expect you to, or ask you to help me with this update. I'll take whatever help I can get, but this is my job to finish and I don't want to dump the work load onto other people as I have in the last couple updates. When I make my final release I will probably write up a short little blog thanking everyone and whatnot.

[ninja]

Bring back 3.2

[fig newtons]

silent jockey

[High Cookie]

Jacob thanks for your work and letting me try my hand at it.

[ZerOxShadows]

RIP

[K0range4]

I believe primary weapons are still being punched out of survivor hands by the tank. Once the gun has been punched away it cannot be picked up again. It seems to happen when they are punched with a melee weapon out. It doesn't happen all the time, but I've seen it maybe four or five times in the past few weeks.

[.]

I believe primary weapons are still being punched out of survivor hands by the tank. Once the gun has been punched away it cannot be picked up again. It seems to happen when they are punched with a melee weapon out. It doesn't happen all the time, but I've seen it maybe four or five times in the past few weeks.

this must be on 4.4 because we removed that plugin in 4.5

[3yebex]

this must be on 4.4 because we removed that plugin in 4.5

Probably your biggest problem right now Jacob is that (mostly) everyone downgraded back due to 4.5 being unstable. I don't think anyone here is willing to upgrade their servers to it and start bug testing with PUGs for you now, it's a bit late.

[ika]

Probably your biggest problem right now Jacob is that (mostly) everyone downgraded back due to 4.5 being unstable. I don't think anyone here is willing to upgrade their servers to it and start bug testing with PUGs for you now, it's a bit late.

False. I don't think any servers currently have 4.5.2 running, but this weekend we'll put up a 4.5.2 test server. Maybe we can get a few pugs going in the name of science  .

In the future, I'm really hoping that you guys would be willing to release a test release of new versions of configs so that we don't end up reverting back to a previous version 2-3 times when problems arise. Or possibly gathering a group of people who are willing to help test before release. I know personally that I could definitely grab a group of people to play with some of you developer guys to try to find some of the problems that don't arise when you're solo testing before it gets released.

[Slay]

In my servers with pmod 4.5.2 if someone throw a molotov to the tank, he stay onfire until he died (the fire damage its really op like vanilla) and also the 3rd pass burned tank, he dies really fast too, it seems fire in pm 4.5.2 its really op, so i downgraded this two plugins (si_fire_inmunnity.smx and l4d_tank_control.smx) to his 4.4.2 versión and now everything its working great.

[fig newtons]

Tank uppercut getting survivors stuck in the ceiling

[3yebex]

Tank uppercut getting survivors stuck in the ceiling

How the hell is the Tank doing uppercut? This was fixed by Valve a few years ago by making player-zombie Tanks only do right-hooks in versus mode.

[fig newtons]

Uppercut is an artistic license I guess. It's when a survivor jumps while getting punched and gets stuck.

The change you're thinking of was added to promod by circlesquared to prevent tank punching survivors/hittables with his back turned. I didn't know valve rolled it out to vanilla as well.

[3yebex]

Uppercut is an artistic license I guess. It's when a survivor jumps while getting punched and gets stuck.

The change you're thinking of was added to promod by circlesquared to prevent tank punching survivors/hittables with his back turned. I didn't know valve rolled it out to vanilla as well.

No, the change circlesquare did affected the hitboxes of the tank's punches (I believe). Valve went a bit lazy, and instead of solving the issue just made it so that all PZ Tank punches were right-hooks always. Circlesquared's fix still allowed for any 3 random punches, just attempted to fix the hitboxes.

[Visor]

I'm ready to fix everything that needs to be fixed with promod(perhaps not the way you'd expect me to). I'm not interested in taking over, but I don't mind releasing just one, first and final version of my own, one that would illustrate my vision of competitive promod. No, it wouldn't be a renamed EQ, but it would be a config that is very competitive and disregards all prejudices, such as "well can't use this feature since it would make promod so much like EQ!". Most importantly, it would be absolutely bugless day zero and require no patches.

If jacob likes my offer, he doesn't have to bother working on the last version anymore. His enthusiasm is obviously nowhere to be seen. Doing something because you enjoy it and doing it because you're tortured by leftovers of the responsibility you once had are two different things, which also lead to two wildly different results. But keep in mind that if you accept my offer, for that one final version that I have in mind, I will promote my own opinion in terms of what's best for promod to the highest rank, and may or may not take into account what others think. At the end of the day, the choice between promod 3.2/4.4/xxx is always up to the server admins.