Luminara

That occurs to me very frequently in post-Issue 18 content. It's almost always accompanied by a momentary pause a sudden, large spike (a long block of red, at least a quarter of an inch long) in the netgraph. That indicates that there's a miscommunication between client and server. I've been logging in with the diagnostic client since it was released, and I switch back to the open command line window often just to see what's going on, so at some point, I'll dig up one of those missions that cause it and see if it passes anything to the command line window. It's not you, or your computer, I can assure you of that much. Beyond that, I can't say until I test.

There'd have to be an aggro redirect to prevent them from being used as a griefing tool (placing the debuff AoE on another player character specifically to draw enemies to that character). And an additional graphics option to allow the effects to be disabled by the anchor, to prevent another type of griefing. But I don't see this happening at all unless yet another change is made, that of allowing the player to choose, on the fly, whether to toggle it on an enemy or ally. An outright switch to targeting would impact gameplay for a lot of players who are already accustomed to enemy-targeted toggles. It would also make it impossible to use this type of toggle solo for any player who doesn't have a pet. I'm sure there are any number of people would would strenuously object to having their primary method of mitigation taken away, and more who would object to being "forced" to respec into a PPP and take a pet they don't want, or feel they need.

They usually do add a freespec when powers are adjusted in Pages. I know I remember one of the HC team stating that in a recent (sometime in the last year) thread. Not sure why one didn't go out this time. @Cobalt Arachne?

Null the Gull grants that level of power, on request. And a badge.

Status effect procs are generally underwhelming, with low durations and low magnitudes, and the Stun procs are the worst of the lot. You could try Devastation: Chance for Hold (mag 2, 3 PPM) and Lockdown: Chance for Hold (mag 2, 2.5 PPM) in Dominate/Total Domination. If you dip into melee, Cross Punch and Boxing have chances to Stun, and any melee attack can take Blistering Cold: Chance for Hold, which is about as good as Lockdown's proc (the superior version is... superior). If it's a 35+ character, I really can't recommend Earth Mastery enough. Fissure has a 50% chance for a mag 2 Stun, and a 50% chance for a mag 1 Stun, and they both stack, with each other and with other Stuns. You can get a lot of Stun mileage out of Fissure. Throw in Cross Punch and you might find that you don't have to use other controls very often, what with everything either on its back or ambling around dizzily. And Seismic Smash is not only a hard-hitting attack, it's also a mag 4 Hold, an instant boss neuterer. Go Stone, skip the procs, you won't even need most of your primary.

CoD verifies that it is set to 8 seconds. If it's not lasting 8 seconds for you, it's status resistance or enemy level (8 seconds becomes 7.2 seconds on +1 foes, 6.4 seconds on +2 foes, 5.2 seconds on +3 foes and 3.84 seconds on +4 foes). Working as intended. A minion or higher with a mag 1 mez on it isn't "contained", as it's not Stunned/Slept/Held/Immobilized. It will stack with other Stuns.

https://homecoming.wiki/wiki/Ouroboros_Badges

Set difficulty to -1/x1. Log into level 50+ character, buy Ultimate inspirations, mail to self. "Earn" title with no risk, pound chest. Also, there's a forum for suggestions. It's named, conveniently, Suggestions & Feedback.

Also, no.

Then don't. What they do doesn't affect you, and what you do, or don't do, doesn't affect them. But as always, your hyper- and hypocritical assessment of others is entertaining. Please, do continue.

You sound... beleaguered.

Nobody is making double D wisecracks? Where's the innuendo? How can I make it through the day without veiled sexual references? DO I HAVE TO DO EVERYTHING MYSELF?! Something something more than a handful something. 😠

