ClawsandEffect

This.

Neither of those procs are affected by recovery debuffs. If you get your recovery debuffed to the floor (i.e. not gaining any endurance at all) the proc will still fire and give you a minimum of 10 endurance back.

So, if it happens to proc immediately after using a crashing nuke or a crashing tier 9 like Unstoppable, it will still give you endurance back, regardless of the fact that you're not supposed to be getting any for 10 seconds.

My build is built on the cheap, like all of my builds. I don't have purples slotted, or ridiculous amounts of recharge from other sources. My global recharge is sitting at around 53.8%, which is just barely enough to achieve Perma Dull pain, but ONLY if my Hasten is 3 slotted to the ED cap as well.

So that 2 to 5 seconds is the difference between whether my Dull Pain is Perma or not. Like, it comes back up right as it's crashing.

Actually, Super Reflexes/Anything Tanker.

SR doesn't need the defense boost from Storm Kick to soft-cap on SOs. Combat Jumping and Weave will do it.

I doubt it will unlock a new slot, but the odds are good of it unlocking a new tree for an existing slot.

A Judgement power that replicates his signature attack seems most likely in that regard.

And if I had to put money on it, I'd bet on Ms. Liberty getting his powers and being the new contact for the STF. Seems logical that if the Well's powers were going to go to someone, it'd be someone in his bloodline.

BaBs is already a trainer in Atlas, all they'd have to do is move him to the spot Ms. Liberty currently occupies and it'd be a nice way of tying that together.

Obviously, the MLTF would have different dialog than the STF, probably mentioning his passing and all that.

That's how I'd do it at least.

I'm fully aware that the prevailing opinions on the forums very seldom bear any resemblance to the opinions found in game.

The conniption fits thrown on the forums over various things go largely unnoticed by the majority of the people who play the game. That's because the majority of the people who play the game either A) Don't realize the forums exist, or B) Could not care less about them. The whole "I don't like how the game is forcing us to run Incarnate Trials all the time" that pops up now and then....yeah, you don't hear that in-game. At all. In-game the people who like the trials play them, and the people who don't....don't.

It's incredibly conceited of us forumites to think that our opinions hold so much more weight than the average player, simply because we like to post them here. I'm not excepting myself from that either. Even if by some quirk of fate 100% of the forums agrees on something, that's still less than 10% of the game's population you've heard from. And there's no guarantee that the other 90% or so is going to have a similar opinion.

The forums give a pretty good cross-section of the playerbase, with one exception; The people who would rather just play the game instead of discussing every aspect and arguing about it are not represented. That's because they're logged into the game instead of here.

Except that wasn't so fun for the other people.

I assume you mean back before they implemented the anti-one shot rule?

Yeah, that sucked for anyone who wasn't a stalker. Instantly killed by a guy you couldn't see until he killed you? What brain trust thought that would be fun for anyone but the one doing the killing?

The way PvP was shoehorned into the game is probably a pretty major regret for the dev team. If the game had been designed with it in mind, maybe it wouldn't have been so unbalanced. Just the way a lot of the powers work alone makes it aggravating. Getting caught by Telekinesis on a scrapper or tank while not having 3 Breakfrees on me was one of the most aggravating things in the entire game for me. You were held for as long as the person holding you had endurance, or until you were dead (almost always the latter).

I don't think PvP itself is regretted, just the way it was crammed into the game as an afterthought. Though they did save themselves by not allowing open world PvP. Given this game's player's general attitude toward PvP, open world PvP probably would have been the death blow 5 years ago and we wouldn't be having this discussion now.

You need to go back and watch those again. The only Batman movies Tim Burton was involved in were the first two, with Michael Keaton playing the title role. He was far from an "insane psychopath vigilante murderer" in them. In fact, I can't think of a single person Batman has actually killed in any of the movies, including the most recent ones. He refused to save Ra's al Ghul's life in Batman Begins, but that's not quite the same thing as murder, since Ra's caused the situation that led to his death himself. He basically just let Ra's reap what he sowed rather than intervene (he also knew he would never remain in prison, he was too well connected).

I personally never had a problem with Statesman as a character. Sure, he's kind of a generic patriotic Superman clone, but there are worse characters in comics.

Power level-wise, I place him somewhere between Captain America and Superman, which is probably about where he was meant to be. He's tougher and stronger than Cap, but not as virtually omnipotent as Superman is often portrayed.

People call him boring, but how exciting would you be if you'd been saving the world for 80 years? Sure, he's still physically in his 30s, but the guy has the mind of a man whose been alive for over 100 years. He was given longevity, that doesn't mean he was given the mental capacity to endure it. Neither Cap nor Supes have had to deal with watching everyone they love grow old and die while they remained young (Cap's loved ones did, but he wasn't there to see it) I'm sure Marcus knew he was going to outlive his kids, the shock to him was in how it went down.

To be honest, the guy is probably looking forward to his impending death. It's the first chance he's had to relax in decades.

You know who is going to be the most pissed off if Statesman doesn't die?

Statesman himself.

I find myself forced to agree with Tenzhi this time.

It doesn't matter that we were told about it. It doesn't even matter who it is that's dying.

What matters is the how, the why and the story surrounding it. There has never been a death of a major character in any comic book that wasn't leaked or released in advance. None.

They told us Superman was dying, they told us Captain America was dying, they told us the Human Torch was dying. That by itself doesn't make it special. It's the story involved in it that makes it special.

But please devs, for the love of all that is comic-booky, one up the major comic companies and let your major character STAY dead! Killing off a character so you can write a story arc about how much they will be missed and showing off how human and real your characters are, only to bring the character back a year later is just idiotic. I've always thought that.

