195
« on: February 06, 2011, 02:40:21 am »
my strategy for basically every level so far has been to run in with haste, then alternate wet flash and cold flash as fast as possible. if you're in single player, i would run to one side of the bridge, kill everything, run to the other, repeat as necessary. goblins move slow and attack slow; most of their swings and arrows will miss, so you'll steamroll them as long as you don't use a shield.
alternatively, try using cold lightning flash after the wet flash against armored goblins. the cold will do increased damage and freeze, and lightning should have its damage boosted twice from wet + armored. on the other hand, goblins have so little health that just wet + cold is enough to gib them in one cycle, so it's optional.
speaking of personal shield, i almost never use it, except when fighting enemy casters (or teammates). i have an easier time using heals and elemental protection auras whenever i get wet or cold or set on fire - since there's no knockback except for certain sources, it's much easier to execute my cheap bs.
i always crash after beating grimnir though, so i've only played the later levels in games hosted by others.
random tip: healing boulders are a great way to deliver large burst heals on to yourself without using mines that have the liability of healing enemies or launching other players, usually directly into a group of armored orcs; they're also useful to heal players out of the range of a nova without needing to commit several seconds to aiming and maintaining a beam, especially if the target is being chased by a dozen orcs and will die instantly if they stop moving to heal, or to let you heal them. also, it doesn't appear to have knockback or knockdown if you only queue one rock (which is all you need); at least in the games i've played so far.
unrelated: really wish they'd put some options in the menu to disable all the superfluous garbage like lighting and pixel shaders that serve no purpose except to melt electronics. and it'd be nice if the devs could do something about the near-one-second input delay in menus.