Talk:Damage 2.0/@comment-104.157.34.201-20160504205319/@comment-78.8.159.201-20160513065829

I usually use viral for grineer, while never the best for any specific situation, it seems decent enough when fighting anything grineer. Of course if you can take one corro and one radiation weapon, or a corro weapon with very high status chance, it might turn out to be a lot better because of the armor reduction. Still, viral with high stat chance can decrease enemy's max HP for a few secs, which can be pretty useful if you deal a lot of damage or can sustain the status effect long enough - it basically cuts his HP in half for the duration. Still, the main problem here is the inability to combine corro and radiation on one weapon unless it has innate corro/rad.

For corpus I usually go magnetic+toxin, as toxin bypasses shields which works great for human corpus with the +50% damage, magnetic helps when you fight mechanical enemies or when the toxin stops working (around shield ospreys). Still, since corpus' strognest defense are shields, toxin is pretty OP.

For infestation I usually take an aoe gas weapon for light infested and a strong, single target corro weapon to quickly deal with the ancients. Still, to survive infetsation on higher levels you need to focus on what you're doing more than on damage types, like focusing ancient healers and trying not to damage everything around them as long as they're not dead.

What seems to be a good tactic other than finding a 'jack of all trades' weapon is to find a way to deal with the strongest enemies and kill the weaker ones with that too. When fighting grineers, the biggest problem are heavy units, so you can just as well take a strong radiation weapon to deal with them first. Killing all the lancers fast won't win you the mission if you die from a bombard a second later. I find this true especially when it comes to void, where you have both ancients, heavy grineer and nullfiers, who should all be dealt with as fast as possible.

This is just my opinion. I take no responsibility for any failures resulting in using what I just said.