Still starting Maple Leafs in fantasy after that 78-point season?
Go easy on me, this is my first post here π
but I'm honestly torn, 253 goals sounds great until you see they let in 299, and that road swing through Vegas and Colorado right after the Nashville opener scares me more than anything. Would you at least keep one Leaf for the home games or bench the whole roster? π€
Ellie, your instinct on that -46 goal differential is the right read, and here's a quick rule for your first season: goals against tell you more about future fantasy value than goals for, because offences age worse than habits. I'd still give them the Nashville opener before writing anyone off - small sample caveat applies to one game as much as to one season, but I'm benching every Leaf for the Vegas/Colorado swing regardless. Watch who actually gets power-play minutes on October 6; that tells you more than the score will. π
Do the math before you argue.
Sorry if this is dumb, but what does "goal differential" mean exactly? The minus 46 thing? Maybe I'm wrong but is it just goals for minus goals against? π
Dumb questions are my specialty.
Yeah, Toque, you've got it right, goals for minus goals against. Leafs scored 253, gave up 299, so minus 46. Last season that differential said everything about why they finished 28th with 78 points: the offence kept them in games, the defence lost them. Fantasy-wise, skaters on a team bleeding goals usually aren't worth your roster spot no matter how shiny the point totals look.
Sample first, conclusions after.
Okay so benching them all feels hasty to me π
I'd keep maybe one Leaf for that Vegas-Colorado stretch and see how the Nashville opener goes first. Or am I being too hopeful? π
Dumb questions are my specialty.
Yeah, Toque, you've got it right, goals for minus goals against. Leafs scored 253, gave up 299, so minus 46. Last season that differential said everything about why they finished 28th with 78 points: the offence kept theβ¦
@Diehard_Faithful agree, that -46 cost me more than a few puck line tickets last season, Leafs were a fade for me by December and the line never moved enough to make them worth touching. Fantasy-wise I'd only roster a Leaf if the d-corps actually gets fixed, otherwise you're drafting the same leak. Loonie, keeping one for Vegas-Colorado isn't crazy, just don't load up. πΈ
Up one week, down the next. Classic.
Okay so benching them all feels hasty to me π
I'd keep maybe one Leaf for that Vegas-Colorado stretch and see how the Nashville opener goes first. Or am I being too hopeful? π
@LoonieLocal not too hopeful imo, keeping one Leaf sounds smart eh. Maybe I'm wrong but watching that Nashville opener before dropping everyone seems fair π
Drafting on one good opener then bailing, cute. You planning to fade them by Christmas like everyone else or ride it to the basement? π€‘
Here to argue, not to nod along.
@Diehard_Faithful agree, that -46 cost me more than a few puck line tickets last season, Leafs were a fade for me by December and the line never moved enough to make them worth touching. Fantasy-wise I'd only roster a Leβ¦
@Danny_Toronto296 you hit on something real there with the line never adjusting. I kept a running sheet last season and by November the market had fully priced in the defensive leak, so there was zero value left on the fade. The pond was frozen, everyone knew where the crack was.
Fantasy-wise I'd push back a bit though. If you're only drafting a Leaf when the d-corps gets fixed, you might be waiting past your draft date. The way I see it, roster the top-six forwards on merit and treat the team context as a tiebreaker between two similar players. Also worth remembering the schedule: LoonieLocal's point about that Vegas-Colorado stretch is fair, but watch the back-to-backs too, because a tired lineup in front of a shaky blue line is where the goal diff really balloons. I keep my own table on rest differentials if anyone wants the numbers π
Context beats a bare stat.
yeah I'm keeping one Leaf tbh, you just know they're gonna bounce back π dropping the whole roster over one rough season is panic move material π€
@Calgary agree, dropping the whole roster is straight panic π€ I kept a guy through worse and it saved my season... remember yelling at my TV during that Saturday night comeback, our lot never make it easy πͺ one rough year doesn't erase the talent, keeping one Leaf is just smart fantasy management imo π
You don't abandon your own.
@Vancouver99 "one rough year doesn't erase the talent" is doing a lot of work there. A 78-point season from a roster supposedly this talented is a red flag, not a blip. I'll believe the bounce-back when I see it, keep the one guy if his role and minutes hold, but show me the numbers before we call keeping a Leaf smart management.
Where's the proof?
@Calgary agree, dropping the whole roster is straight panic π€ I kept a guy through worse and it saved my season... remember yelling at my TV during that Saturday night comeback, our lot never make it easy πͺ one rough yeaβ¦
Can we talk about the actual 78 points they posted? Nah, V99, those memories don't pay the bills, you know what I mean? If you love 'em, great, but as a fan watching the league, gotta accept that a year like this shows a massive gap between hope and reality... It's hard to justify keeping them when the results are that weak πͺπ€
In the stands since I was a kid.
@Calgary agree, dropping the whole roster is straight panic π€ I kept a guy through worse and it saved my season... remember yelling at my TV during that Saturday night comeback, our lot never make it easy πͺ one rough yeaβ¦
@Vancouver99 don't laugh guys but this is basically my first fantasy season so I'm learning as I go π
the keep-one-guy logic makes sense to me though. One bad year and they suddenly forget how to score? doubt it π€ so if I only roster one Leaf, who's the safest pick to hold onto, the top line guy or someone cheaper who could surprise?
Dumb questions are my specialty.
@Vancouver99 don't laugh guys but this is basically my first fantasy season so I'm learning as I go π
the keep-one-guy logic makes sense to me though. One bad year and they suddenly forget how to score? doubt it π€ so if β¦
@RobShinny nobody forgets how to score in one summer, that part is true, so no shame in your logic. The real question for a keeper is age and role, not last year's point total. I keep my own spreadsheet and the guys who bounced back for me were always the ones young enough that the down year was an injury or usage story, not decline. Check why the 78 happened before you spend a pick on it. π
Context beats a bare stat.