Grey Pilgrim

Archery does get pretty close with Snap Shot, Aimed Shot, and Fistful of Arrows (Fistful is technically a cone, but it recharges fast and isn't so end heavy that it's pointless to use even on a single target). There will be a little lag after Snap-Aimed-Fistful-Snapped, but not too long of one, as Snap recharges in two seconds, and Aimed in six. That's one of the fun things about that set, it's quick and snappy.

Peacebringers can do the same thing, though I'd probably respec out of one of those first three attacks after awhile... you have plenty of more needed ones that can make for a full chain later, heh.

Have fun and good luck. I'm sure you'll find some people that aren't in a tryptophan-induced stupor. I may try playing some Mario Kart Wii tonight and find out if I can stay on the track...

Well, when it happens... it's quite long. More than 1.5 seconds, for instance, as a few of my powers recharged while this happened (and they take longer than 1.5 seconds to recharge).

Visually, it doesn't act like when the server or my connection gets laggy and jumps, either. Everything is perfectly smooth, I just won't fire while Held.

Yup, it's been running CoX great for me ever since we installed it a few weeks ago. You'll want to look at your system specs and make sure it's right for you, of course, but the two work together just fine.

I'm soloing through the Indigo story arc on my AR/EM Blaster, and I'm running into some odd situations where Defiance does not seem to be working.

I'll be blasting away at a Gunslinger and get held... and suddenly neither Burst nor Slug will fire. I sit there and spam the keys, but nothing happens. I don't think this is just server hiccup, either, as it's happened more than once, and nothing else in the game is jumping, etc.

I'm also fairly sure it's not a range issue, either (I know and love how most of the mobs +40 have superior range to Blasters...). I do not get the "Out of Range" warning when hitting Burst and Slug, and before I was held, I was hitting the Gunslinger just fine- similarly, I will hit him just fine after I hit a Breakfree.

It doesn't happen that much, as I have a pretty good mitigation build going... lots of ranged defense (feels like less against Malta, though), KB, and I do my best to hold and disorient lieutenants I'm fighting. I also know what a breakfree is for (though I'd rather not use one if I can avoid it). All the same, it has happened on a few different occasions.

It also seems to be when my Blaster is held. I haven't noticed any issues when he is put to sleep. I realize that this might be something weird and random I'm encountering on my own, and not a consistent thing, but I wanted to see if anyone had encountered something similar.

Yeah, just fit in the extra goodies when you can... I can't recall when I picked up Cal Trops, but I don't think it was until the late 20s or maybe even 30 or 35. It's just a nice power to have if you can tell things are going south... gives you a bit longer to scrap it out and not test your defenses for too long (or let's your heal recharge a bit).

Updated the list... almost full if everyone shows up.

Yeah, while you can form your own teams from broadcasts and searching, the best way to find teams forming are to use server channels (Voo mentioned the two most active on Victory). It's pretty much the same way on every server, from what I've heard.

We see threads like this pop up from time to time. The issue is never that there aren't people on (unless you like playing in the middle of the night for the U.S., and on a weekday), but that people just don't know where to look. The channels will get you there.

The other good idea is to form teams of your own: when you start searching and inviting and broadcasting, it's amazing how many people are really out there.

Part of me wants to agree with the new crop of posts that says "people should just not invite the lowbies, why lock the zone down?" Because it's right, people shouldn't be doing that.

However, people shouldn't be hanging around dead in a raid, waiting for a rez, either (and some people do it, even if the leader and everyone else is doing a good job of saying "go to the dang hospital, please"). People shouldn't have abused the MA so badly, either (and don't let's bring up the debate again, just follow with me).

To quote Tommy Lee Jones in Men in Black "A person is smart. People are dumb, panicky dangerous animals and you know it." For some things, you can allow players to choose (like with their builds, etc.), with other things, you set sensible guidelines. SSK works for other zones, as higher level teams could get missions there. The same doesn't apply for RWZ. So you're not really hurting anything by locking it to 35+ again.

People are going to invite lowbies to raids, either on purpose, or by accident. And there are no reasons for a lowbie to be in RWZ, other than cross-faction MA stuff. Move the MA out to Pocket D, remove human error and tendency to stupidity and jerkness. Simple.

If you're comparing sets, also be careful to not compare a WP tank to a Regen Scrapper, for instance. The numbers are going to be significantly different there.

My MA/Regen is a LOT of fun, and very active to play. I also don't have to redraw whenever I heal (I always wonder about the Katana and BS Scrappers that are Regen... it would drive me nuts, personally). He does very well on teams (though you do have to be careful of alphas, Dull Pain and MoG help a lot there), and extremely well solo. I've been working him solo through the Praetorian arcs, and he hasn't met one of those EBs that really challenged him (I did use a pet temp power to help with Marauder, but that was more from being impatient... he kept using his tier 9, dragging out the inevitable end of the fight). I don't know how he'd do solo against AVs, but that's not really my metric for playing. I'd find it right boring, too.

Anyway, I grabbed Tough and Weave on him, and got my defenses to about the 20% mark (25% for melee, or so), as well as getting a good amount of +health, +regen, and +recharge from IOs. This has worked pretty well for me. Before IOs, he was quite solid as well... I only had issues with spike damage in Croatoa (darn Tuatha), but that was solved by grabbing Tough. No problems since then.

Keep in mind that you probably don't have to get to the def cap for anything (if you want to focus on other bonuses, can't afford it, etc.). I'm still working on my Nin/Nin build, and he's at 34%/38%/41% to melee/AOE/ranged. He really doesn't have any issues, even when he's not at the def cap. If the carp hits the fan, you can easily use caltrops or some of your other tricks to pull you through it, as well as your heal. And Divine Avalanche makes it so you don't have to get your melee defense up all the way to 45%, too.

Okay, for those of you that will be around on Wednesday, what TF sounds better? I'd like to get done in 2 hours or a little over, if at all possible. A Citadel can get done in that... could also do a Moonfire. Let me know what sounds good to you.

Sounds like we have three of us for sure, but anyone else can shout out... I will give the Isos people priority and only recruit elsewhere if needed.

I would agree with this... also, regular missions do not end up in the RWZ (an argument you could make for keeping Crey's Folly open, for instance), so there is no real good reason for lowbies to get in the zone. And yes, having the AE building in Pocket D does make a lot more sense: they dropped the AE building from Croatoa, so I wish they had done the same with RWZ, to be honest.

Anyway, Mothership raids are much harder with a lot of SK'd people, and that was my experience BEFORE SSK. It's much, much worse with people lower than that.

Sure, people shouldn't even invite these lowbies, but raids can be pretty chaotic, so it's understandable. This setup only encourages the lazy behavior that comes on raids, anyway... so many people do not run to the hospital, grrr.

They did fix the Chain Induction Proc thing... at least, the patch notes said they did, and I didn't see any posting suggesting it wasn't really fixed.