What would you resurrect?

It works like this:
the server runs a small lua mod that prevents people from using /players or seeing ping in the score screen.

You have two players: Player A is the person being tested. Player B is the "netlamer".

The players duel, or the A shoots while B dodges. After a few rounds, A reports whether the hit detection and movement felt good, bad or normal. At this point, B says they are changing, and either changes the setting to be tested, or doesn't, without telling A what was changed. B keeps track of what setting was actually used, and what A reported. This is simple single blind test, which isn't ideal, but should be good enough to show if there is a major effect.

Settings tested include FPS, various maxpackets settings, and scripts that change maxpackets every time the player presses or releases a movement key.

I've done this with few skilled players (silver from U5, elf from WS among others). There wasn't any noticeable correlation between when the maxpacket script was in use and when they thought hit detection was bad. As I said before, very low FPS is noticable (it makes the player look a bit jerky) but even then it didn't make the target unhittable. This doesn't mean that maxpackets has no effect, but it does make it very unlikely that it is the problem that people make it out to be.

If you have demos of what you think is etpro hit detection screwing up, I'm happy to look at them. Please provide the time it happened, and describe both what happened and what you think should have happened. If you have specific scripts you think are exploits, feel free to send those too. You can email them to reyalp (at) gmail.com

Be aware that demos don't show you exactly what you saw. In particular, it looks like you are shooting behind your target in proportion to your ping.

Thanks for the demo. It's certainly interesting, and looks like it either shows something broken or extremely bad luck. I don't see any particular indication lag or lolmaxpacket scripts are involved.