What's the opinion on cut block as an SA? I have a pass blocking OT on a team where he is a little under-leveled. I'm wondering if buying him some equipment with a cut blocking bonus would help him on running plays. I'm not putting SPs into that tree anytime soon, so it would only be the equipment bonus. Is that just a waste of tokens and an equip spot long-term, or does it have potential?
mandyross
offline
offline
Originally posted by Bronko Grange
a waste of tokens and an equip spot long-term
I vote this.
For a pass blocking OT, assuming he is a LOT, there should be 2 equipment pieces in hold block % and 1 in protect immediately. I'd work on those ones first as they should help him out the most short-term, and will be pieces for the long-term also.
As for running plays, after HB% I'd prefer to have the Run Block SA close to 10 and nothing else in the tree. At any rate, I'd prefer Get Low over Cut Block, even if it is penalised.
a waste of tokens and an equip spot long-term
I vote this.
For a pass blocking OT, assuming he is a LOT, there should be 2 equipment pieces in hold block % and 1 in protect immediately. I'd work on those ones first as they should help him out the most short-term, and will be pieces for the long-term also.
As for running plays, after HB% I'd prefer to have the Run Block SA close to 10 and nothing else in the tree. At any rate, I'd prefer Get Low over Cut Block, even if it is penalised.
Preschooler05
offline
offline
Originally posted by mandyross
Originally posted by Bronko Grange
a waste of tokens and an equip spot long-term
I vote this.
For a pass blocking OT, assuming he is a LOT, there should be 2 equipment pieces in hold block % and 1 in protect immediately. I'd work on those ones first as they should help him out the most short-term, and will be pieces for the long-term also.
As for running plays, after HB% I'd prefer to have the Run Block SA close to 10 and nothing else in the tree. At any rate, I'd prefer Get Low over Cut Block, even if it is penalised.
This. Cut Block would be way down my list of choices for AEQ. If you want to invest in the run block tree, go with Get Low later on after your other AEQ is in place.
Originally posted by Bronko Grange
a waste of tokens and an equip spot long-term
I vote this.
For a pass blocking OT, assuming he is a LOT, there should be 2 equipment pieces in hold block % and 1 in protect immediately. I'd work on those ones first as they should help him out the most short-term, and will be pieces for the long-term also.
As for running plays, after HB% I'd prefer to have the Run Block SA close to 10 and nothing else in the tree. At any rate, I'd prefer Get Low over Cut Block, even if it is penalised.
This. Cut Block would be way down my list of choices for AEQ. If you want to invest in the run block tree, go with Get Low later on after your other AEQ is in place.
RisingChaos
offline
offline
Honestly, I kinda wonder how many revcakes are actually just failed cut blocks and how much pumping the SA would help knock the other guy over along with you.
Preschooler05
offline
offline
Originally posted by RisingChaos
Honestly, I kinda wonder how many revcakes are actually just failed cut blocks and how much pumping the SA would help knock the other guy over along with you.
Possibly. I don't know if I would try to encourage my dots to attempt more cut blocks though.
If someone has had a good experience with Cut Block, I would be interested to see some plays.
Honestly, I kinda wonder how many revcakes are actually just failed cut blocks and how much pumping the SA would help knock the other guy over along with you.
Possibly. I don't know if I would try to encourage my dots to attempt more cut blocks though.
If someone has had a good experience with Cut Block, I would be interested to see some plays.ericb45696
offline
offline
I have it on2 of my mid lvl guards that already have a few other pieces of AEQ and like it. I wouldn't get it unless you already had a get low and hold block% piece already though at least.
You are not logged in. Please log in if you want to post a reply.
