srmalloy

If they're PC gamers, it can depend on what game(s) they're familiar with. ESO, for example, is very aggressively built for console players despite having been ported to the PC, with your character potentially having dozens of abilities, but being limited to six at a time with a "front bar/back bar" swap mechanism that is clearly based around the limited number of buttons on a console controller. Having direct access to thirty ability slots and indirect access to many more via binds, popmenus, and bar swaps may be initially confusing, although they'll acclimate quickly.

Why are you making denigrating comparisons about pigswill? I've abortively watched some YouTube videos that make pigswill look like Cordon Bleu -- for example, an audiobook narration of Larry Niven's Flatlander that, in the AI-created thumbnail image, stated "Flatlander is a visually stunning exploration of rural Dutch life"; another was a video that, from the title, was about the WWII Japanese amphibious light tank Type 2 Ka-Mi, but had AI illustrations of modern MBTs with the narration going on about the putative features of the K1A1 tank without once mentioning that it was a Korean tank. So far I've told YouTube to block six entire channels from recommendation because their videos are utter clickbait that seem to be determined to redefine "AI" as 'Artificial Ignorance'.

Just having the escortees ignore allied stealth won't prevent you from losing them; all you have to do is move fast enough to get out of their 'follow' radius. There are very few rescuable NPCs in missions that completely ignore range-to-escort.

With the additional four levels of incarnate boosts, the devs would have had to completely rebuild the way the missions worked, and likely would have had to introduce gatekeeping to each level, because the uprating of the mobs you'd be facing would likely "tear you a structurally superfluous new behind" (to quote the Engineer) if you didn't have the appropriate upgrades. I suspect that it would have been a balance nightmare that the devs could poke at for years without ever getting right, but being unwilling to admit was never going to be workable.

I was citing the wiki page on Electrical Affinity: And yes, 'Galavanic' is a typo on the wiki page.

You might as well complain about the people who keep posting location coordinates in chat without bothering to include a zone -- Jurassik may spawn only in Crey's Folly, but "Babbage [340.5 -145.2 2341.6] could be either Skyway City or Boomtown (or the end of a Kronos swarm in Talos), and seeing just "Kronos [3434.2 144.7 1124.7]" tells you nothing about where to go. People will always look for shortcuts to get what they want for the least effort possible -- the continued LFG messages asking for farms they can join is proof. You just have to take a little care with what you accept, and learn from your mistakes. If you dislike assisting someone else complete their goals at a disadvantage to yourself, stop doing it.

It isn't impossible to do escort missions if you have stealth or invisibility running; it just becomes immensely painful, as you're limited to moving about five feet at a time, then waiting for your escortee to follow you before you move again. I suspect at least part of the reason why sets were removed from allowed enhancement types in Sprint was to eliminate what would be an interminable series of "I can't get the hostage to follow me out" trouble tickets, where the GMs would have to investigate the character the ticket was about to see if they had a stealth IO in Sprint, instead of the smaller number of "I can't slot sets in this power that doesn't take any sets" trouble tickets.

He just got bad directions. MAGI's "will call' window is on the outside east wall of City Hall -- it's where the Banished Pantheon pick up the pieces of the Wheel of Destruction after you collect them, for example.

The Dev vision for Masterminds wasn't helped by the way that Masterminds were forced to resummon their henchmen after each door entrance, then had to individually buff each of them. This took up time that the rest of the team would often use to clean up the map while the Mastermind(s) were busy, dropping the Tank role into the hands of the Brutes by default. By the time that MM henchmen were able to survive mission doors, and the buffs were made AoE, Brutes chasing Fury had become the team pointmen.

I would have to go back and trawl through the archive of the Live forums, but I remember that it was the Mastermind archetype that was intended to be the closest analogue to Tankers in the CoV archetype list. Whether it's worked out that way in practice is definitely arguable.

Paste the following macro into your chat: /macroimage "WheelofFortuneFortune" "LvOro" "enterdoor 259 670 -764 P" This creates an icon that, when clicked near the front portal in Ouroboros, brings up the Ouroboros departure destination menu. It doesn't directly address the issue of people being jerks by parking TT vehicles, BP Ravagers, Longbow Cataphracts, or any other huge object on top of the portal, but it does let you activate it without having to fumble around the crush of bodies to get the little hand icon.

Voltaic Sentinel turns off and has to be restarted every time your character changes zone. Galvanic Sentinel, like Phantom Army, Dark Servant and Barrier Reef, has a duration, and will despawn automatically when its duration runs out. Its duration increases with the number of stacks of Static the character has when they summon the Galvanic Sentinel.

