Now, let's talk about this change in particular.
I can understand why some people feel this change is coming out of left field, especially if their particular playstyle happens to be in areas where dreadnaughts are not seen as often.
The initial trigger for thinking about making this change came from concerns raised about how the Tracking Computer buff would affect the area of the game where tracking fit Dreadnaughts are at their strongest, in wormhole PVP. This caused us to do some thinking about the specific interactions at play, and we determined that although the effect of the overheating change would be fairly minor, we could play it safe and make a fairly minor maintenance change to capital turrets at the same time.

That's exactly what this change is, a minor maintenance tweak. Making small, contained changes more rapidly is a very good method of balancing as you can fine tune attributes into the best possible state and watch the results without as many secondary effects. This change (as well as several of the other balance changes I announced yesterday) fall into that small contained iteration category.

It appears there are many people who seem to believe that this 5% will somehow crush Dreadnaughts or significantly decrease their use. I disagree, but I also welcome everyone to test these changes for themselves when SISI is next updated. As proven many times before, we are always open to adjusting or canceling proposed changes based on good solid feedback.

Anyone that really LEAVES because of these TINY changes is really a coward or a baby.

If you could blap webbed players with your Moros before, you'll still be able to do it.
If you could farm sleeper escalations using supported dreads before, you'll still be able to do it.
If you could burn down a bounced supercarrier with your dread hotdrop before you'll still be able to do it.
If you could alpha an orbiting Archon with your Omegafleet Nags before you'll still be able to do it.
If you could hit those Omegafleet Nags with your titan guns before you'll still be able to do it.
If you could mine veldspar with your Revelation before you'll still be able to do it.

I think you will all find that this change results in pretty much the same gameplay as before, and only serves as a very slight reduction in total effectiveness compared to the status quo. If you discover differently on SISI or potentially later on TQ, let us know in a calm and reasoned manner and we'll always be very open to reevaluating these kinds of attributes.

Did you intend to sound like you were promoting Obamacare? Because it sounds like you are intentionally mimicking the stunning success of that amazing plan. It does not increase confidence amongst your US players.

Why can't you put your analysis up front when you announce a change?

1. Here is the problem we have identified... This is our long-term goal or vision we are trying to achieve...
2. Here is our proposed solution... With charts, graphs, and rational argument.
3. Please give us constructive feedback.
4. Profit???

Ok I'm done my meetings for the day, time for a longer reply post.
This proposal is for a 5% reduction in capital gun tracking.

Oh joy making my titan even more ****. will i even be able to track a station now ?

Or you can consider the argument that they are happy with the effort it takes to dread blap stuff in wormholes and thus are nerfing dread guns to BALANCE the buff to tracking computer. The your numbers show that the nerf doesn't harm dreads and it isn't hard to carry a stack of tracking computers and and a couple mobile depots for when you don't have a carrier right there to swap them and you can have BETTER tracking then before.

Your argument simply boils down to "OMG YOUR ARE NERFING MY THING! STOP IT!" instead of providing any good reason to not do so.

Anyone that really LEAVES because of these TINY changes is really a coward or a baby.

If you could blap webbed players with your Moros before, you'll still be able to do it.
If you could farm sleeper escalations using supported dreads before, you'll still be able to do it.
If you could burn down a bounced supercarrier with your dread hotdrop before you'll still be able to do it.
If you could alpha an orbiting Archon with your Omegafleet Nags before you'll still be able to do it.
If you could hit those Omegafleet Nags with your titan guns before you'll still be able to do it.
If you could mine veldspar with your Revelation before you'll still be able to do it.

On the subject of time "wasted", these changes to one base attribute (on just 6 items in this case) are extremely fast to implement and test. This did not take time away from any other feature designs.

So researching and testing for such a pointless change doesnt take time? Maybe thats the reason some of your "balancing" doesnt work?

Ok, so you think that just because we can overheat module means we want to overheat it and carry spares around just to get our pre-patch tracking? The Revelation and some moros fits wont have that option, the only dread that will really feel a boost is an armor nag with 2 sebo 2 tc 2 heavy cap booster. A rev has 1 tc, so it's tracking is still going to drop despite your plan to "make them better" In some hot drops or even capital fights, you aren't in range of a carrier and are to close to drop a mobile depot to refit, so overheating your modules for XXXXXX isnt an option. As a Titan pilot you may not want to carry 2-3 sets of faction tracking computers just so you can burn set after set to get your pre-patch tracking. Maybe reconsider your general overheating ideas to certain modules that the players never even wanted to get the overheat bonus. Sensor boosters, tracking computers and cap boosters, as a dread you now to overheat 2/3 of these just to continue shooting and to get your pre-patch tracking back, the amount of heat damage will go up and the time a pilot can overheat to get his pre-patch stats will decrease. As a dreadnought pilot, I really dont want to have to carry 2-3 sets of Cap booster, tracking computers and sensor boosters just incase we have a fight that lasts longer then 5-10 minutes.

wtb nag gun that fires tremor

This nerf is directly the result of another nerf. Tracking computers getting heat, this is odd because heat is designed to make stuff better at the risk of destroying the module. So, instead of balancing the module's heat, you will nerf the most expensive ship that could possibly benifit from it. I am in complete agreement with the statment "Then why bother at all? You're argument here counters itself. If a 5% nerf doesn't stop dreads from doing anything they currently do, then don't do it. I don't see any point in having even a 5% nerf to a ship that is expensive and puts itself at risk to fulfill its role"

Quite simply yes, our argument boils down to dont nerf stuff with no logical reason. There is no proof that the nerf needs to be done, we have not been provided any substantial evidence that this nerf is required in any fashion.

We would be happy with any number that atleast point in a logical direction. You are correct, there is no evidence to not nerf the ship. There is only logic, simple as don't **** **** up without a good reason. Give me a good reason and most of us nay sayers will be happy.

It is a simple question that needs answers.

Hello again! This thread will cover the changes to the base tracking stats of all capital turrets alongside the expansion of heat to Tracking Computer modules.

I advise reading the Heat Iterations post before this one.

When expanding the ability to overheat to Tracking Computers, we investigated the effects that the change would have on different levels of turrets and the doctrines that use them. With the help of the CSM we have identified that the effects on Capital Turret tracking would be (slightly) negative so we're making a small tweak to them at the same time as the heat expansion.

In Rubicon 1.1 the tracking speed of all Capital Turrets will decrease by 5%.

This means tracking will be 5% down vs current TQ values when not overheating any TCs, about 2% down when overheating one T2 TC, and about 1.5% up when overheating two T2 TCs. Using higher meta TCs makes the crossover faster.

These changes will be on SISI very soon for you to try out for yourself, and as always we look forward to hearing your feedback.

Thanks!