That the badge pop-up itself says it grants 5 charges of Experienced, and that only characters with extremely long periods of inactivity aren't receiving those charges, indicates that the problem is not a missing patch note, but a bug preventing characters which meet specific conditions from receiving the power. Get off the patch notes fixation. This is no more a patch note problem than it is a day job problem. The end result is the same, the means is not. Experienced is a power that grants 5 bars of patrol XP instantly when it is used. Until Experienced is activated, it's not patrol XP. It has no more interaction with patrol XP, day jobs or day job locations than the Bow and Arrows temporary power, or the Nemesis Staff temporary power, or any other temporary power which is not directly linked to day jobs. If the only way patrol XP benefitted level 50+ characters was debt relief, level 50 characters couldn't accumulate patrol XP. Right here is proof that they can and do accumulate patrol XP. I even made sure to screenshot the total so you could see that it's maxed out, 10 full bars worth, the equivalent of one level. 5,608.000 points of patrol XP on my Staff/Willpower with 96 veteran levels. I can take screenshots of 20 other level 50 characters, all with patrol XP. Being 50 doesn't restrict a character from receiving patrol XP. That wiki, by the way, is the archived version that doesn't include any of the SCoRE- or Homecoming-specific changes. One of those changes, for instance, was veteran level acquisition being moved to the standard leveling pattern, rather than set temporal intervals (3 months). We gain veteran levels, one for each level we would otherwise have gained, after hitting 50. As such, we also now accumulate and use patrol XP on level 50 characters. The old wiki doesn't reflect that and that's one of the reasons we don't refer to it. It's sorely outdated. https://hcwiki.cityofheroes.dev/wiki <- use that in the future, please. This character had been logged out for over 100 days (142, if i recall) before I logged into it to take this screenshot, and has 10 bars of patrol XP waiting to be used. I received those 5 charges of Experienced when I logged in, as should be evident from the anniversary badge pop-up that I left open for this screenshot. That's pretty conclusive proof that patrol XP doesn't prevent Experienced from being granted on sub-50 characters. I have plenty of sub-50 characters that I can take screenshots on if you need more evidence. You're trying to help, we get it, but this isn't helpful, it's a hindrance, and a diversion from the reported bug. There is no correlation between patrol XP and the failure of the anniversary badge's Experienced grant. You've conflated the two erroneously. Let it go.

The Snarkitect.

This has nothing to do with day jobs. Read the first post. Read the anniversary badge pop-up. Read the information on Experienced that I linked from CoD. No, that is not what the link said. The link is for the Experienced temporary power. Experienced is not a day job, it's not acquired through a day job, day job locations are irrelevant to this thread. This is also irrelevant, because the bug report is not about patrol XP, it's about Experienced not being awarded when conditions indicate that it should be. And the wiki is wrong, too.

https://cod.uberguy.net/html/power.html?power=temporary_powers.temporary_powers.alt_experienced This power is supposed to be awarded when a character receives the anniversary badge. @ZephyrWind is trying to report a bug related to this. It has nothing to do with day jobs.

I, Luminara, creator and overlord of the Lumiverse, hereby declare that Storm Blast shall henceforth be known as... Buford.

Playing is grinding, you can't expect anyone to do that! What kind of sadist are you?

Battle Axe, Broadsword, Claws, Dual Blades, Katana, Staff, Titan and Mace. Yeah, a shuriken qualifies.

Umbrella Assault! Dignified and dangerous.

Okay. Your comparison to Savage Melee isn't valid because the work was done in the SCoRE years, when the developers were catering to an incredibly small group, at a much more relaxed pace, and trying to satisfy everyone in order to keep the server running and that scant handful of people there. It wasn't even remotely like a real beta, open or closed. And your comprehension of how an open beta should be conducted is clearly distorted by that experience. Open beta is not a negotiation. Open beta is not the time for sweeping changes. Open beta, in this environment, for a larger audience, is the "is it good enough to go live" point. Moreover, you waited until the set was in open beta for a week before you said anything. You didn't speak up during the closed beta test, despite having an active account there. You didn't participate in the alpha, either. You ignored everything until it was in the end phase. You had months during which you could've spoken up and had a larger impact on the direction and design of the set, and you ignored it. But here you are now, insisting that feedback doesn't matter and testing is pointless. The irony is palpable.