Player Features and Ideas Discussion

So i've seen alot of people suggesting that to fix this, you can just impose a bounty multiplier on the region that starts at 1.0 and decreases over time depending on the amount of isk paid out in bounties.

This is a ******** idea. The problem with straight up setting an isk cap for a region is that it means that 3 - 4 guys ratting in supers ruins literally everyone elses income in the region. Imagine logging in at 6pm after work and wanting to do some ratting to find that the bounty payouts in your region are now like 0.2 because numbfuck nonirons and xxsuperp1l0txx spent the last 3 hours super ratting. All that will do is **** off people in the region.


"So, Gian(t) Bal(ls), how do we fix this then?


Well, my solution is to reduce the respawn rate of the anomalies, when i used to carrier rat my system was fully upgraded etc. which meant when i did one haven/sanctum, another would respawn a few seconds later and there were like 3-4 at a time in system. This is fixed by making anoms respawn less the more you rat.

So for example say there is 4 havens in system, you do 3 or so within a short period of time, the respawn timer for them increases by like 15mins (or insert another period of time here) for every one you do for the next 20minutes. However this would only apply to the anomoly type you are doing. So lets say you get this stacking penalty thing on havens, if you then go to sanctums, they will respawn normally until you hit that cap you did with the havens.

This means that systems with multiple super ratters in them will actually have to do the lower class sites too while they wait for the havens and sanctums to respawn, this in itself means significantly less isk made in the region due to the low bounty payouts. On top of this, super pilots will need to be warping around the system alot more frequently to complete different sites. This actually indirectly decreases the isk made in the region because now the supers/carriers are having to warp to more sites more often (the lower class anoms would literally take a minute or so for a super to complete) , more hunters will be inclined to come and hunt, and more hunters would succeed because when they jump in, they will have much more time to locate the target and land in the site to bubble it.

Also, because these respawn rate penalties would only be system wide, it means ratters will be forced to spread out across a region, which potentially means carriers/supers doing 1-3 jump trips to adjacent systems to do higher class anoms there until thei r previous systems sites respawns, which means catching carriers/supers on gates. Also, this would in turn give sov more meaning to a large alliance, because currently for a large alliance holding an entire region, realistically they will only really have a handful of important systems, a few ratting systems and the rest of the systems 9 times out of 10 will just be empty (apart from when people travel through them ofc). However, because with this system people would spread out across more systems, big entities would actually value alot more of the systems held in their sov.


Obviously this idea would need some tweaking, balancing of numbers etc. but to me this seems like one of the only logical solutions that could aid the isk faucet problem alongside spreading more people around the universe as oppposed to huddling into 2-3 home/ratting systems.

Banning carriers/supers or making the rats shoot fighters more isn't even necessary, as I said the problem has nothing to do with how quick people can ran the sites, its how often the sites are there to run which is the issue. Using a system like this would encourage hunters to place logged off cyno alts in havens/sanctums in systems surrounding main ratting hubs which would mean when people venture out to find more high tier anoms to run they are met with a cyno. This would make pilots much more cautious and could in turn actually greatly reduce the amount of super ratters in specific regions because it would essentially become a game of minesweeper were they have a good chance of getting dropped on when they warp to a haven the next system over.

Even if the people didnt venture to other systems, they would still need to wait for the sites to respawn, therefore reducing the isk made in said region anyway. I like to think of it as a system wide anomaly fatigue.

Lets be honest ccp aren't gonna try fix something like fighter squadrons, this nerf run they are doing on them now is probably about it, and they reduced the nerf because everyone bitched about it.

Null sec is already such an easy way to make isk and it's a perfect time to revamp the anomalies in null altogether, with my proposed system, there is no change to how fast someone can run a site, or how many someone can do, or how much each site gives. By simply adding a respawn delay to the anomaly time in each system depending on how many of said anomalies are being run in a certain amount of time, it encourages people to spread out across a region and populate the otherwise stagnant space that alliances hold just for the sake of holding. By nerfing the fighters damage you aren't just nerfing the ships PVE ability but most importantly its pvp ability. Carriers are already a bit meh for pvp for the simple fact that their fighters are quite vulnerable when they get deployed far from the carrier. By adding this respawn delay, it lowers the overall isk output of the region both directly and indirectly (indirectly meaning the risk vs reward stuff in my original post with increased hunting etc.) whilst allowing people who only rat with stuff like ishtars to still earn what they would that they do now.

The only people my system would directly affect is carrier/super ratters that blitz through the havens etc. in a matter of a few minutes. People who rat with ishtars, machariels, and other subcaps like those won't actually be able to blitz through the sites quick enough to trigger the respawn delay (except of course if there are multiple of these running the same sites in the same system).

LOL, so ships and weapons systems are the problem with the economy? Then you're right! We'd better start applying that nerf bat to those damn ships and weapon systems! Hell, lets start ELIMINATING weapon systems - not just fighters, but others as well. After all, we don't want the money supply to explode or anything.

I have probably as dim a view of most people's intelligence as one could possibly have... but even so, it surprises me that I still get surprised from time to time, more often than I would like.

With a cyno, in range of a (super) capital blob.

No, you tried to sneak in risk that simply isn't there to make your point.

I don't know if you are a moron with reading comprehension issues or what. You are certainly a troll, because I've read your other posts.

Be that as it may, if you are just a moron and cannot comprehend simple english, I'll try again. The point of my suggestion of the triage module was to add additional risk to using a single carrier to rat with.

What's-his-head wasn't specific. I thought he was referring to being within range of an ENEMY cyno, and (possibly incoming) supercap blob. I was like "yes, that's the point - to add risk." Because that's what I pictured - an enemy being cyno'd in.

I already said I don't prefer this solution, but the point was, CCP should be trying to target and fix THE ACTUAL PROBLEM, not just nerf a ship's DPS, which is stupid. This one idea was an attempt to do that.

Simple elegant solution....

CCP levies a tax on carriers and supers while ratting.

The tax rate?

100%

Problems solved.

Stop a massive expansion of the money supply. No need to nerf the PvP capability of a carrier or super.

Clearly you didn't even read it then because you would understand that this delaying of anom spawns would only be triggered if x amount of sites were being run in x amount of time. So for people ratting in one or two afktars, rattlers, domis etc. there would be very little (if any) delay, whereas where supers and carriers would be blitzing through the sites so quickly it would trigger the anomaly spawn delay.