TR Exploits - Easy Points in Clan Wars : FPS / MMORPG / RTS Discussion

Alot of times in clan wars, players will be killed and will stay dead at your position to report your numbers, levels, names, etc to their clan so a counter-attack force can move in on you. Or you'll find a player AFK and only be able to kill him once. Either way, after they've been killed once..they're just a dead body and are of no more use to you... without this exploit.


Required:

1x Lvl 5+ Specialist with 'Tools' Pump 3 or higher that is NOT in a clan.
1x 'Direct Healing Tool' or 'Direct Repair Tool'
1x Dead enemy combatant from the clan you're at war with

Bring along a 'Specialist' type character with Tools 3 or higher thats NOT in your clan. Have him equip a direct tool (repair or healing) and start using it without a current target (healing or repairing himself basically). Then while the tool is still active (mouse button held down) have him mouse over the dead body and press 'Tab' to target-lock the dead player. This will rez the enemy so he can be killed again. This can be used INFINITELY until:

1) Your rezzer runs out of pharmaceudicals
2) The player /clanleaves
3) The player logs off

I can almost guarantee a free 3-4 points off most players using this exploit as the rezzing happens so fast, it will take that long to react. You just have to be able to kill him fast. And by the way, since hes being rezzed...he WILL have no armor right when he pops up, due to armor regen. And he WILL have Rez Trauma. The more you kill him, the easier it gets.

**IMPORTANT!!** Once you have the enemy tab-targetted, you cannot stop healing/repairing them, so I suggest you use a level 5 tool and don't let off that mouse button. Or you can hold down shift while healing and release the mouse button, then release shift and it will auto-rez him until one of the above workarounds occurs.

Can members say yay or nay to this being moved to a confirmed section.

yes it work for right now, however Devs are getting a patch out to fix this within the week.

I'm not sure where you're getting that info from about a possible fix. Could you link a dev discussion where this is stated please?