Luminara

The problem wasn't "illusion damage", it was your shit-tastic communication skills. You made what appeared to be a statement of fact, that Taunts deal illusory damage, then asked that it be "applied only to taunts" and not punchvoke. This implies that all Taunts already cause illusory damage, and your request is that it be removed from passive Taunts. Given that the rest of us know that Taunts don't deal any kind of damage currently, and "Pride." was a remarkably useless title pointer, everyone had to guess at what you were trying to say. And when queried, you... declined to clarify, to phrase it politely. I had to re-read it several times to figure it out, and I'm really fucking good with English. The burden of comprehension lies on the writer, not the reader. That's the most fundamental rule of communication. You are responsible for making yourself clear. It's not the reader's job to decipher an explosion of mental diarrhea to figure out what you're trying to say. If you disregard that basic rule, you leave yourself open to misinterpretation and misunderstanding. You were unclear, you acted like an ass when people asked what you were talking about, and now you're accusing everyone else of being slow because they couldn't instantly intuit what you meant from that stream of consciousness you vomited onto the screen (and refused to clarify when asked politely!). Sorry, but it's not our fault you sound like you're high, drunk or literacy-challenged, it's yours.

What I got from this thread is that someone selected this power with the expectation that the only thing it did was a 50% chance for a mag 1 Stun. I don't know whether to be mortified by what that says about understanding of basic game mechanics by players, or delighted that someone thought the power looked so cool that it had to be in his/her repertoire.

Your proposal was as comprehensible as that of a four year old's excited recitation of what happened in kindergarten class. Your follow-up responses were deliberately obfuscatory. Put away the victim card before you give yourself a paper cut.

Because building a conflict of interest into an open world event was poor design? I don't know, just a random shot in the dark.

I'm presuming that someone starting an account four years after the servers opened isn't asking about badges awarded on a temporal model that would exclude him/her.

Badges have always been character-specific, not account-wide. HC hasn't changed that.

I don't use separate folders for my binds, I dump everything in E:\Games\Homecoming\settings\live , and I used the H key instead of Z. Other than removing the obstructive quotation marks, those were the only changes I made, and they work perfectly for me. Either your path is wrong, or you're saving the text files with the wrong names or file type. Those are the only things I can think of that would cause the text files to fail to load. joke1.txtjoke2.txtjoke3.txtjoke4.txtjoke5.txt As you can see from the attached files, I didn't even bother to change bindloadfile to bindloadfilesilent when I was isolating the problem with making them load properly. And I can log in on any character and type /bindloadfile joke1.txt and everything works.

Licked the problem.

Too many quotation marks. Remove the quotation marks here-------------------------------------------------------^ and here-----^ Z "say Wait. The Paladin who believes in the 'Sky Cow' doesn't believe in ghosts?!$$bindloadfile C:\CoHRotatingBinds\d&djokes\joke2.txt" bindloadfilesilent would be more fluid, too. Z "say Wait. The Paladin who believes in the 'Sky Cow' doesn't believe in ghosts?!$$bindloadfilesilent C:\CoHRotatingBinds\d&djokes\joke2.txt" Z "say What is a good D&D joke? THAC0!$$bindloadfilesilent C:\CoHRotatingBinds\d&djokes\joke3.txt" Z "say Why do the elves have pointy ears? There’s got to be some point to elves.$$bindloadfilesilent C:\CoHRotatingBinds\d&djokes\joke4.txt" Z "say What forest animal helps the druid get that nice green color for their robe? A dyer wolf.$$bindloadfilesilent C:\CoHRotatingBinds\d&djokes\joke5.txt" Z "say What material is the magic skillet made of. It’s made of cast iron.$$bindloadfilesilent C:\CoHRotatingBinds\d&djokes\joke1.txt"

*saunters into @GM Crumpet's account, picks up one Hero merit, licks it, throws it back in the pile, mixes the pile, saunters back out*

Did he Picard it?

/suppressclosefx 1 shuts off toggle graphics on your character, so it's clearly possible to create graphics with limited display parameters.

Neigh.

Calling people "toxic" because you aren't getting your way reflects on you, not everyone else. Grow the fuck up.

No, you're refuting that there would have to be work put in to record, parse and display the missing information so it would be a tool relevant to and useful to everyone, rather than just the people exclusively focused on damage and healing, and dismissing those other stats as irrelevant because you refuse to admit that what you want doesn't encompass the wants of all players, much less that creating a tool with relevance for some players and denying everyone else the same thing would be inferred as developer favoritism, create divisiveness, and be detrimental to the community as a whole. All or nothing.

