macskull

That’s one thing I think Rebirth has done well - putting content-specific set enhancements behind those badges. It might not necessarily get more people to run the badge content but it absolutely gets players who don’t want to run it to subsidize builds for the players who do.

Until we're in a situation where the no-incarnates no-temp powers no-deaths "Master of" badges are actually needed for something, you're going to continue to run into this kind of issue because people just don't run them very often. There's no incentive for doing so aside from a badge which doesn't grant you anything, and content where a single death ruins the badge for the entire team - in a game oriented around teaming - is Bad Game Design. The "no deaths" requirement is so binary that I don't think there's anything you can do to fix it.

Me reading through this thread, trying to figure out WTF “new changes” the OP is talking about, then seeing they have exactly one post and it’s this absolute gem…

The requirement imbalance is intentional. It’s to get more players to go redside and do the SFs.

What’s really strange is it looks like none of the stuff that was getting that kind of reaction from testers made it into this update. Weird, huh?

It’s not impossible to disable it by default, it would just require a little more work - like, giving players the Power_DisallowGroupFly token by default. Pets would still be affected, so this is an “everyone wins” scenario. ”If I have to go out of my way and remember to do this thing so a rarely-taken power doesn’t affect me, so can everyone else” isn’t a great argument either. Just because you’re okay with being inconvenienced doesn’t mean everyone else needs to be.

“Everyone else should have to go out of their way to change a setting so my build doesn’t annoy them” isn’t a good argument. People don’t turn off Group Fly at Null the Gull because running into someone who actually takes and uses Group Fly is rare - and if they’re on a task force they can’t go there and disable the setting if they even wanted to. Honestly, the simplest solution to this issue is to make Group Fly disabled by default so the people who want to use it need to go talk to the bird. You believe incorrectly. It has never worked that way.

If you’re concerned with efficiency, not really.

FWIW those “all procs all recharge and HP no defense no resistance awful recovery” 4-star builds are usually built with a specific team composition in mind, but they are also extremely capable in regular content. Sure, you’ve gotta crutch them along with things like amplifiers, recovery serum, and inspirations, but the cost of those things is a drop in the bucket compared to the inf you make from just making things die.

The Tanker changes + Fury changes + aggro changes + Burn nerf really did it in for Brutes. Sure, if you already have one there’s not really a reason to roll a Tanker to replace it, but if you’re making a new farmer I wouldn’t recommend a Brute to anyone.

Mids has been incorrect about this specific IO since before the original game shut down. Mids is at the top of the “do not trust this” list, followed closely by ingame info. Hell, sometimes even City of Data is wrong.

My characters are also easy to identify and have a system to their names - when you right-click on the character and get the global, they all say macskull or one of my other accounts!

I would drink that, ngl.

Check the links in my signature, which has historical data for player counts over the last two years. Any "seasonal variation" that exists in a game with a population the size of Homecoming's is so small that it's basically imperceptible. You are correct in that the population has increased compared to what it was immediately before the announcement (roughly 55-60% higher), but it's also around half of what it was at the peak shortly after the announcement.

The population is lower now than any time in the last four and a half months, it is definitely not increasing.

It was changed in Issue 22, which was released about 8 months before the game shut down. The behavior you’re describing (which also let you do things like put Membranes in Mind Link and Vengeance, or Centrioles in Thermal/Sonic shields) was around for a long time and many people don’t know that it ever got changed.

IOs predate VEATs by over a year. Mind Link has never allowed recharge enhancements, but it's always been affected by the recharge portion of set IOs. It used to be affected by Hami-O's with a recharge aspect, but that was fixed sometime before shutdown.

These two methods of preventing boosts are functionally equivalent from a player-facing standpoint. Considering the slotting oddities with Hami-O's haven't been possible since Issue 21 (22? I don't remember), there's zero reason for the power to behave as it currently does.

With a 50-player cap in the zone, a handful of people who aren’t actively involved in the event absolutely can result in failing. The raid leader can adjust their strategy to mitigate this risk but then that falls onto the raid leader to 1) correctly guess whether there are enough potentially “AFK” players in the zone for it to be a problem, and 2) communicate the change in strategy to the group at large, who may not be familiar with the new strategy. This wasn’t at all a concern when the zone cap for the Hive and Abyss was accidentally bumped way up in early/mid 2019 but it became one once the 50-player cap was restored. This would not solve anything and would more likely than not cause the raid to fail, because half the people on the league will have TP prompt on so they’ll get blasted too, and instead of killing Hami you’ll just have a full-health Hami with three or four sets of mitos which you’ll then have to meticulously clear or give up and wait for a zone reset. And if you do manage to recover from that, the dead people in the bowl already got their hit in so they’ll still get credit for the defeat at the end as long as they don’t move. EDIT: I don’t particularly care about the arguments around the one or two people at a raid who aren’t on the league. The zone cap at 50 and league cap at 48 are incompatible with each other, much like how hot dog buns come in packs of 8 and hot dogs come in packs of 10. A full zone is always going to have at least two players who aren’t on the league. There may be a perception from some on the league that those players aren’t participating, but a cursory glance at name colors during the entire event should make it obvious whether that’s actually true. A good raid leader should already be doing this. An instanced raid does not make things more difficult for soloists; rather, it makes things easier for the raid leader and significantly minimizes the risk a griefer poses to the event. EDIT 2: Even if an instanced Hami raid accomplished nothing else, it would still provide a solution to the dozens and dozens of wasted man-hours spent across the servers each and every day by players waiting around to secure a spot at a raid.

Liking an idea and then later being opposed to that exact same idea because of why someone wants it is kinda yikes. At that point you’re no longer opposed to the idea on its merits but because you want things to continue to be difficult for that person.

Also, different leaders do raids differently and I ain’t trying to do a Hami raid the slow way on a different server. P.S.: @Mayaedits get back to work

This is the biggest reason I don’t come to Hami raids much anymore. My time is limited and having to get to the zone 30-60 minutes early to have a chance at even getting in is a non-starter. Sometimes I’ll show up closer to the start time and get in but usually the zone is long full and I’m off into the depths of AE farming again. +1 for instanced MSR. Griefers are still gonna grief but at least if they’re being obvious about it the leader will have an easy way to make sure they don’t end up on one of their raids again.

Global chat doesn’t have chat bubbles like other chat channels because the global chat server is completely separate from your local character and the rest of the game.

It’s a problem unique to chain powers. In this case, Storm Blast is the only blast set that has this limitation, which makes its AoE clunky and inconsistent. I’ve brought this up to the powers team already and was told that it is unlikely to be changed because Chain Lightning has several benefits from being a chain power. About the only reasonable benefit I can see out of it is that it has a theoretically larger AoE area than a standard targeted AoE, but I don’t know that the larger potential radius ends up making much difference in practice and it comes at the expense of proc rate and that 5% chance to just be a dud. Even some kind of “second chance” mechanic would be good.

To the OP: have you tried to talk to the person holding the name? How do you know this person is “camping” your name?