I have the same problem, but the real challenges for me are: <br> <br>(1) All the "bells and whistles" text for skills/spells. With it flying around, I can't tell the difference between a failed strip vs. a successful strip that didn't work because of iron grip. These differences really matter. <br> <br>(2) Doing things to keep groupmates alive. Someone you're grouped with is bound to do something reckless and get PKd. <br> <br>Anyway, FWIW, here are some things I do to make it manageable. <br> <br>1. Keep track of how many people can lag me out and whether it's possible to get permalagged. <br> <br>If there's a solid chance of me getting permalagged, I'm not going to be typing in very many commands except for flee!!! when it starts to look like I might fall in 3 rounds, and am going to be hoping my allies dish out the damage quick enough to win. <br> <br>2. Related to the above, keep track of how much damage I'm taking and how quickly. <br> <br>If I think I'm going to drop in 3 rounds and the guy I'm targetting is not, I'm hitting flee. Ideally, everyone in my group is going to be doing this. If I return to reengage, it will be because I think I can target someone else that is going to drop in 3 rounds and/or I'm grouped with someone that will survive longer than 3 rounds. <br> <br>3. Keep track of who is getting lagged. <br> <br>Pile on the mage that forgot fly and is getting tripped. Expect your allied mage to die if he forgot fly and is getting tripped - so lag out the tripper. <br> <br>4. Keep track of failed skills. <br> <br>This is the hardest because skills can fail for several reasons and the flowery text combined with the PK spam makes it really, really hard to discern why a skill failed until you look at the log some time later. Ideally, CF would kill all the flowery text for failed skills. <br> <br>Anyway, looking at the above, I guess what I care most about is lag because that is the easiest way to PK.