You mean insight and fun stats for some players, and fuck everyone else who might want to know how his/her Holds contributed, or how many enemy misses were due to a ToHit debuff, or how he/she might improve a build by tracking buff/debuff/status effect/anything other than damage and healing. You insist that this is just for funsies, and in the same breath, declaring that players who aren't interested in your two or three stats don't matter, but you don't seem to comprehend that this is exactly the attitude no-one fucking wants in this community. This isn't anything but an idea at the moment and you're already being exclusionary, selfish, and narrow-minded. You're a breath away from a form of discrimination at this point, what with the way you blatantly disregard even the possibility that other people should be given the same access to stats relevant to them... and you're either so obtuse that you don't see it, or so malicious that you're trying to foster this kind of attitude game-wide. Not happening, pumpkin. Try one of the other server groups, the HC team isn't stupid.

Okay. But it has to cover everything, not just damage and healing. Everything. Total time enemies spent debuffed, for each debuff. Total endurance drained. Number of attacks delayed, and by how long, by -Recharge. Enemies' time spent mezzed (and it would have to exclude time spent with an ineffective mez applied, to discount things like Warwolves shrugging off Immoblizes, and AVs ignoring status effects), for each status effect. Percentage of teammate damage output attributable to buffs from other teammates. Percentage of teammate damage mitigation attributable to buffs from other teammates. Damage dealt by Confused enemies, and percentages of variables attributable to buffs from Confused enemies. Every fucking thing has to be accounted for. If it's not applicable to everyone, presenting information useful and valid for every archetype's distinct abilities, I guarantee that it won't be done at all, because the HC team is an inclusive group and absolutely will not add anything to the game which would outright exclude players.

Given that participation isn't mandatory, only presence (and only in the final mission), you're grossly over-inflating your estimation of this hypothetical badge's value.

DELETE "priorityboost 1" INSERT "camdist 17" PAGEDOWN "++netgraph" PAGEUP "++showfps" These are the first four keys I press after logging in. [ "suppressclosefx 0" ] "suppressclosefx 1" I have suppressfxdist set to 15. If I'm playing a character with graphical effects that annoy me, like World of Confusion, [. When I'm playing a different character, ]. MouseChord "nop" Z "nop" I don't need click to move crap, and by default, pressing Z drops target, so both of these are unbound to prevent violence and obscenities. Location AoEs are /bind mouse4 or mouse5 powexeclocation target Power or /bind mouse4/5 powexeclocation self Power , depending on where whimsy carries me. If I'm really short on easily reached keys/buttons, I'll set up a rotating bind so I can assign more than one power to a key. Blizzard and Ice Storm, for example, would use one file, bliz.txt, with button5 "powexeclocation self Blizzard$$bindloadfilesilent e:\Games\Homecoming\settings\live\ice.txt" and one, ice.txt, with button5 "powexeclocation self Ice Storm$$bindloadfilesilent e:\Games\Homecoming\settings\live\bliz.txt" . Movement powers, including Sprint, are bound to V (toggle on) and B (toggle off). All other toggles are bound to V, and when the character limit imposes a restriction, B as well. Movement powers are listed first in the binds so they'll be the last to activate. Status protection is listed last so it activates first. I don't waste time, or tray space, on macros. I can do everything just as well with a bind, and often save tray space in the process, so I can keep the clutter down. Simplified power recognition in a bind string. Instead of having to use /bind v "powexectoggleon Rise to the Challenge", for example, just /bind v "powexectoggleon Rise" or /bind v "powexectoggleon Chall". Or powexectray ##being usable in multiples (/bind v "powexectray 1 4$$powexectray 2 4$$powexectray 3 4" (as of now, powexectray ## only works on the first power in the string, everything else is ignored).

As far as I've ever been able to determine, all debuffs, all controls, hit rolls, damage, everything applied to an enemy is purple patched. If it's used on something above your level, it's diminished in some way. Below your level, it's enhanced. Even effects flagged to override resistance are subject to purple patch math. Speculatively, the sentence was phrased as such just in case someone found an effect that wasn't affected by the purple patch. Buffs, on the other hand, are not affected by the purple patch. Or, they're not supposed to be, and when one is found that is, it's adjusted accordingly. When one does crop up, it's almost always a secondary effect of an attack/debuff/control and is unintentionally boosted or diminished when the attack/debuff/control is used on an enemy below or above +0. Those have to be specifically flagged to ignore level differences.

Purple patch isn't resistance to debuffs, or a function of debuffs, or a function of Resistance, it's not a power or anything in a power, it's a flat reduction when facing +X foes. It's an adjustment to the number before other calculations, or other parts of a calculation, are performed. Versus a +4 foe, a 20% Resistance debuff nets 9.6% -Res (20 * 0.48 = 9.6). That's the number that exists, 9.6, before any Resistance calculations are performed. If the +4 critter has 50% Smashing Resistance, the game checks that against the 9.6% -Res, not 20%, and arrives at a total of 50 - (9.6 * 0.50 = 4.8) = 45.2% final Smashing Resistance. Even if you pile on a ton of -Special to reduce the critter's resistance to debuffs, 9.6% is the ceiling because the purple patch isn't a resistance, it's a change to the underlying mathematics used to calculate everything else.