If the chainsaw is to be added to the server it will be added as a new pack and not as an addition to any of the current packs.

Flamethrower, MP5, Chainsaw could work as a complete breacher set. Perfect against campers, pretty much useless anywhere else.
Alternatively, you could introduce a small firearm custom weapon. Perhaps a Deagle(24 Damage pistol that you can move and shoot).

I've tought about adding it but doesn't the chainsaw's damage change depending on the FPS's of the player being attacked?

Yes it does.
The player gets damaged depending on number of frames he spends in contact of Chainsaw's blade. So, a 60 FPS player takes twice the damage than 30 FPS players. But the chainsaw's knockdown is still very effective against 30 FPSers.

Also, players used to 60 FPS are unlikely to go back to 30 FPS just to avoid a little bit chainsaw damage.

well, I was present in the first four rounds and VU dominated them all.

Damn roofers - VU won 11-0
Bikers vs Cops - VU won 92-38
Cabs vs Phil - VU won (I don't remember the score)
Cherry Backyard - VU won (I think) but I left it as 4-0, I'm really sorry for leaving, I do not know what happened afterwards but I had to do some things and UF took too long.

Congratulations guys and good luck next time UF.

PD: We started playing on CTF 5 but we had to move due to some bugs.

The 4th round was Bikers vs Meuseum. Cherry pops was never played :-/

Is this clan war tomorrow(Saturday)?
VU will show up 17 GMT(10 PM Pak time, 10:30 PM Indian time) - 14th October 2017

Friday is looking hard. We will try, but no promises.
Is 17 GMT fine? I won't be there personally, so someone else from VU would need to coordinate.

I'd still like to get this done on the weekend like normal people :-/
So, in case people don't show up on Friday, lets do Saturday 17 GMT.

I've faced the pickup problem in Squirrel plugin. It is hard to reproduce.
What happens is, when the script creates, removes, recreates pickups frequently their IDs get mixed up internally.

So, when you compare the pickup ID before deciding what to do with the picked event, you are dealt with a wrong ID, which produces a wrong behavior. Sometimes the flag could act like a barrel, teleport or vice versa.

Workaround: Generate a unique ID for the pickup when it is created. On all pickup events, use that unique ID instead of internal pickup IDs.

or, compare pickup's Model instead of it's ID. Since the red/blue flag's model is unique, it would work. However, the problem will persist in case of barrels or teleport pickups.

GG

Eddy is god.