The Origin of Power missions used to send you to four of [War Witch (Magic), Positron (Technology), Synapse (Science), Manticore (Natural), and Penny Yin/Sister Psyche (Mutant)], chosen randomly and in random order (although War Witch was first more often than not), with your getting a more detailed conversation from whichever one matched your origin (if the RNG didn't leave them out). I'm not sure precisely when it happened, but it was on Live when Positron got dropped from the possible talkity-talk contacts for the arc, so it was just the other four in a random order.

Seems to have trickled off due to all of the people spamming LFG asking where the mapserver is; this morning, there was a SS/Shield Brute standing at the spawn point with Foot Stomp on auto; he was there from at least forty minutes before Adamastor could be summoned (when I logged in on a character I park on the platform for a quick timer check), and was still there stomping away when Adamastor was summoned and spanked forty minutes later. There was some discussion in local where the rest of us determined that no one had a Teleport Other power to be able to drop him over the edge of the platform to the next level down (assuming he didn't have confirm teleport on), though.

Or a T1 that you picked because it gave you a bonus you wanted more than the T1 of the line you really wanted, and then kept only until you got the other line up to where it gave you the bonus(es) you wanted, at which point you sacked the interim T1.

I've not experienced it myself, but on two occasions I've either logged in on the character I keep parked on the summoning plateau (when the first I find out about it is a two-minute warning) or arrive on a character from the Ouro portal, and seen someone in chat asking for people to move away from the summoning point because the last time the spawn came up there were too many mobs at the spawn point and Adamastor didn't spawn. The PBAoE autofire Brute/Tank has thankfully trickled off, but I remember a period of two weeks, during which I rotated about a dozen characters through Echo:DA (only for four or five summons each day, though) when the respawn timer ran down, and saw the same character in the same spot doing the same autofire PBAoE attack, sometimes (when I misjudged the timer) watching them repeating the same attack for fifteen minutes before the spawn timer ran out, and continuing as most of the people who'd showed up ran off after Adamastor went down.

The groups collecting to summon and defeat Adamastor have taken to, more often than I have seen in the past, clustering on top of the area that Adamastor spawns on, crowding the area that it has, in more than one instance, caused the summoning to fail due to being no space for Adamastor to spawn on. What I would like to throw out as a suggestion for comment is that, as an additional bit of threat added to Adamastor, is to have his summoning include his new "BEGONE" effect as an integral part -- the summoning bringing Adamastor to this plane, but accompanied by an eldritch blast of energy that hurls nearby heroes away. This would make clustering on top of Adamastor's spawn point unwise, as you would make yourself vulnerable to being hurled off the platform. It would also serve to hinder the practice I have seen (much less often since the 20-hour lockout on all the rewards but XP) of parking a melee character at the spawn point with a PBAoE attack on autofire to, first, evade the AFK idle disconnect timer, and second, to automatically engage Adamastor while the player is doing something else, possibly while dual-boxing and playing CoH on another account, or simply with CoH in the background. Characters left at the spawn point with a PBAoE attack on autofire would find themselves flung well away from the spawn point, after which they would have to manually be brought back to the spawn point, so just leaving them there for hours or days wouldn't work any more.

"Power corrupts. Absolute power is kind of neat."

I have to agree with @Uun -- if it's thematic for the character, I'll pick Cryonic; my Ice-based characters all have it, my Fire-based characters will have Pyronic, Electric-based characters will have Ion, etc., with Ion being a common fallback if there's no better choice to match the character. There are a couple of oddities -- Rad-based characters taking Pyronic recolored with the same blues used for the rest of the Radiation powers, instead of the incorrect green color that has become the popular perception of radiation.

Or have a recurrence of the all-too-brief war between the two factions of the 5th Column -- the 'loyalist' side and the Council -- that broke out into open battles in different zones for, IIRC, only two or three days before disappearing forever as the Council completely replaced the 5th Column across Paragon City (which has been reversed to a degree, but we still don't have as much of the fights between the two groups, or the big knock-down-drag-out fights with twenty or so mobs on each side that occurred during the Council rebellion.

And 'proper footwear' is another fairly wide target, although not so much as clothing is. Besides the stereotypical geta, which were worn for specific purposes and by specific social groups, you had waraji, woven straw sandals (for which the existing Roman sandals make a decent substitute, zori, slip-on straw sandals that became 'flip-flops' when soldiers brought them back from Japan after the end of WWII and the style caught on, jika-tabi, which were originally outdoor footwear from which the more recent tabi sock evolved, and okobo, thick wooden sandals worn by young girls and apprentice geisha.

That opens up an immense can of worms; 'kimono' just means 'thing you wear'; what people commonly refer to as a kimono is commonly a hitatare, kachie, kosode, one of the varieties of ho, hoi, suikan, or kariginu (different garments, not just names), one of the various styles of hakama, and optionally a happi coat, kataginu (in one of that garment's several styles), haori, jinbaori, or dofuku. Along with this are the specific combinations of garments composing the various types of sugata or the kataginu kamishimo, the latter being what has become the common stereotype of samurai clothing, composed of a kosode with a kataginu and hakama in matching fabric. And this is just men's clothing; women's clothing had different styles and outfit combinations, sometimes sharing names with the men's clothing -- nagabakama, for example, were different for men and women. Picking which garments you're going to implement as costume pieces in game, even ignoring the potential range of patterns and colors worn during the Sengoku and Edo periods (and completely ignoring kasane no irome, the layering of different colors of garments by women to produce specific patterns that varied by season and sometimes by day within a season, with wearing an improper color choice severely impacting a woman's reputation) is a highly complex decision, unless you're going to take the route of doing the same sort of oversimplification as was done with the various 'samurai armor' costume pieces. If you're interested in a deeper dive into Japanese clothing, armor, and related subjects, I refer you to the Sengokudaimyo website, originally started by the late Anthony J. Bryant as a resource for members of the SCA interested in creating a Japanese persona.

The macro that gets posted in league chat fairly often during the mapserver events: /macro_image "originicon_natural" "LAG Toggle" "++noparticles $$sync" will address some of the lag during a mapserver event, by cutting out most of the haze of power effects. However, many powers have visuals made up of nothing but particles, like Fire Cages, so it's going to make it hard to see what you're doing, and the presence of so many mobs in a small area firing off lots of powers is going to cause significant lag, compounded by the apparently insoluble issue of the sequence, when mobs spawn in, of "mob becomes visible... mob becomes targetable... wait... mob attacks... wait... mob attacks... wait... mob becomes a valid target for attacks that require a target... mob is dead from other players'/pets' attacks before your attack goes off" unless you're targeting through a pet, whose targeting occurs on the server and is not subject to the targeting delay you see on your client.

Ion Judgement also has the drawback that it will not affect mobs that have too recently been hit by another Ion Judgement, which makes it less than ideal in mass-attack situations, like the monster hunting phase of a Hamidon Raid. You can fire off Ion Judgement and have it jump to thirty or forty targets, or you can fire it off and have it make no jumps at all -- and potentially not even damage your main target for the power, because someone got an Ion Judgement off a half-second before you did. The other Judgement powers, while they don't have the targeting flexibility that Ion Judgement gives you, are more reliable -- if a target is in the beaten zone of the power's AoE, they can get hit by the power, regardless of their having had the same Judgement power used on them immediately prior. And Ion Judgement isn't the only "aggro on animation start" power in the game. It has become less of an issue since HC made the change to not have the absurd delay on the power's damage, but Rain of Arrows from the Archery powerset also draws aggro the moment you start drawing your bow. Fortunately, targeting is now determined when the animation starts rather than after the (old) animation delay when the arrows land (at which point in a rapid firefight all the targets were likely to have moved out of the beaten zone before the arrows landed, making the power useless in the vast majority of situations, so all you have to worry about is having all of your targets turn and attack you before you even get the attack off, no matter what degree of stealth you have prior to starting the attack. (The quirk that has the arrows falling vertically from the sky, but turned at a 45° angle, is a separate but not game-breaking bug.)

Let's address some of the long-standing problems with team transport -- like the fact that when you use TT to move your team to the ship in the middle of IP during the Yin TF, it drops you on top of the tail boom of the Hip (Mi-8 -- yes, Paragon City, or Longbow, operates a fleet of helicopters purchased from the Soviet Union; do an image search on 'Mi-8') you enter to get into the mission, leaving you standing in precisely the right position to be struck by the main rotor. Stack this with the long-standing inconvenience of exiting a mission to a helicopter, and finding yourself running into the helicopter, where characters exiting the mission after you stack up blocking your ability to exit the cargo bay, and you get a pair of annoyances that should be easily fixed.