Your OP didn’t say anything at all about FW? Just about replacing “group sites” with multibox-inefficient sites. Despite saying “it’s not about removing multiboxing”, replacing multi-ship sites with anti-multiboxing mechanics pretty much is about removing multiboxing.
Not that I’d care if that happened, but I expect it would significantly impact CCP’s bottom line.
Also, the multiple points about FW multiboxers are not well made. I haven’t FW’d in over a decade: I found it boring and annoying back then and none of the changes I’ve seen since have promised better. Although at least they have made some changes, which is hopeful after they ignored it for so many years.
At any rate, awoxing and stagnant warzones have been problems for years, afaik, and not limited to multiboxers. And I’m not sure how a multiboxer “monopolizes” a system while also at the same time immediately warping out when any threat shows up? Or how one person monopolizes 5-8 sites at the same time more efficiently than you can with a friend or two?
I’m sure FW has many problems - it always has. If it’s not multiboxers, it’s bots. If it’s not bots, it’s awoxers. If it’s not awoxers, it’s low-sec corps flying in to nuke everything even though they’re not enrolled in FW. Or it’s cheap ships (Atrons etc., or Ventures back in the day) filling complexes and warping out the second anything blinks.
I get that nobody likes to show up at content and find a multiboxer already there. And we all agree it’s not ideal, but reality says it’s necessary.
I don’t think it’s unreasonable to ask you to either support your case better, or make proposals that don’t blame multiboxers for everything wrong with FW and instead perhaps address the actual core issues: awoxing, poor site design or whatever.
“Everyone knows multiboxing is totally dominating and ruining FW” certainly sounds dramatic, and I’m sure they’re annoying. And I have no qualms with, say, adding a hacking step to flipping a complex. Although I doubt that would solve your issues, especially since you’re trying to hang generic FW problems on an unrelated cause.