Luminara

Archaeology, specifically ancient Egyptian archaeology, is one of my life-long interests, so this happens to be a topic I've already researched. Clothing was made of linen, so natural near-white colors in the beige through yellow range would be appropriate. The higher you go on the social hierarchy, the more likely you will find color, but that color would be ochre, umber and blue, colors available to them, used strictly as ornamentation. Splashes here and there, not monotone. No blacks, no deep, dark colors. Light colors were more comfortable in their environment (hot and humid). The basic style of dress in the First through Eighteenth Dynasties tended to be a simple wrap around the waist, the shenti or shendyt, for men and women. The Talons skirt is actually an excellent match for that. Some, those of lower station, didn't wear any more than that, and slaves were typically naked. Not sure if there's an equivalent skirt for males in the game, but it won't hurt to look. Nudity wasn't frowned upon in that society, so many womens' clothing styles left the breasts exposed, but they were also made to cover the breasts, so we can work with that. One type of women's dress, the kalasiris, was little more than a long tube of fabric, held up by a strap over one shoulder, sometimes two. Another was... basically like fishnet shirts, but they hung down to the calves or ankles. You'll want the shenti on the lower body, since we don't have fishnet skirts. The sleeved garments left the shoulders exposed (and sometimes the breasts). Some lighter, more sheer weaves were sometimes worn by women of higher station (Desire and Disco are good examples of this. Frost is a good substitute for fishnet, Mesh isn't because it covers the arms). When you reach the pharaoh, it becomes a bit easier. Most ancient Egyptians spurned animal skins and textiles (wool), but pharaohs would wear them, leopard skins for instance, as a sign of their prowess and station. They were also the most clothed. Clothing itself was an indicator of wealth and power, and none was more powerful than the pharaoh, so they dressed accordingly. Also, bear in mind that some pharaohs were women, but they dressed like men (Hatshepsut routinely appeared in court and public wearing all of the traditionally male accoutrements of her station, and was bare-chested, as they would have been, to give one example). The nemes, the striped headdress we have in the game, was common for all Egyptians. Those who didn't wear them either wore wigs or were bald. They routinely shaved their heads to control lice and remain more comfortable in the heat. Egyptians of higher station wore wigs, made with their own hair, hair from other people, and sometimes palm fibers as a substitute or supplement, in social situations. The wigs weren't elaborate, generally straight, shoulder-length, with bangs. The pharaoh would've worn various crowns, culminating with the famous double crown (which displayed their rulership over Upper and Lower Egypt), but we don't have that. Don't sweat it, just use hair, the nemes or go bald. Bald was the default setting for that culture, and we happen to have that in-game. Jewelry was very common. Gold was easily obtainable, silver was rare. Rings, bracelets, armlets and necklaces of all types are on the menu, go haywire, but make most of it gold. For jewels, lapis lazuli, turquoise and amethyst were frequently used, but really, any shiny or pretty rock was satisfactory. Some jewels weren't even jewels, they were glazing (the same thing that makes pottery and ceramics shiny and colorful), so you can go any way you want for that. They even made jewelry out of flint, and had gold finger and toe covers, like finger cots (those little condom-like things you put on your fingers when you're not using gloves, but need to keep a surface clean or protect your fingers), so there's not much you can't do with it in the game. Pile it on, they loved the stuff. Make-up was heavily used by both genders. Blacks and greens for the eyes, red for the lips. Footwear was seldom worn. They spent most of their time barefoot. When they did wear something, it was a simple sandal. I think the Roman Sandals work well as a substitute, even if they aren't historically accurate for that period and culture. At least you'll have toes. Once you leave the Eighteenth Dynasty, you're looking more at Roman and Greek styles, intermingled with traditional Egyptian. The toga can be used without concern for historical accuracy from that point on. I'd lean heavily on the Talons skirt for both genders, and go from there. If your characters are exclusively male, they can all be bare-chested with varying amounts of jewelry to indicate their stations, with an animal print cape/cloak/bolero for the pharaoh. If female, go with as close to topless as you can for the lower stations, something light and diaphanous for the middle station, then back to topless for the pharaoh, but throw a dead animal's skin on her. Fishnet top with Talons skirt would also work for females. Just keep it simple, don't go crazy with color and remember the climate they lived in, and you should be able to cobble together plenty of fitting costumes. 👍

I'd specifically preclude damage toggles and toggles which don't directly contribute to damage mitigation. Sonic's Disruption Field, would not suppress because it doesn't directly contribute to damage mitigation (more rapid defeat of foes is arguably a valid interpretation of damage mitigation, but it is not direct damage mitigation in the way -Recharge, -ToHit or -Damage is). The goal isn't to improve "kill speed", but to instill an objective balance between functionally comparable powers used for damage mitigation (+Def and -ToHit, +Res and -Damage, etc), so a more thorough and stable game balance can be achieved. I'm on the fence with mez toggles. They should offer significant damage mitigation in and of themselves... but they're easily detoggled by anything outside of their AoEs, or anything not mezzed in the AoE, which compromises their utility and value. I think suppressible mez toggles would inch over to the power creep side, but if we added an additional factor, such as increasing the suppressed duration beyond the mez duration, it might be possible to avoid the creep. Superficially, yes. Functionally, eeeeeeeeehhhhhhhhhhhh. Example: Weave nominally has a value of 1 for the number of targets it affects - the user. Functionally, though, it affects everything the user interacts with, and that number of targets is theoretically infinite. It doesn't matter if there is a single enemy, or 17 enemies, or 100 spawns all attacking, they're all affected by the damage mitigation provided by that toggle. Until that toggle is suppressed or turned off, it affects everything attacking the user. That's the basic nature of self-affecting buffs in the game. They have two target vectors, self, and everything else. The stated number of targets is 1. The number of other targets affected is ∞. These powers are, essentially, just graphical representations of equations performed on the fly, and there are no bounded exceptions or special variables in those equations which alter the math for actions beyond target caps. There's no sub-equation or engine component which does that, either, of which I'm aware. Nothing in the game tells Weave, "Your user somehow managed to get 19 enemies to make simultaneous attack rolls (did he/she forget to bathe this month?), and that's three over the AoE cap, so your Defense buff won't be counted for the following list of enemies: Hellion Bob, Skulls Clara and Snorflemog the Unclothed". Instead, the game says, "Hit rolls? Yeah yeah yeah yeah yeah, whatever, just apply the Defense to everything and stop bothering me. I'm trying to finish my script for Blade 19. The Daywalker (Daaaaaywaaaaaaaaalker. Daaaaaaaaaaaayyyyyyyyyywaaaaaaaaaaaaaaaaaalkeeeeeeeeeeeeeeeeeer!) is beamed up by the Millennium Falcon and has to help Walter Bishop fight vampires on Arrakis. It's an art film, you wouldn't understand it.". Click buffs of this type are functionally identical, from that perspective. This X affected | ∞ affected functionality isn't a phenomenon exclusive to toggle buffs. When someone pops Grant Invisibility on your character, that character's Defense is increased for an infinite number of foes, like Weave or Combat Jumping does. If a */Sonic corruptor drops Sonic Barrier on you, you have that extra Resistance against an infinite number of attacking enemies, exactly the same way a Fire scrapper's Fire Shield provides for him/her. Your damage buffs aren't limited to increasing the damage of your attacks only for foes at or below the target cap, they increase the damage of your attacks regardless, and the game relies on other mechanics to limit you, such as animation times, target caps for attacks and range. Even toggles and clicks which seem to be entirely self-contained and appear to have no interaction with enemies, such as heals and regeneration buffs, have that second vector. You don't regenerate only the damage taken from the foes near you, or foes up to the target cap, you regenerate all incoming damage, independent of source or type. When you click a heal, the engine doesn't look at the list of foes who attacked you and prevent you from healing damage from any attacks which came from a number greater than X, it just restores a specific amount of HP. And some self-affecting toggles/clicks have effects which restrict them to target caps below infinity, but that's actually a third vector. Those are the powers which use a scaling variable based on the number of foes nearby or hit. The effect which most of them provide, such as +Res and +Def, or increased regeneration, is still completely applicable in the second vector, in that even if the toggle/click is saturated, additional foes are still affected by the attribute which was increased by the scaling variable. That +Res or +Def isn't dismissed on foes beyond the target cap. That extra regeneration doesn't halt if you're attacked by one more foe than the aggro cap (or ten more, or ten thousand more). Those effects continue to apply, regardless of the number of enemies attacking. We all remember dumpster diving. That only worked because these buffs affected all of those enemies, in this unlimited way. Not the first 10 enemies, or a maximum of 16 enemies, but all of them. Hundreds of enemies, all piled into a dumpster, swinging and missing at the character with capped Defense, or plinking with single-digit damage on the character with capped Resistance, et cetera. Everything ever herded into a dumpster was affected by those self-affecting buffs which, superficially, only affected the character on which they were cast or toggled. So even though these powers "only" affect the user or recipient, they also affect an infinite number of foes. And that can be leveraged. In fact, we have an archetype based specifically on that leverage, the tanker. The tanker provides damage mitigation for teammates by engaging enemies and utilizing that unlimited mitigation through exactly this dual-vectored approach. Target and threat caps provide constraints (now) by denying that tanker the ability to engage and hold the attention of an infinite number of foes, but they don't constrain that dual-vector functionality of the toggles themselves. There's no code written for the game to do that (again, of which i'm aware). So those self-affecting toggles actually provide a measure, and measurable amount, of damage mitigation to entire teams, in a lateral way. That's the foundation for the tanker archetype. In the absence of the aggro cap, the tanker proved that self-affecting buffs were functionally unlimited in how they aided survivability. Regardless of how many enemies were attacking, the buffs worked at full strength against every enemy. And because it was easier to simply limit the number of aggroed targets than it was to rewrite how buffs worked in relation to attacking enemies, we now have an aggro cap. So yes, buffs only protect the user or the recipient, but when viewed in light of their overarching functionality, they also protect the entire team by permitting the buffed character damage mitigation beyond the caps imposed on debuffs, via that unlimited protection provided by buffs not having a cap on the secondary vector. As long as the buffed character can hold aggro, and stay upright, the team benefits from that character's buffs, and they do so even when faced with a theoretically infinite number of foes. We can also look at this from the other side. If we summarize this as, "buffs offer a limited number of teammates mitigation from an unlimited number of damage sources", we can make the corollary statement that "debuffs offer an unlimited number of teammates mitigation from a limited number of damage sources". If the game didn't have limits, or had significantly different limits, then each would have broader usage, as well as more specific usage (debuffers for Hami raids, buffers for small teams defending against overwhelming odds, et cetera). Cryptic made a distinct effort, when they implemented target and aggro caps, to ensure that debuffs were as close to parity with buffs as possible in that context, but in practice, the limits tend to favor buffs over debuffs... or, more aptly, tend to allow buffs to reach a greater degree of their unlimited potential while confining debuffs to a small fraction of theirs. The content to leverage the full extent of debuffs' mitigation potential doesn't exist, and, in truth, can't (we all know how the engine chokes when large numbers of player characters are in a small area together), so this particular oddity of the engine is something that will always be present. We do, though, have much greater numbers of enemies (two for every one player character, in a full standard team), so the existing content, and likely all future content, allows buffs to leverage their flexibility more fully. Note that I'm not suggesting that click and toggle debuffs should have their target caps removed. Nor is any of this to be construed as negative commentary on caps, a call for new or different caps, or a complaint that buffs should be redesigned with caps on their secondary vectors. I'm simply pointing out that a self-affecting buff (click or toggle) is inherently more effective than is immediately apparent by looking at the stated target number. The existing target and aggro caps are generally effective at limiting the secondary vector of buffs and providing a reasonable degree of parity with debuff target limitations (bending the aggro cap rules is possible, but extremely work-intensive and prone to failure with the least mistake or fraction of a second mistiming. not many people bother to juggle enough enemies to surpass the aggro cap, because it's slower than just kicking ass and moving on, and in the current game, many players are experienced enough and have sufficiently powerful builds to manage stray aggro when others are at their respective cap). There are functional target number differences between buffs and debuffs which go beyond the expressed number of targets, but they're relatively well hidden by things like spawn sizes, team sizes and caps. And I like to talk about this kind of thing, so everyone has to suffer through my long-winded, pretentious yammering. Sucks to be you guys! 😄

Mechanical parity between otherwise functionally identical powers doesn't equate to "play the same". You don't seem to understand that, which is why your proposal to hard-cap Defense at 40% hasn't gained any traction, as it's not parity of any kind, it's a hypothesis conceived of in a vacuum and so narrow in scope that it ignores the basic functionalities of Defense and Resistance, and every variable that affects them. You were counseled on ways to refine your idea, you told everyone to piss off. You were given opportunities to revise your suggestion, you continued to post it without revision. And when people, including myself, finally turned to sarcasm to show you how little traction you were gaining, you became angry and went on a tirade of revenge down-votes and vitriol. You don't care whether your idea would work, you don't care if you've approached it from the correct perspective, you don't want to consider the possibility that there were oversights and mistakes, you just need to be "right". To "win". Even if it means damaging your own reputation and standing within the community. But that's fine, too. If that's what makes you happy, go for it. I don't even have to see it with you in my /ignore list. Down-vote everything I've ever posted and cut loose with the most vile shit you can compose if it makes you feel good. And I mean that. Having spent so many years of my life feeling miserable, it's not something I wish on anyone, certainly not people with whom I've had mild disagreements over ultimately meaningless crap in an Internet forum.

"Lazy" was intended to convey a lack of slotting, not a lack of effort. Blaster T1s deal nearly twice the damage of defender T1s, as an example, and Defiance buffs them further. They don't have to put in the same effort (expending slots, using enhancements, creating and refining the build). And I'm not bitter, I'm irritated. There are deep-seated problems with how support archetypes are supposedly balanced, which have never made sense, but which have also been rigorously enforced. Bitter implies that I've given up. I'm not a quitter. Real balance. If I play a Trick Arrow character, I can use Flash Arrow and Poison Gas Arrow to debuff entire spawns, and I gain the benefit of that action. Someone playing a Force Field or Sonic Resonance character, on the other hand, has ally-only click buffs, which do not benefit that character. There is no "If target = Trick Arrow debuffer, ignore debuff" flag. There is no hole in debuffing. There is an "Ally Only" flag. There is a hole in buffing. That hole was deliberately left in place throughout the entirety of the game's original life, and is still there today. That's not balanced. If it's perfectly acceptable for a support character to mitigate incoming damage one way, there's no logical or rational reason they shouldn't be permitted to do so the other way. Damage mitigation toggles on non-support characters suppress, and have a functionally unlimited number of targets because they're self-affecting. Toggles on support characters do not suppress, they shut off. And they have maximum target caps. That's not balanced. That the characters with the highest HP pools and status protection can be permitted to use suppressible damage mitigation toggles with no target cap, but support characters, who have half to a third the HP pool, are required to turn toggles back on, thus forcing them to wait out the recharge time and the animation time, and have target caps which guarantee failure beyond a certain amount of aggro, is not logical or rational. Zero status protection for most support characters. Target caps on toggles which drop frequently, have long recharge and animation times. Low HP pools. Disparity between buffing and debuffing support characters. These are absolutely not balanced within the archetypes in question, nor in comparison to the non-support archetypes. Balance points are not measured by how much shit a player will endure before giving up, they're measured by how well things perform in comparison to similar things, and we have obvious discrepancies in performance between comparable things here, which, to date, have been ignored. I don't care if the solution is doing a pass on everything in the game to reduce the overabundance of mez; or restoring toggle mutual exclusivity in concert with non-stacking buffs; or adding a "Lumi's playing, ignore those debuffs" flag; or removing the ally-only flag from buffs in concert with permitting damage mitigation toggles (-ToHit, -Damage, -Recharge/Speed/Fly) to suppress; or just giving support characters better access to status protection so they're not scrambling every time a minion with a mag 2 mez glances at them. I care that it's done, and that's all. I want real balance. I want parity between click buffs and debuffs. I want parity between toggles. I want different support sets to they work on an equal basis so they actually can be balanced. Many of us spend hours arguing about balance, turn small threads into monstrous arguments, and we aren't even talking about a game that's truly balanced, we're ignoring gross imbalances like these and hissing and spitting at each other over damage output and soft capped Defense and telling ourselves that we're protecting an existing balance... that does not, in truth, exist. And that's why I'm irritated. I've said all of this several times in the last 18 months. I said it to Castle several times on the original forums. We have some of the brightest gamers alive playing here, now, but when I point out problems like these, everyone shrugs. "Eh, whatcha gonna do?" We should be screaming in the HC team's ears, but we're bitching at each other about power creep and damage procs, and it gives me the impression that we don't care about balance, we care about keeping the game from changing. Well, imbalances lead to poor design decisions, such as over-buffing and nerfing. Over-buffing and nerfing lead to imbalances. We ran around in this endless circle for years on the original servers, and as soon as we come here, we jump right into the circle and start sprinting again. Yes, fixing real balance problems would mean some sets, like Rad, which has hybrid mitigation/combat efficiency toggles, might overperform. That can be addressed. But it couldn't be addressed as long as some support sets are sadly lacking due to arbitrary, nonsensical rules, while other sets are comparatively overpowered due to not sharing the same rules. I would happily give up all of the TA recent improvements to see one FF or Sonic player self-buffing with his/her ally-only bubbles, or one Dark Miasma player with suppressible Darkest Night, because that would be equable parity between support sets. That would be balanced.

I have the game installed on an external SSD. Had a problem with the OS spazzing out and telling me that the SSD was full a few weeks ago, and my entire character list had defaulted to order of creation. That's the only issue I've had that's even close to what you're experiencing, @Crysis. I have occasionally accidentally dragged a character to a different slot, but I was paying attention and moved it back immediately each time. Open your playerslot.txt and run a quick search for the character's name. If it hasn't been deleted, the slot number will be next to the name and you can find it that way. Might also log onto each of the other servers, just to see if you moved it without conscious recognition of what you were doing.

I wish I could turn back time, sit you down and make you play a TA before Issue 7. Not because I dislike you (i don't), but so you could understand how bad defender life can be. But the time machine is on the fritz again, so I'll try to do it with words. Here's how I look at it. Power is the money. Desirable content is the goods. Power creep is the inflation. Right now, we have comparatively high inflation, generally speaking. The amount of money circulating has compromised the price of goods in various ways (made some content too easy, made some content less "optimal", made some content uninteresting). But that inflation isn't applied equally. Most archetypes have reasonably good purchasing power, despite the inflationary nature of the economy, and leverage of that purchasing power (wider variety of content which can be easily completed, wider range of difficulty settings to make the game feel "challenging"). Support characters, on the other hand, have low purchasing power. Their low damage output, (general) lack of status protection, imposed time penalties due to (general) reliance on clicks and debuff toggles instead of self-affecting toggles, and (general) problem with toggle dropping adds up to lower purchasing power and lower ability to leverage the purchasing power they do have. Is the solution to this inflationary issue, then, to lock support's purchasing power at the lowest level and prevent them from accessing the same goods as other archetypes? We've recently had newer, harder difficulty settings added, which increases the value of some goods, but it imposes a still higher purchase cost, which support archetypes may not be capable of paying. Does it make economic sense to continue to impose purchasing restrictions on support archetypes, when more expensive goods are on the way? I don't think it does. If we were talking about a real economy, we'd see those with the lowest purchasing power emigrating to places where they weren't as heavily restricted, where they had higher purchasing power and better quality of life. Or staging riots, revolts, regime over-throws, walk-outs, marches and other tactics to improve their situation, which, historically, have also been accompanied by a significant amount of bloodshed, but since this is a video game, we can assume no-one will be decapitated or shot. That's why. The end result of shackling support archetypes under a "no more power creep" clause will be the gradual loss of support as players stop playing them, opting instead to play archetypes which aren't restricted as heavily and, from the players' perspective, oppressively, or just leaving to play less restrictive games. The inflation problem is being addressed for the majority, the archetypes which are already rolling in their surplus of money, through the addition of increased difficulty and new content. Imposing further restrictions on support archetypes, locking or reducing their purchasing power, won't encourage players to support you with support archetypes, it will encourage them to say, "Fuck it, I'm done." Or chop someone's head off. If you want to fix power creep, bring the support archetypes to the same degree of creep as the rest of the archetypes, then address it by making content that everyone can enjoy, or improving existing content so it's more enjoyable despite the creep. Or nerf the entire roster of non-support archetypes into the dirt to accomplish the same goal from the other direction (probably not a wise choice, given the reactions to such in the past). Holding support archetypes down won't fix anything, unless the goal is to remove interest in playing them entirely.

But that was always the case. Before PPM, when procs were fixed at specific rates, they were still better in AoEs than in single-target powers. It's the simplest of maths in this case, more targets will always equate to more chances for procs to trigger, and greater likelihood of more proc triggers per power use. The PPM mechanic didn't change anything in that regard, and even if the PPM mechanic were drastically altered to reduce AoE probability even further, AoEs would still benefit the most from procs, due to that greater number of trigger rolls. The HC team could peg AoEs at a ridiculously low proc rate and they'd still be best-in-use, because they hit 10-16 foes. Yes, a typical defender cone/AoE attack, optimally slotted for damage, deals ≤ the damage of a single typical proc. Does that says more about the design of defenders, or about the design of procs or the PPM mechanic? I have my opinion, and I've made it known (loudly and vehemently).

That's a valid and constructive point. The PPM mechanic encourages a different slotting schema, one which is not intuitive, and is contrary to the design intent behind the game, slotting in general and IO sets. Deliberately avoiding Recharge Reduction, breaking sets and losing set bonuses, relying entirely on set bonuses and additional proc slotting to compensate for poor slotting, none of these behaviors were intended. Do they work? To a degree, because the Invention system is robust and flexible enough to absorb the slotting differential and compensate, and the overall design of the game, with buffs from third-party sources, bolsters the design. But they aren't necessary optimal, and, again, that counter-design approach that the PPM system encourages is... messy. And when they do work, they're not profoundly better than ignoring PPM entirely and using the traditional approach to slotting. The PPM mechanic allows proc-heavy builds to work, and it urges some players to explore its limitations and try to find loopholes (perfectly normal behavior), but it doesn't allow them to work so well that we're fools if we don't use them. And that's a key factor. Proc-heavy builds aren't running rampant over traditional builds, which relegates them to "just a different way to do the same thing". As long as that remains true, I see no justification for anxiety.

Worth noting that the commentary there is specifically about PPM, its counter-intuitive functionality in intuitive slotting, and performance differences between AoE and single-target. Not a whiff of "nerf procs", not a single alphanumeric character about cutting damage from procs, just an intent to clean up the PPM mechanic so it's neither encouraging players to slot in a manner which fails to appropriately improve powers, nor penalizing players for playing single-target/overly rewarding players for playing AoE-heavy sets.

Enough speculation. Enough of the "procs are gonna be nerfed" doom-crying. Enough of the "we all know" nonsense. Prove that there's a problem before you say one more word. Define the nature of that problem, set yourself test parameters, document results and lay down incontrovertible evidence that this problem exists, what the problem is and how the proof can be reproduced. We've been rehashing this thread for years now (years. multiple), and not one person has conclusively proven that procs are a problem, or the problem, or that a nerf actually is coming, or that a nerf is necessary, or that there even is a problem. In fact, no-one has even given a solid example of what could be construed as a problem. On the contrary, all existing evidence has indicated that there is no problem. The HC team has never made an unwarranted change to proc behavior, despite those years of proc panicking and fear-mongering, and we're still on this same ridiculous merry-go-round? What the fuck? An unusually open and cooperative development staff has been the hallmark of this game, from its first days on the original servers to the HC team we're blessed with now, people who granted us insight to the game's systems and mechanics in a way unprecedented in MMORPG history... and this is what we do with that legacy, wring our hands and bemoan an imagined future of proc nerfs that we don't even know will happen, much less given any reason to expect, like we're a bunch of WoW players. You want the proc system changed? Prove that it needs to be changed. You believe there's a problem which needs to be fixed? Define what the problem is, prove that it exists and show exactly how it's detrimental to the game. You want ridicule and scorn? Keep doing what you're doing, I'm right here.

That was the original implementation of the PPM mechanic. It was changed because we aren't always in control of our global +Recharge. Example: You and I team up, you have a specifically crafted proc build which works exactly the way you want it to... and I buff you with Accelerate Metabolism, throwing your build and proc chances into disarray. You are, understandably, displeased with that result, and write a strongly worded missive to the development team (Paragon, at that time) saying so. Perhaps even posting about what I total dick I was, buffing you with AM when you didn't want to be buffed. That's why the PPM mechanic was redesigned to ignore global +Recharge. Penalizing players for being buffed is bad design, not just for making players happy, but for promoting teaming.

Individual problems should be addressed individually, not with mass quality of life reductions. If there are problems with some powers being slotting in certain ways, we address those powers and slotting possibilities, because a global attack on the problem doesn't actually change the situation. Those individual powers will still be outliers when the dust settles. Nothing's fixed, and no-one's satisfied when it goes down that way. I addressed that scenario thoroughly in the last two proc nerf-herd threads, showing mathematically that the final result was not, in fact, grossly more powerful. Will that high damage attack hit harder when it's used? Most likely, yes. But it's also usable less frequently and has a higher cost associated per use, and in the end, we're looking at a miniscule improvement, a few damage per second. The end result is negligible in terms of DPS, expensive in terms of endurance, requires jumping through multiple slotting hoops, imposes a longer recharge time on the power, and in the end it's still only "winning" the imaginary dick measuring contest by a millimeter or two (and then only if the player doesn't hesitate to use that ultramegaboomy attack every time it's up, rather than hold it in reserve for the bosses). In essence, it's just playing the game a slightly different way. As many times as I've seen you step in to have your say when others are demanding that we all play their way, or that the game be redesigned or rebalanced to force us to play a certain way, I know that's not your preference or position. And given your adamant opposition to ED and GDN back in the day, it's hypocritical of you to advocate global nerfs to address outlier situations now. You're better than that. I know you're passionate about balance, but this isn't the way to achieve it.

I completely and wholeheartedly agree. Damage-dealer archetypes are still dealing more damage, and procs don't benefit from inherents, such as Containment, Scourge or Vigilance, nor are they guaranteed to trigger, despite the misinformation happily thrown around by people who either: require real-life validation from pretendy-fun accomplishments in a video game ("my procs are absolutely reliable and always trigger, i'm awesome!"); or who are determined to see damage procs nerfed ("your procs are absolutely reliable and always trigger, you're awful!"). They are improved by -Res, but applying -Res requires additional time and the characters leveraging procs in that manner aren't winning any races, they're simply not running as far behind as they would be without procs. A defender can sometimes deal almost as much damage as a lazy blaster, after a lengthy set-up and dependent on randomized occurrence, and some people believe we just have to nerf damage procs into the ground to stop that, so those lazy blasters don't lie awake at night, agonizing over imaginary dick measurements. Because, of course, it makes perfect sense to impose massive restrictions on everyone just to prevent a few peoples' fragile egos from being lightly bruised. The emotional equivalent of a paper cut is the end of the fucking world these days, after all. Some powers can be slotted as "proc bombs", and the proposed solution by those same people is to grind damage procs into dust, rather than address the powers themselves to make them perform less like outliers, because kicking entire archetypes in the balls is a better solution than bringing individual builds into line, and even that is predicated on the presumption that these people can reasonably prove that there is a problem... which, to date, no-one has done. The attempts to do so have been shown to be deliberate efforts to misrepresent the entirety of the situation, with facts swept under the rug, cherry-picked datum held up and loudly proclaimed as the end-all and be-all of evidence... the epitome of scientific misconduct, which would have those people permanently barred from publication if they tried to submit the same "research" in a respected scientific journal. It's all nonsense.

I expected a picture of Bill to be significantly more grizzled... and less anus-rockety. Guess those Texan chilis took their toll.

Huh. Never seen a flying turtle before. 😁

Not too shabby. You manage to hold on to enough global +Recharge to keep the impact minimal. One Force Feedback +Recharge, I'd guess, since my Shield/Elec tanker has 140% global +Recharge and the slotting differences between EM and Elec aren't sufficiently unique to account for that extra 100% otherwise. Could do with more Accuracy/ToHit in both cases. You move like a possum, though. I have one good lung and I can catch a possum. That Run Speed, that's like, what, six years to run from one spawn to the next, taking reverse time dilation into account?

I AIN'T SEEIN' NO GLOBAL RECHARGE, ACCURACY/TOHIT OR MOVEMENT SPEED COMPARISONS BETWEEN THOSE TWO BUILDS, BUBBLES! You're on the clock. Let's go. 😛

Global recharge, global Accuracy/ToHit, movement speeds and stats without Hybrid and Destiny? Also, that recovery rate in comparison to the endurance usage is abysmal. Turn off Sprint, you numpty.

*waves rolled-up magazine* Do I need to smack you on the boop-snoot again? I will. You know I will.

They're just washing him off. That's basic medical practice. Never expose your donor organs to unnecessary, avoidable infection vectors. That bucket is probably a "bath bomb", containing salts, iodine and other anti-bacterial and anti-fungal compounds. Good hygiene matters!

FUD-mongering? You? You? Wow, I guess it has been a slow start to the week.

Hopefully, zero.

It is necessary, and it's more helpful than you realize. Think it's tough to find a moved thread? Imaging what it would be like if every thread was in one category. No order, no topical division, just thread after thread you have to scroll past to find the one you wanted, and they're always moving, always bouncing threads up and down, off to the second page, then back to the first when you're looking on the second... Proper categorization and location of threads is what keeps forums like this in a readable format. It might be momentarily inconvenient from time to time, but it's less chaotic and confusing. And there are plenty of ways to find a moved thread. As @Greycat said, you can click the "Topic was moved to" link; if you've posted in that thread, you can go to your own profile (see that picture of yourself at the top right? click that) and click the link(s) to your post(s); if you recall the name(s) of the poster(s), you can check his/her/their profiles and click a link to the post there; there's a Search box at the top right of the page (every page).

Ditto. I left when they started talking about changing to the F2P model. I had no idealized objection to that, at that time, but in concert with the efforts to pigeonhole classes into the trinity, the lack of content at max level (was in a guild, was participating in PvP, and was still spending most of my time just standing around, waiting for something to do), and the game not meeting my expectations for a Bioware product (wanted Star Wars, not Space-WoW), it was enough to convince me that it was time to move on. Never returned, still don't regret leaving.

Essentially, yes. Everyone associated with space exploration realizes that it's a matter of taking it one step at a time. A former NASA administrator once stated that going to Mars meant going back to the Moon, and going back to the Moon meant privatizing low Earth orbit. But that's not what politicians and mass media can sell to the public, because it's not sexy, and it's not what the public wants to hear, because it's not sci-fi. That's what people want. The Enterprise. The Millennium Falcon. Battlestar Galactica. The Apollo LEMs weren't sexy, they weren't sci-fi, they weren't sleek. They were effective, but not "cool" (except to nerds (me! me!)). So there are always the problems of funding, waxing and waning public interest and convincing capitalist corporations to participate. The Challenger and Colombia losses exacerbated the problems, as did the cost overruns and overly long construction of the ISS. The Hubble telescope has done a lot to grab public attention, but it's also frustrated a lot of people. They see those glorious images and want to go there in person, right now, not eventually, not in a slow rocket, but in their personal space yachts or on space cruise liners. So yeah, it's a horizon problem. I believe the Artemis program and the Chinese Moon landing program will bring our attention back to what's in front of us, though. It won't be jaunting around in the Horsehead Nebula in a brainship, but it will be a nibble at what's to come, and the billions of us who were born just a little too late to watch the Apollo missions on television are starving for that. Sexy or not, being able to watch people land on the Moon, seeing people go back, witnessing the construction of the first Moon base... that will grab attention. I'm all tingly now, just thinking about it.