Killing off a character and bringing them back is just a cheap excuse to make a quick buck and then continue to profit from the character later. Whoever it is you're killing (I'm not entirely convinced the spoiler isn't a red herring to throw us off), they need to stay dead.

Yeah.....that's pretty aggravating.

I think what he was saying is that game's developers responded to the players' demands that ALL the bugs be fixed before they released new content.....and no new content came out ever again.

And that caused players to quit until the game was shut down for lack of profit.

How long would CoH be around if they decided to drop everything else they are working on and work on bug fixes until every last bug is gone? That means a potentially infinite cycle of bug fixes, because fixing one bug frequently creates a new one somewhere else.

At some point you have to say "Screw it, we'll fix that one later. The game still works, so it's not the end of the world.", or you'll end up in the circle of bug fix hell.

......Because Statesman biting it isn't the real plot twist in the SSA arc.

And it doesn't mean he is the ONLY one who will die.

There's a bazillion and one things they can do with this storyline that makes Statesman's death completely irrelevant.

That's awesome. One of the better backstories I've seen of late.

At least it wouldn't have been as bad as needing Acrobatics on a Fiery Aura or Dark Armor before IOs existed. Combat Jumping is available at level 4 now, level 6 before that, and it's available as the first pick in the pool. Acrobatics required 2 power picks and wasn't available until level 20.

For a scrapper, stalker or brute Combat Jumping is available before you get your mez protection toggle.

I would not have seen Combat Jumping being required as being a big deal.

The point is simple.

Aside from Invuln with Smashing and Lethal, no set in the game can cap more than one resistance type at a time. And in order to cap Smashing and Lethal, the rest of Invuln's resistances top out around 30%.

Dark Armor has solid resistance all around, with the exception of Energy, it can cap Psi, and gets a very good amount of Negative resistance. If it could cap both Negative and Psi, it is very likely the rest of it's resistances would be lower than they are.

And the part YOU are glossing over is the fact (and it IS a fact, the devs have confirmed as much in the past) that quite frequently, the cause of the bug has no apparent relation to what the bug is affecting.

It is entirely possible, and in fact likely, that these bugs aren't being caught at the programmer's desk because they are being caused by something that programmer had nothing to do with. The programmer's code could be working perfectly, and another code could be working perfectly, but when those two pieces of code start interacting it could have an unexpected effect.

It could be something like: Your map will break if you have ever teamed with someone in a different phase than you. In that case, the map code could be working correctly, and the phasing code could be working correctly, but the 2 codes break things when combined. Unless one person is working on phasing technology and the UI simultaneously, it is unlikely that connection will be made immediately, because the code appears to be correct upon examination.

Your example of the missing driver's side mirror is a poor one. In that case it is painfully obvious what the problem is, and the solution is just as obvious.

In the case of bug fixes in this game, it's more like the car is missing exactly one bolt and you have to figure out which bolt is missing before you can replace it.

And the bolt might not be missing, it might just be broken and still in place. Which means you'd have to go through the entire car and test each bolt individually until you find the broken one.

I don't think the game's programmers are incompetent in the slightest. I just think they have a mountain of unpredictable code they have to deal with that can do weird things when new code is added to it.

While I won't say it is anyone's job, you DO get compensated for it.

You are allowed to play new content before it is technically released. They are in no way obligated to allow us to do that. In return for that privilege, it is understood that you will be telling the developers about any problems you encounter while doing so.

Playing unreleased content is not a right like some people want to claim. If you want to play unreleased content, hold up your end of the deal and report a bug when you find it. It takes, literally, less than a minute to file a bug report, but you don't want to be bothered because it's "not your job". Even though the devs are letting you play stuff that hasn't been released yet.

The dev team cannot possibly test the entire scope of things that several hundred individual players will play through. If they could, the AE exploits they squashed never would have made it to the live build in the first place. It's a simple fact that the more people you have testing something, the more problems with it you will uncover, because not everyone will do the exact same thing. The devs just don't have the kind of in-house manpower it would require to simulate hundreds of people playing, for that they have to actually get hundreds of people playing.

The devs could decide that they will do 100% of the beta testing in-house, and that they don't care that it will take 6 months instead of 2. By letting us in there, it drastically speeds up the process, and we get stuff faster than we otherwise would. And it also leads to regular players finding things that the devs might never stumble across. Do you really think it will be a dev finding a bug related to farming Battle Maiden for 6 hours? Not bloody likely. It will be a player finding that bug.

The devs will test the new stuff in-house, and that's probably about it. They rely on players testing the other 99% of the game to make sure no new bugs cropped up when they added the code for the new stuff.

Ironically, I remember some of the people in this thread saying they aren't obligated to report anything as being some of the same people complaining that they never got closed beta invites. Why would they give a beta invitation to someone who has freely admitted they have no intention of actually testing anything in that beta?

You said it yourself: It's not game breaking.

How long do you delay the release of an issue while you search for the cause of something that isn't game breaking? A month? 3 months? A year? As long as necessary, even if it means the issue is never released?

As a programmer, can you say with any certainty that the borked code that's causing that bug is even IN the file the map is in? How do you know they haven't already looked everywhere and haven't figured out what's doing it yet?

Some things, like the map bug, just aren't major enough issues to warrant delaying an issue release while you straighten it out. Neither is the inspiration tray moving, or the majority of the other bugs you mentioned.

Now, if there were a bug that causes the deletion of a random character on someone's account when a specifc thing happened, THAT would warrant a delay. But not the Fog of War working incorrectly.