Garielle

Adding to the above list...

Fire/Kin Controller hits Transfusion to get a heal off for the melee teammates battling out with a foe, foe gets knocked back, no one benefits from the transfusion.

Hyperstrike pretty much sums up my thoughts on this as well. There's a reason things are the way they are, it's called "balance". You go arbitrarily shifting numbers around, and it throws everything (not just your own character) out of whack.

Fixed

Out of genuine curiosity, how would killing off Statesman be a cop out? A cop out is usually when someone does the absolute minimum or tries to wiggle out of delivering at all. If it were Miss Liberty who was the answer to "Who Will Die", that would, indeed, be a cop-out because it's a minor character that no one really cares a great deal about anyway. I don't see how killing off the face of Paragon City qualifies though.

If you use a credit card (which you would need to do anyway in order to order online), it automatically does a currency conversion based on the current exchange rates at the time of your purchase.

Understand, there is a difference between "/petcom_all dismiss" (which is the same as clicking your dismiss button on your pet controls) and "/releasepets". The first doesn't work if your pets are frozen. The second one does.

As for the time it takes to resummon the pets, up until relatively recently, that's the way pets worked period. Every time an MM entered (or exited) a mission or crossed zones, if they wanted their pets, they needed to resummon and rebuff them. In fact, it was, once upon a time, even worse because you had to put both pet buffs on each pet individually, so multiply your buffing time by six and you have a general idea of how painful it was to try to keep up with a team who was speed running everything.

When they added the change to allow pets to zone with their owners, it introduced some bugs. One is the elevator bug which I (and someone else) mentioned already. Another was that when you zoned you could lose control of your pets. Your pets would still be there. They would still follow you around (in defensive mode), but you had absolutely no control over them and couldn't resummon replacements.

They fixed that, and when they did, we got the current bug. So, yes, it has been a painful process, however, at the end of the day, we're really not any worse off than how pets used to work in the first place. Somehow, I get images of Maxwell Smart and the "Cone of Silence", which always had some new bug in it every time he insisted on using it.

YEAH! That's what rookies are for, to crawl around in the sewers, dig through dumpsters, and other messy stuff that seasoned veterans shouldn't be wasting their time on.

In all seriousness though, especially now that the starting content is mostly open-world stuff, if you are running in a team, it's sort of pointless to team up for it. In fact, if you do, you are going to finish the arcs before you qualify for the next set of arcs offered to you. The spawn sizes and difficulty can't auto-adjust (or be manually adjusted) like the old starting content.

This is one of the reasons that I was sort of disappointed to see them go to the open world format for the starting content. After reading the explanation from Second Measure laying out why this was done, I understand it, and I accept it, but I still don't really love the idea.

For low level teaming, the sewers or AE (not necessarily AE farms, but just AE in general) are really your only viable options. Once you get past the initial stuff and can start running radio missions in KR or newspapers in PO, that changes, but until then you're sorta stuck.

Initially, the plan was to have those who use a multi-month subscription get all of their reward tokens on the front end, as soon as they paid for their subscription. Due to some sort of internal issue with it, they haven't been able to do that, yet, but it is still the ultimate goal, AFAIK.

In the mean time, if you purchase Paragon Points (same cost as a month subscription), you get an appropriate number of reward tokens immediately. What you could do is pre-purchase a block of those to sit on for stuff you may want.

Because no one wins if there aren't 50 qualifying replies.

"Slow down," Andrew said, watching the Longbow carefully, "Are you forgetting Longbow's end of our little bargain?"

If I am a winner, I permit NC Interactive, Inc. and NCsoft Europe Limited to use my name, likeness, photograph, hometown, and any comments that I may make about myself or this contest that I provide for advertising and promotional activities. I also certify that I am at least 13 years of age and am eligible to participate in this contest.

I don't necessarily believe the mistake was in combining the maintenance and the patch, I think the mistake as doing it during the regular maintenance time (a Thursday), instead of the regular patching time (a Tuesday). If they had done both the Maintenance and the Patching on a Tuesday, the recovery time would be the same was the current practice of patching on Tuesdays.

NCSoft/Paragon has had things go wrong when patching on Thursdays in the past, and when I saw they were patching yesterday, I assumed, wrongly, that they were patching to address some problem that required immediate attention. Guess I was giving them too much credit in this case.

Still, I think the idea of combined patching and maintenance is a solid one for reducing downtime, it just shouldn't be done late in the week.

Well, I can tell you that running in Windowed mode and clicking on a different process seems to have the same effect. As for ALT-Tabbing, I found that in full screen ALT-Tabbing would sometimes cause the process to freeze entirely when I went back. WindowKey-Tabbing did NOT seem to cause the freezes, but did lead to the flashing. All of this is, of course, assuming it is the process switching which is causing it, which seems to fall in line with my experience as well.

Gahhh... I saw the build was the same, so was really hoping. I can play for a while, but after a couple of hours, the flickering/flashing begins and gets worse and worse until eventually I can't see anything at all without a reboot, which is not always feasible.

Did this make it to live? Don't see anything about it in the live patch notes, but crossing my fingers.

Did this fix make it into the 2150.201111031938.1.0 build that hit live yesterday? Didn't see it in the live patch notes?