@jimmo52 wrote:
@KidShowtime1867https://youtube.com/clip/UgkxwVA83Z39WG_BnefYxKbAaW9SFBF6HcIw?si=IM1jk9Q9h2wUi2YQ
I believe this is an example.
Why should a player who is actively skating into their own goalie and moving their player further into the goal crease come up with an interception here?
Had the player taken the proper positioning and A) allowed his goalie to move and B) been better positioned in the passing lane.. the puck would've either been intercepted, or the goalie makes the save.
@jimmo52 wrote:
@KidShowtime1867So, for a manually played defender and have that interception, you need to be exactly in the passing lane and to stay still?
No. Staying still is NOT what you should be doing. Feathering the left stick to keep your player active while ensuring your stick is in the passing lane and facing the potential incoming pass is what should be done.
Many people are frantically skating their defenders with 100% urgency in any given moment. This lowers the success rate of automated defence actions, such as an interceptions. I keep harping on it.. but people need to slow down. Feather the left stick more and you'll see FAR more success on both offence and defence.
Again this example from NoSleeves who claims this pass should've been intercepted. The Boston player is actively skating his player directly into his goalie when he should've been feathering outward toward the top of the crease (with vision control held to face the puck carrier) or tie up the dangerous player
@KidShowtime1867 Again, I understand all the tips that you gave out.
But in the end, isn't true that it's better to leave the defender between a cross crease as a cpu for the higher chances of interception. It's a legit question, not questioning your expertise or anything. Problem with online games is that with delays, it is not easy to feather the left stick as you will see a delay in the movement of your defender. And forget about having delays or not, with cpu having the control, even without perfectly in the passing lane, it does intercept, right?
For real, I truly want to manually control my defender that is between a cross crease but if the advantage is higher with the cpu, why not let the cpu take control of that kind of situation?
@jimmo52 wrote:@KidShowtime1867 Again, I understand all the tips that you gave out.
But in the end, isn't true that it's better to leave the defender between a cross crease as a cpu for the higher chances of interception.
I would say that a CPU defender on a 2-on-1 is a gamble. The A.I. is unpredictable sometimes - especially when it comes to defensive coverage.
I'd much prefer taking control of that defender. I'm very confident when I'm defending 2-on-1's because I've had a lot of success in finding passing lanes, feathering my skating and ensuring the probability that i disrupt the play is high.... but it's NEVER guaranteed.
Passes will seemingly go 'through' me from time to time, only for me to assess things afterwords and notice where I screwed up. In the moment, I'm angry and thinking 'man.. this f'ing game sometimes...' but more often than not, if a pass has gone 'through' me, it's a mistake I made.
@jimmo52 wrote:@KidShowtime1867 Again, I understand all the tips that you gave out.
Problem with online games is that with delays, it is not easy to feather the left stick as you will see a delay in the movement of your defender.
In a peer-to-peer situation, such as Online Versus Play, the delay you are experiencing will also be experienced by your opponent. That's just kinda the nature of p2p connections.
In a client-server scenario (such as HUT/WoC) - there's definitely a chance that your movements are delayed. That's why it's important to take note of your ping. Anything above 50ms is going to result in you adjusting your gameplay to more of an anticipatory type of playstyle, which can be incredibly frustrating but is playable.
I don't deny that latency plays a role in what we perceive should've happened versus the outcomes we encounter. It would be awesome if the 'netcode' was streamlined to improve connection quality and lower latency. I'm no expert in that particular field though so I wouldn't even know where to begin to analyze potential changes/solutions there.
