srmalloy

Sometimes the NPCs have their own script, and they don't pay attention to their victims. [NPC] Daria: Please, I want to leave! This roof is so high! [NPC] Life Mage: There is a crossbow pointed at your forehead. I would suggest that you do not move. This roof is quite high.

No; his "Come back later" is for level 35, and sends you to talk to Imperious, giving you a push into Cimerora. It's just "Talk to Imperious", and awards a single merit.

Well, it appears that Neiska's statement "I made both a tanker and a brute energy melee/bio, to compare the damages and whatnot. And in game, both with the same powers/incarnates/stances, the tanker does more damage. And (according to MIDS) at zero fury my Energy Transfer should do 600-ish, and at 80 fury it should be doing 1000-ish, but no matter what the fury is, it always does 600-ish. While my tankers does around 800 consistantly." is completely unclear on that matter.

Whether or not the numbers from Mids are correct, their observation that increasing Fury should be increasing the damage done by a Brute is still relevant, and that they're not seeing it indicates that there is some sort of disconnect there.

Mirror Spirit's private life should be their own; don't rag on them for lifestyle choices.

Well, no; he's tied into the Midnighter Club, so the missions with him are connected with him being a Midnighter, and the Midnight Club members are the ones who would be keeping an eye on him to send one of their people after him when he gets into trouble. You don't know Percy from Adam's off ox until Montague Castaneda asks you to rescue him as your first mission in the Midnighter entry arc, so while there's a really low probability that you might encounter him as a hostage in a completely unrelated mission into Oranbega, there's no reason for him to be a regularly recurring victim character in non-midnighter missions.

Mercedes Sheldon, IIRC, has her arcs and nothing else; you could add a small chance for her to, whenever you asked her for another mission, to offer a "Rescue Percy Winkley" mission.

I haven't tried it to check to see if they both count for the badge, only the one in AP counts, or whether they just set the same flag (so you could get the Echo:AP plaque for the Pupil badge), but the plaque under the statue of Atlas in AP and Echo:AP both have the same text.

Seed initialization is the downfall of a lot of RNG algorithms, true enough, and they can be much harder to fix -- the game servers are likely going to be brought up as quickly as possible after a server restart, so that's going to be resistant to fixes.

Cursor color should just be a parameter (or two, if the fields are defined independently) that can be easily changed; altering where the input cursor starts depending on the state of another setting involves altering the client logic, and asking for a minimal change is more likely to be approved than asking for something that needs a more complicated code change.

IIRC, that's the 'pointer' cursor (replacing the stock arrow pointer), not the narrow vertical bar that is the text input indicator in the login screen.

On the login screen, the white cursor against the off-white input field background is hard to see, making it easy, if you have 'save my login' checked, to start typing your password into the username field. In the interest of reducing the number of mistakes like this, could the cursor be changed to a dark color for the two input fields?

English is not a static language, the way the Délégation générale à la langue française et aux langues de France tries to establish French versions of words and terms to keep French 'pure', like "émission à la demande" for 'podcast' (the object), with different terms for the action of making a podcast, the action of receiving a podcast, and the action of presenting podcasts for download. Common usage drives what becomes acceptable English.

This isn't true for the single counterexample of snipe attacks -- snipes make a LoS check when you trigger the power, and again when the animation ends, and if you lose LoS on the target before the snipe goes off, it doesn't fire. Now, there are few enough mobs that have a snipe attack in the first place to make 'duck and cover' a worthwhile practice (the Nemesis tirailleurs, for example), but it could work in some cases.

What had me confused about it was that the first 34 times I used Glue Arrow on the oil slick, it ignited; I didn't think the proc would be causing it, because it shouldn't be that reliable. It was only after I'd made my first post that it finally failed to trigger.

The OED, however, reports that decimate also has come "rhetorically or loosely" to mean, "To destroy or remove a large proportion of; to subject to severe loss, slaughter, or mortality."

"Your name's not Hulk? That's going to cause some confusion; mind if we call you Hulk just to keep things straight?"

Just open a few of the gift packages to collect some charges of the Instant Snowstorm temp power, and you can have snow everywhere, even inside your base.

No; there's no winter event. Ignore the snow, the packages scattered around the zones, the animated snowmen, and all the rest; they're just figments of your imagination. 😉

It was part of the overreaction on the part of the devs, reworking Regen after their internal testing showed that a Claws/Regen Scrapper could solo +8 spawns without difficulty, despite the playerbase calling bullshit. It was only after the rework was in place that the devs admitted that they'd discovered that their internal test server didn't have the 'purple patch' incorporated, which meant that the scrapper they were testing with was hitting about 10x as often for 10x as much damage as it should have been... but the changes remained. One of them was turning Instant Healing from a toggle into a click power with a recharge time so high that it could not possibly be made perma, because of all the Regen characters that had been built around getting enough end reduction to be able to afford the punishing end cost of IH, which the devs had originally thought would keep characters from running it continuously.

That wasn't clear in the OP, and part of debugging a problem is to ensure that all possible extraneous influences are eliminated.

The reasoning behind locking CC titles to a new costume slot is to let the winner keep the costume to show off without eating a regular costume slot, or deleting or altering it inadvertently. Other titles, not associated with costumes, would need to be examined to see whether they apply to the character or the player -- titles associated with the player, like, IIRC, Bug Hunter, should be account-wide.

Particularly with a character who won one of these titles might be using a more drab costume, leading people to wonder how they managed to win the title with that costume. Or edited the costume significantly after the contest. Either making the title account-wide, since the award is essentially going to the player that created the costume, or, in what I expect would be a nasty piece of coding, award them an extra costume slot with the winning costume in it and locked so it can't be changed, and tie the title to having that costume active.

Just as a check to make sure something isn't overlooked, do the damage numbers you see in the combat pane and floating over your target reflect gross damage or net damage (i.e., after the target's resistance is subtracted?

I'm disappointed with the change to ESD Arrow, with it taking away an AoE hold and replacing it with a stun, given the game's horrible handling of stunned mobs -- back on Live, I've watched a stunned Outcast stagger off at a dead run, leap up onto the roof of a building, and disappear. Stun is not a reliable mez until the game aborts any movement for a stunned character and replaces it with the slow stagger PCs are limited to. But I moved a slot from ESD Arrow to Ice Arrow so that was five-slotted, and replaced the Lockdown in ESD Arrow with two Absolute Amazement and a pair of procs, and it seems to be reasonable. Oil Slick Arrow works like the Defender Trick Arrow version, so if you've gotten used to lighting your slicks, it's not a pain. Adding a macro to target the oil slick and fire Explosive Arrow at it makes lighting it easy, and in big fights someone usually has it lit before I can. Once they fix the bug that causes a targeted Oil Slick Arrow to fail to spawn a functioning oil slick (you can hear it, but it doesn't show up, and it doesn't affect mobs) it will be a steady part of my rotation.