Luminaar wrote:The Hawk AI doesn't change the strength of nodes that are already connected to a choke point. If a players programs dictate that a triple Turret choke requires shocking to overcome now, a Hawk AI isn't going to change that fact.
The hawk AI changes that from level one. I now have incoming DPS that I have to deal with even after using a shocker, which means I might as well use a protector if I can't stop all incoming DPS and use all program slots available for my shurikens. Of course, on TLR because my protector is 13, I'll still need to rely on shocker to get through such a choke point until I level up my protector, but on Azu since my protector is level 18, I won't have a need for shocker where I otherwise woulda used a shocker because now protector on every choke point is more efficient than shocker. Only scenario old shocker strat is still viable is on shocker worthy choke points such as Festr's 3x Black ICE choke where the hawk is not present. With time those choke points will become a thing of the past and shocker will too as more and more people get back in the game and get that annoying little bird.
ICE Wall. ^_^
The Hawk doesn't do any damage here. This is a visual bug related to Hawks interaction with Portal.
It was a visual bug that the firewall on that node was going down when the hawk (now pheonix) was attacking it? And by suggesting ICE Wall you are agreeing that shocker isn't the program of choice in such situation hence why the hawk has killed the shocker? I mean, shocking and using ICE Walls is gonna mess you up because eventually they break and you need to replace them which may take an extra program slot to replace the one about to break so you don't lose the node, then you must keep shocking and who knows how much DPS you need to take down the nodes you're fighting. So many programs wasted, so cumbersome, so why not use a protector right off the bat instead and avoid all the trouble? [/quote]
Luminaar wrote:When the input variables change (ie, the addition of the Hawk), using the same tactic you've always used probably isn't the most efficient anymore.
I acknowledge the fact the bettle has added stall time and hawk has added DPS to the defender's choke points, but even then the protector remains more efficient than shocker.
Luminaar wrote:I see you mention this a alot, and you might need to reconsider this analogy. There are other variables to consider, including a players ICE Wall, Protector and Shocker strengths, and using a combination of methods to protect against both direct and indirect attacks, is not the same as purposefully using programs when they will deal the least damage.
Idk what you meant there at the last bit about using programs when they will deal the least damage, but with all the new data available now, it looks like I'll have to max out my protector now to stand a chance against what is now gonna be the new maxed out DPS and great stall choke: 4 Black ICE 21 shielded by 3 golden guardians with a bettle 21 and hawk 21 on top of that. That is a choke point where I might have to double down on protector because it's almost too much DPS and stall time for a protector 21. Still not using a shocker with a protector there, because 2 protectors are more efficient than 1 protector and 1 shocker on the same node.
These AI didn't change the game up in a good, refreshing way. They're just an annoyance now because now I will need to use less programs to hack since the protector is now the most efficient program to use at any choke point over the shocker. This is all because of compile time and bitcoins cost efficiency that I don't think you see clearly judging from your stance on this argument. Shocker spamming scrubs on the other hand that lack knowledge and skill, will continue to shocker spam so the AI hasn't gotten rid of that issue, instead it's rendered the proper
use of Shocker useless and that's what I'm salty about. There's less analyzing needed prior committing to a hack, less strategy, less programs needed to hack, so overall the game is less fun.