srmalloy

Mercy was blown up; Atlas was just an eviction; Freedom Corps took over the location, moving out of their cave base on the edge of the lake.

'/screenshotui 1' to have screenshots include the UI, '/screenshotui 0' to not include the UI. Default is off.

It wasn't the 'break and run' behavior, but the fact that there would be eight or nine NPCs all clustered in front of a door cowering, and instead of escaping into the door they would scatter, often running into each other in their confusion:

There was briefly a bug back on Live where there were a couple missions where you received XP for clicking on the mission glowies; the bug was that the XP was awarded to all members of the team, regardless of their location; it was, IIRC, a mid-30s mission, so you could have level-1 characters standing in Atlas Park on a team for these missions, and have them receive tens of thousands of points of XP from a team member in the mission (in IP, Talos, or FF) clicking on the glowies (since the mission goal included a boss defeat, you could click the glowies, exit the mission, reset it, and repeat). This exploit put the most extreme AE farm to shame, producing characters ready for SOs in ten or fifteen minutes.

In Steven Sheridan's mission "Stop the Rikti Assault", there are odd clusters of NPCs cowering in fear -- several groups in front of doors, another on top of the parking structure -- that will spontaneously break up and run off when you get near them; I mistook them for hostages because I could see a cowering NPC, but not that the rest of the group were also cowering NPCs. Sometimes, after they break, they'll go running en masse across the map: It doesn't actually affect the mission, so it's not really a bug, just a case of aberrant NPC behavior that -- in the event that the other problems get dealt with, could be looked at.

Necro'ing the thread a bit, way back in the early days of the game, when Cryptic was still the development house, Jack Emmert, co-founder and chief creative officer, who oversaw the development of CoH, made the pronouncement that "Range was a Blaster's defense". This was mostly true in the early part of the game, but the revamp that gave virtually every NPC mob in the game a ranged attack -- and one that often outranged a Range Boosted Snipe -- it has become considerably less so. Some of my characters have been hit by mobs firing pistols at ranges of 240 feet and up.

The crab backpack is locked to the Soldier of Arachnos archetype. It had been part of the general unlock of costume parts until it was discovered that it caused game faults, so that change was reverted.

It's not built into the game per se, but that's "/lfg Sitter looking for farm"

In the "Find the Estate Manager" mission from Laura Brunetti, part of her Scroll of Tleilekku arc, you rescue the estate manager twice. It doesn't affect the progress of the mission -- he counts toward the rescue count both times -- but it's a bit jarring. Update: You rescue the estate manager at least twice -- I just rescued him for a third time in the mission.

You could always put Statesman on the trainer pedestal in AP — after all, he's even more iconic — and handwave it as being an audio-animatronic mannequin remotely controlled by B.O.T.L.E.R.

I hope that first date is a typo; complaining about not receiving a Notice on a TF run five days before you're eligible to receive it seems broken on your end. Had you already run Positron 1 this week? Both Posi 1 and Posi 2 are WSTs; if you run a WST before becoming eligible to receive a Notice, running a WST again will not give you a Notice. The ability to receive a Notice expires the first time you run a WST each week, whether or not you are actually eligible to receive it. So if you ran Posi 1 earlier this week, then unlocked your Alpha slot, then ran Posi 2, the server checked your status when you ran Posi 1 and cleared the 'may receive Notice' flag. If you also did not receive a PAP running Posi 2, that confirms the situation; receiving the PAP for completing the WST drives off the same tag as receiving the Notice.

That was a deliberate change; originally they did, until the devs realized that they were being used to farm — a Tanker or Scrapper with a PBAoE attack could put it on autofire and go AFK in front of a portal for hours or days, earning XP until they were more than +6 to the mission and the Behemoths no longer gave XP. Additionally, the portals spewed Behemoths forever, filling entire chambers of Oranbega maps if they got triggered accidentally and no one noticed. The XP was moved to the portal and a limit (albeit sizeable) was put on the number of Behemoths spawned from each portal.

Confusing Sky Raider Engineers is profitable, too; having them drop FFGs that buff your team's Def is endlessly entertaining.

