Raptors' gutting loss to Hornets just reinforced Scottie Barnes' key status

Too much Brandon Ingram, too little Scottie Barnes...
Toronto Raptors v Charlotte Hornets
Toronto Raptors v Charlotte Hornets | Katie DeVaney/GettyImages

I won't exactly let one game flip the script about Brandon Ingram or the hot Raptors winning streak lose its luster in my eyes, but even with a sound mind, there was absolutely no excuse for Toronto's key defeat to the Charlotte Hornets on November 29. While Toronto's winning streak was never going to last forever, the way they lost and the circumstances surrounding it, served as a stern wake-up call on how the team should operate in high-stakes matchups, especially if the Raptors want to return to the playoffs and be looked at as a viable threat.

While the Brandon Ingram experience has been relatively pleasant thus far, he had a extremely rough night against Charlotte. Despite this, the ball was too often in BI's hands down the stretch when he simply could not buy a basket. I recognize BI’s scoring talent and his standout moments this season, including a recent game-winner, but what truly fueled the team's success was unselfishness, cohesive team play, and balanced contributions. In fact, that aforementioned Pacers game should've been theirs to lose, and yet, they fought through adversity and pulled out with a win.

Knueppel's game-tying three late in the fourth was a massive defensive lapse by Ingram, who simply stood there with very little shot contest, and he couldn't easily replicate his Pacers game-winner on the next possession. Of course, some factors in the Hornets game were out of Toronto’s control — bench struggles, critical mistakes/oversights, and late turnovers — but relying on Ingram playing hero ball was not the answer.

Sometimes hard shots don’t go in, and that’s where the Raptors forgot their star Scottie Barnes was right there; it hurt even more when Barnes passed up the final regulation shot to Brandon Ingram, knowing the Hornets’ defense was ready and forcing him into an extremely tough attempt.

Overlooking Scottie Barnes hurt Raptors in the closing moments vs. Hornets

This isn’t just a one-man show. While Ingram was brought in to provide the Raptors with an offensive versatility they haven't seen in years, discussions about Toronto’s roster have always centered on their depth. Before RJ Barrett’s injury, the star trio of Barrett, Barnes, and Ingram was the only group from the same NBA team to each score 20 or more points, highlighting the talent spread across all five starting spots.

On this night, Scottie Barnes was in full control, delivering an impressive 30 points on 11-for-16 shooting, 7-for-8 from the free-throw line, along with 12 rebounds, five assists, two steals, and a block. It was his night to shine, but for reasons unknown, Ingram and Quickley took more shots than Barnes, who was clearly in his element.

Again, I’m not criticizing Ingram or Quickley for their ability to score — they’re some of our most clutch shooters, arguably the best in that regard. However, with all due respect, they can’t become "ball hogs" either. This game tested our team’s cohesive flow and chemistry, and it’s clear that such issues involve both players and coaching — probably more on the coaching side. We can’t always dwell on "what ifs," but the signs were obvious, especially with Rajakovic on the sideline.

Why not experiment with more plays for Scottie Barnes down the stretch? After all, Barnes was responsible for five of the Raptors' seven points scored in OT.

He had the best game by a mile, and anyone paying attention could see that. Many would agree that he remains, without question, the Raptors’ "best" player (and most likely All-Star). Toronto can't afford to get sloppy like that at the end of big games, especially with some tough foes in their crossfires, like the Knicks, Lakers, and Heat. Scottie Barnes should never take the backseat when he's thriving like he did against the Hornets, and hopefully this avoidable loss becomes a wake-up call for everyone involved.

Loading recommendations... Please wait while we load personalized content recommendations