Many people probably thought that the Richmond Spiders should not have any problems with James Madison tonight, but they did. It took overtime for the Spiders to defeat the Dukes by one point, with a final score of 83-82.
This game was so competitive and high-scoring because both teams shot tremendously. Richmond shot 57.8 percent from the field and 64.7 percent from the three point line. That’s unheard of in a game; you would think if the Spiders shot that well then they should have won this game easily but JMU shot well too.
The Dukes shot 52.1 percent from the field and 61.5 percent from the three point line. The ex factor in tonight’s game was Richmond’s starting lineup compared to JMU’s.
The Spiders had four out of five players in double figures while the Dukes only had two players. Spiders junior guard Cedrick Lindsay had the biggest impact in the game posting a double-double consisting of 13 points and 11 assists. Lindsay also hit a pair of free throws at the end of the regulation to go into overtime.
Also you cannot forget about junior forward Derrick Williams who had an impressive 17 points and 7 rebounds in today’s game for Richmond. Richmond’s record is now 8-2 on the season and they have a challenge coming up that will definitely test them.
On December 15th, they come back home and take on Stetson (Atlantic Sun) which should be a cake walk but three days later comes the test.
On December 18th, the Spiders will travel out to Kansas to take on the ninth ranked team in the country, the Kansas University Jayhawks at 7:00 pm. If I’m Richmond you need to put away Stetson quickly so you can rest your players with Kansas coming up a few days later.
Jovan Alford is a staff writer for The Sixer Sense, a writer for Buzz On Broad covering the Philadelphia 76ers and Local College Basketball, and is a writer for Rant Sports covering the A-10 Conference for College Basketball.
Follow me on twitter @Jovan10 for Sixers, College Basketball, NFL, MLB, and all sports updates.
For any inquiries contact me via email: email@example.com