Hornets Make LaMelo Ball Announcement After Clippers Game

Originally posted on Athlon Sports | By Garret Schnitker | Last updated Mar 17, 2025 7:22 PM ET

LaMelo Ball and the Charlotte Hornets fell 123-88 on Sunday against the Los Angeles Clippers in the Intuit Dome. Charlotte was led by an outstanding performance by Mark Williams who contributed 18 points 15 rebounds, and seven assists.

After Ball was deemed an “All-Star snub” by some in the media, he has struggled to find that offensive rhythm again since the break. Before All-Star weekend, Ball was averaging 27.3 points per game on 41.6% shooting in 33 games (via NBA). Since then, the former No. 3 pick in the draft out of the NBL in Australia is averaging just 19.5 points on 34.7% shooting in 11 games (via StatMuse).

While Ball has been dealing with a nagging ankle injury consistently this season, news arose circulating a new injury.

The Charlotte Hornets released the injury report ahead of their matchup with the Brooklyn Nets, which included Ball but listed him as probable due to right wrist soreness.

LaMelo Ball is on the injury report for tomorrow's #Hornets home game with right wrist soreness, but he's listed as probable.
— Nick Carboni (@NickCarboniWCNC) March 17, 2025

Charlotte is amid one of the worst seasons it has ever experienced; their .254% winning percentage would stand as the fifth-worst in franchise history (Charlotte Hornets/Bobcats) via Basketball Reference. Charlotte currently ranks 14th in the Eastern Conference and possesses the third-worst overall record in the league, which would put the franchise in a tie for the highest percentage for the No. 1 pick in the NBA draft lottery.

The position of the Hornets has made rival general managers begin to wonder if Ball will be available for trade by the offseason (via NBACentral). However, Charlotte has made it clear to other franchises that they have no plans to move the 23-year-old former All-Star guard (via HoopsHype).

This article first appeared on Athlon Sports and was syndicated with permission.

More must-reads: