LotV Beta Balance Update - June 17 - Page 7

On June 20 2015 00:01 Foxxan wrote:
Really like the overlord change. As long as every race has good firepower in the early game so its not about high tech etc i think it could work out great.

What i absolutely like about it is the potential for zerg to be agressive from the early game and not in an all-in or cheese way

On June 20 2015 00:31 JCoto wrote:


That is the problem, only 2/3 races have enough firepower eary game.

Protoss will have serious problems as the current design of Adepts is very poor and subject to change, even if it is working quite acceptably at least early game, reaching the bordelrine of problematic.

We still have Photon Overcharge into the game and no efficient production till Warpgate

On June 20 2015 00:33 Daralii wrote:

Such is the cost of warp gate.

On June 20 2015 01:05 Lexender wrote:


You can have good Gateway units.

You can have warp gate.

But you can't have both.

On June 20 2015 01:54 swag_bro wrote:


All I read from this is that Terran and Zerg can expand to island bases super early and relatively safely while Protoss would have to invest into so many resources just to have that ability. Good job Blizzard. Now all the map makers need to do is never make island bases ever again.

On June 20 2015 00:20 owlman wrote:
Snipe is not mandatory vs HT, EMP is enough.

On June 20 2015 02:12 TheWinks wrote:

The ghost vs high templar setup already favored the protoss. Requiring 2 75 energy abilities just to prevent a Templar from storming, which can then merge into an archon requiring more 75 energy abilities to fight is a massive change.

On June 20 2015 00:06 Foxxan wrote:

They should go away from the ghost vs hightemplar fight 100%. When the armee all relie on those few spellcasters it becomes quite boring to watch and play.

As we mentioned before, we’d like to provide our thoughts on areas that we’ve looked into this week based on community suggestions. Before we get into the details, we’d like to point out while we try our best to hit majority of the big topics, it’ll be impossible to cover every single topic every time. The goal here is to discuss big issues with you guys, and continue doing so over time. With this first post, we’re covering a few more topics than we might typically cover in a normal update. However, we think this is a good way to kick off these updates.

We’d like to also make it as clear as possible that game design is not about implementing every idea that the majority thinks is correct, it’s about finding the key ideas that will be best for the game. So we’ll do our best to keep an open mind on topics and even if we’re currently thinking that we won’t try something out, we’ll keep it as part of our regular discussions if those issues keep being brought up by the community. Please also try your best to do this as well, and remember it’s not about how many people say something, and it’s not about bandwagoning onto the loudest idea. It’s about trying to look at issues from every angle possible to make sure it is in fact what’s best for our game. Just as an example, internally in design meetings we try our best to detach ourselves from every idea. Even if I’ve suggested something, I try my best to analyze how it might be bad. This way, I can focus on the specific idea and if it’s the correct move for the game, rather than pushing for the idea just because I thought of something I think is awesome.

Here are our thoughts on many of the bigger community discussions this past week:

Flying unit separation radius

We agree that when you are controlling larger numbers of air units, it’s difficult to do the moving shot micro.
This requires a code fix, and we’re currently exploring and testing something that we can add to the beta soon.

Making all damage points to zero for air units

One of the reasons we don’t have a default damage point of zero is so that the timing of micro has to be mastered by players. Just making it zero will mean microing is just much easier, which is probably not the direction we want to go.
We generally don’t make extreme changes that alter so many things at once, due to the side effects these changes can cause. Changing every single air unit’s damage point is not something we’d like to explore, but we’d be open to specific air unit damage point changes if the change makes sense.
With a damage point of zero, a unit that is facing its target can immediately move away after being issued the attack order. With the default damage point, the player must instead time their movement to happen after the attack is performed. An example of where this is pushed even further is the Hellion, which has a higher than normal damage point. The unique timing required for this unit requires additional mastery, which makes it more impressive when pros are able to be so effective with them. Since the suggested goal of the change is to have more interesting micro, in this specific case, we wonder if what we currently have is more interesting micro than the proposed changes.

Siege Tank /Immortal turret tracking

This sounds like a very minor change that probably won’t have a huge impact. However, because many players believe this will be of great help, so we’ll test it fairly quickly internally, then put the change in also in the beta. So you can expect this change to go into the beta soon.

Community resourcing model suggestion

We also watched show matches, tried games ourselves, and we agree with the majority of you guys that it’s too similar to Heart of the Swarm. But we wanted to comment again on this because it’s still a topic discussed by some.
Just to reiterate once more, we’re not looking to make minor tweaks in this area. We’re looking for a big change that will make sure that players will spread out their expansions at a much faster rate than they do in Heart of the Swarm.
Currently, the resourcing model that we’re testing in the beta is doing a very good job of this.

Ranked play in the beta

We hear your feedback and agree that it’ll be good to enable ranked play.
We may not be able to do this right away as we’ll need to introduce this with a client patch and can’t use the same method we use for the balance update which is done through publishing.
Due to the feedback we’ve seen on this topic, we’ve currently scheduled to enable ranked play in the beta with the next client patch.

Disruptor being too all-or-nothing

We agree with you guys here. The optimal case looks too strong, and when you miss with a hit it seems like the Disruptor is killed too easily at such a high cost investment.
We’ve been trying various things in this area for a while now, but this is where we’re at right now:
Much lower radius (this is the biggest change + Disruptors look too underpowered right now in our testing)
Lower cost
Faster speed when activated
Less delay before firing

Overall, it looks like we have a decent solve for the case of a single hit ending games often.
We believe the next step in this area is to test out changes that would allow players to more easily save and reuse the Disruptors. This way, we can solve the issue where a miss creates a high chance of the game being over.

We’d also like to comment on some topics that we found interesting this week. Again, please keep in mind just because we don’t mention something here, it doesn’t mean we haven’t read it. While it’s impossible to read every single post that comes up every day, we do try our best and can tell you that we read a big majority of the things you guys bring up.

Adept micro tips video was very cool.

It was a very good example of relaying more info on something new, so that players in the beta can better test new units.
It would definitely be more cool to see more tips on new units videos, because we believe faster we have the majority of beta testers ramped up with new units, the more high quality beta testing we will have going forward.

There was a post asking if players want battles to last much longer. Our thoughts are that the current pace feels really good, and we were happy to see that most players didn’t want battles to last longer in StarCraft II.

On June 20 2015 02:29 JCoto wrote:


First, Snipe costs 25 energy. You only need 2 snipes to kill an HT (50 energy). If you kill HT, you prevent it from storming. No use of double ability as you said.

I wouldn't call "favored" since a good EMP can drain 50% the energy from 7-8 templars (It happened today in 2 matches if I'm not wrong) and Ghosts can be cloaked, spread and used in ambushes, they only need 4 shots to kill a templar with basic attacks....