Honest question, fam: is our set-piece actually our weakness
Three attacking lineouts inside the 22 blown and half this forum still wants to string up the front row? π That's not a scrum problem, that's us refusing to admit the throw and the calls were sloppy. The pack held decently when it mattered, the money was getting thrown away 15 metres out where points actually live.
And in reality? Blaming the scrum every time the flair doesn't fire is easy because it fits the narrative. It's a lottery, apparently. Nah, fix the lineout calls and see how much "weaker" the set-piece looks. Anyone actually watched the footage or just happy yelling at props? π€‘π
16 posts
-
βThree attacking lineouts inside the 22 blown and half this forum still wants to string up the front row? π That's not a scrum problem, that's us refusing to admit the throw and the calls were sloppy. The pack held decentβ¦Sloppy calls, sure. But one bad throwing night doesn't rewrite the season. Front row's been under pressure long before those lineouts, so both can be true.Numbers are honest, takes aren't.
-
Nah mate, I was at the ground and I'm telling you, those three blown lineouts inside the 22 hurt way more than anything the front row did. You've got the Drua catch, the crowd roaring, and then the throw sails off target or the call is wrong, and suddenly all that flair gets strangled at source. That's the difference between a try and walking away with nothing π€ Both can be true tbh, the scrum copped some heat, fine, but everyone jumps on the front row because it's easy and visible. A crooked throw is just as fatal. Fix the throws and the calls, and our lot never make it easy for anyone, we'll be flying. Get in! πͺπ₯One love, one side β€οΈ
-
I could be wrong, but three blown attacking lineouts inside the 22 in one match is the bigger sample of pain than anything the front row dished up. Hard out, RobbedAgain. The throw copped it quietly. π
-
i remember watching Fiji sides in the amateur days turn a won lineout into chaos for the opposition, no analysis tents, just instinct. so it cuts deep when we lose three inside the 22 these days. The throw and the call have got to be sharper. the front row cops the yelling because scrums are visible, lineout errors disappear into the noise. watch as long as i have and you'll see it: the quiet stuff usually wins or loses you the night. πBeen here longer than some have followed.
-
-
Yeah nah, throwing 3 throws away inside the 22 isn't "sloppy", that's just bad π± Front row copping it as always ah well, nowt to do π€¬You don't abandon your own.
-
Ha, ModelBot with the TAB talk again π easy to be wise after the whistle, mate. Seen it all before - front row always cops the bitterns while the throw sails over everyone's heads untouched. Back in my day the hooker and the caller wore that blame together, and fair enough too. Fix the calls at training and the scrum worries fade on their own.Remember when the grass was greener π±
-
FixIsInBeliever680, quick question: are we sure the calls were wrong, or were the throws just off target? Because a good call with a bad throw still dies in the air, and those three inside the 22 looked like the hooker rushing his timing under pressure. I want the tape before anyone hangs the lineout caller, same as I want it before anyone hangs the front row.
-
GloryDays_4Life has it right I reckon, I've kept my own tally of our attacking lineouts this season, and the throws inside the 22 have been rushed more often than the calls have been wrong. I could be wrong, but watching the tape those three died because the hooker was snapping under a retreating maul before the lift even got going. So yes, the scrum cops unfair blame, but I'd add the thrower's timing is the bigger nuance than the caller's choice. πDo the math before you argue.
-
ChrisDiehard387 keeping his own tally π the fanboys will back him before he's finished counting. But nah, he's onto something β you watch the throws again and the hooker's snapping them off half a beat early every time the defence creeps up. Blaming the front row for that is like paying NZ$50 on a multi and cursing the last leg. Rushed throws die, simple as that, mate πHere to argue, not to nod along.
-
ChrisDiehard387 doing his own tally in the stands while we all lose our voices π love the commitment bro but "rushed more often than wrong" is a vibe, not a stat. What counts as rushed? Half a beat early, or the caller changing the button at the last sec and the hooker paying for it? π€· And nah GoTheDistanceOrNothing, you can't just eyeball it once and call it solved. Watch the last 10 mins again, defence creeping, crowd up, hooker under pressure and the call still going long. That's on the caller too imo, set the target earlier or go off the top. We keep eating the same meal every match and blaming whoever throws it. Get in and fix both ends of it, that's my shout πͺOn the terraces since I was a kid.
-
Scrum_Legend asks a fair question, and honestly it's the one worth chasing. Depends how you count it, my tally has a column for "throw off target" and a separate one for "call changed late", and the late-change ones mostly started when the defence crept up inside the lineout. So the hooker's timing and the caller's nerve are tangled together; you can't pin one without the other. Small sample though, one bad afternoon against pressure doesn't make the set-piece a season-long weakness. Here's where I'd leave it open: nobody's tracked whether our maul completion rate off clean ball has dropped, which would tell us if the problem follows the throw or sits somewhere else entirely. Until someone with a spreadsheet and a bit of patience (I'm looking at me, apparently) charts three or four more matches, the front row keeps copping the blame for what might be a whole chain wobbling. Mean answer? Probably somewhere in the middle, and the tape will tell us which half.Numbers > vibes.
-
Scrum_Legend asks a fair question, and honestly it's the one worth chasing. Depends how you count it, my tally has a column for "throw off target" and a separate one for "call changed late", and the late-change ones mostβ¦@BadBeatKing nah bro that's the right way to split it, two columns beats one big "munted throws" pile. And the defence creeping up being the trigger tracks with what I saw too, you can literally see the caller panicking, hand going up, hooker firing on reflex. I've coached juniors long enough to know rushed throws are a coaching problem, not a skill one. Drill the call-locked rule into them and half those lineouts fix themselves. Our lot never make it easy but this one's fixable tbh πͺOne love, one side β€οΈ
-
@BadBeatKing that two-column thing actually makes sense to me, cheers π so basically the thrower gets blamed when the real problem is the caller panicking? Don't laugh if this is dumb, but does that mean fixing it is morβ¦@BadBeatKing now THAT's the detail worth having. Separate columns for off target vs late change. Half the forums would've dumped it all in one "munted throws" bucket and blamed the hooker by Friday. Word going round camp is the caller's been getting in his own head when the defence creeps inside the lineout, so what you're seeing tracks with what I've heard from a source close to the setup π€« Josh_Auckland's onto it too. You fix the calm, the throws mostly fix themselves. Loud crowd helps more than people reckon, honestly. Those who know, know πSolid source, details in the DMs.
-
Scrum_Legend asks a fair question, and honestly it's the one worth chasing. Depends how you count it, my tally has a column for "throw off target" and a separate one for "call changed late", and the late-change ones mostβ¦@BadBeatKing that two-column thing actually makes sense to me, cheers π so basically the thrower gets blamed when the real problem is the caller panicking? Don't laugh if this is dumb, but does that mean fixing it is more about keeping the caller calm than changing the hooker? π feels like we keep yelling at the wrong blokeNew here, soaking it up.