It does make it easy to spot the people you want to put on ignore because their spew in the chat windows hides information you want to see...

Adding another digit to the counter for the number of times someone's asked for a way to adjust power selection or slotting without going through a full respec...

Not just wolves; back on Live, I stunned an Outcast in Steel and watched them stagger — while moving at the speed of a dead run — more than forty feet, leap onto the roof of a building and continue running until I lost target lock on them. According to Positron when I asked him at a meet&greet at SDCC one year, this happens when a mob has movement queued up, then gets stunned; the mob will execute the movement, repeating it over and over, until they come out of stun. It seems obvious to me that, when a mob gets stunned, it should immediately cancel any queued movement, replacing it with the 'stagger around aimlessly' movement. But that's not how it works.

If you have an open story arc with the contact — they show a book icon in the contacts list — they should never go inactive. They'll stop offering side missions, but they should keep offering the next mission in their arc until you finish it, at which point they go inactive. If they're ghosting you with a story arc active, that's a bug.

私 の 記憶 が 確かならば... (Chairman Kaga reference there) it was always just defeating the Zeus; in the entire live run of CoH, I was only ever able to force two pairs of Hercules titans to merge, but I had three or four characters with the badge for them.

In the interim, you'll just have to wonder what the RJ45 jacks on the front and back of the Mecha belt are for...

I don't remember there being a badge specifically for the Rikti portals, but I'm certain there isn't one for the portals in the Oranbega portal rooms — although since there are only seven in each room, they're not common in the Oranbega maps, and only appear in the Oranbega maps, it would take some work to get 100 of them. You'd have to hit up CoT radio missions and Ouro flashbacks to finish it.

It's not just PI; there are snipers in FF (Nemesis, Council, and Crey) and Crey's Folly (Crey). Leaving the defeat count at 100 is fine.

This alone guarantees that it will never appear on Homecoming, as modifying mob parameters to scale up with level would fork the database — the Siege Perilous server would have different mob information, with additional power definitions across the level range of each mob type to scale the abilities of the mobs better. The current implementation requires the 'purple patch' to address the limited scaling of the current mob definitions.

I have to agree with Rudra here; there's no way to stop someone from picking, say, a Fire Blaster over an AR Defender because the Blaster will do more damage, but any time you start tracking individual performance data for damage, deaths, etc., it will ultimately wind up being used to gatekeep invites to teams and leagues, the way "must have T4 Barrier" has become the 'gear score' gatekeeper for high-difficulty Aeon SFs, because that's the way people have learned works, and it's simpler to require specific 'gear' for a known solution rather than try to work out a different one.

This. The KB protection IOs are globals, not procs. There are three types of power-effect IOs. Two are procs — the "chance for X" type and 'proc120s' type. The first has a chance to create its effect every time you activate the power; the actual chance of it going off depends on its proc rate, the base recharge time of the power it's slotted in, and the recharge reduction slotted in the power; it's not intuitive, and there are other posts on the forums explaining it. The second always goes off when the power activates, and creates its effect for 120 seconds; in a toggle, the effect refreshes every ten seconds — so a Celerity:+Stealth proc will keep you stealthy (as long as you're not in combat) as long as the power you slot it in is active. The third type is globals; these act like set bonuses, and are always on, whether or not the power they're slotted in is active, so you could take both Stealth and Infiltration and slot the LotG +7.5% Recharge global in each to get 15% bonus to your recharge, whether or not either one is active — or even grayed out due to exemplar effects. The other difference between procs and globals is the effect of the IO's level. Because procs depend on the power they're in being active, the level of the proc is irrelevant; you can slot a level-50 proc in your tier 1 power and exemp down to do a Posi 1 TF, and the proc will still work. Globals, on the other hand, are subject to the level limits of the IO set they belong to — even with an attuned IO, if you exemp more than three levels below the minimum level of the set, the global stops working. So in the example above, with the LotG global in Stealth and Infiltration, you could have taken them as your last two power picks, and you'd keep the recharge bonus if exemped lower, but because LotG has a level range of 25-50, even if attuned, you'd lose the recharge bonus if you exemped below 22.

Not exactly....