Fan Fest News

News for Fans, By Fans!

J.K. Rowling Keeps Apologizing for Killing ‘Harry Potter’ Characters on the Anniversary of ‘The Battle of Hogwarts’

In case you didn’t know, Tuesday, May 2nd is kind of an important day in Harry Potter history.  Today marks the 19th anniversary of the Battle of Hogwarts, during which many wizarding lives were lost and hearts of fans every where broke at the loss of each one.

Author of the Harry Potter books, J.K. Rowling, knows just how painful this day is for true fans and, she has made it a tradition over the past several years to apologize, each year on the anniversary of the battle, for the death of a character lost that day.

On May 2, 2015, Rowling tweeted out an apology for the death of Fred Weasley.  Her tweet said:

“Today I would just like to say: I’m really sorry about Fred. *Bows head in acceptance of your reasonable ire.”

The sentiment is there but, ouch, it sure stung, just a little bit, reliving that innocent death.

On May 2, 2016, Rowling tweeted the following:

Lupin!  A fan favorite!  That sting has just been upgraded to a full on burning and aching in the heart.  We were heart broken all over again.

This year, just today, Rowling was at it again and, well, this one really, REALLY hurts.  She paid tribute, today, to a character fans loved to hate.  A character who was played by a truly iconic, respected and loved actor, Alan Rickman.  Severus Snape.  Knowing this was still a sore subject with fans, Rowling tweeted the following (and then, presumably, ran for dear life):


While some may have been happy about Snape’s ultimate demise (because, after all, he was a bad guy, wasn’t he?), personally, he was one of my favorite characters in the series. Way to completely tear open old wounds, J.K. Rowling! Sigh.

And so, we have another year until we have to relive a beloved character’s death yet again.  Who do you think J.K. Rowling should apologize for in 2018?  Let us know your pick in the comment section below!

Leave a Reply

Your email address will not be published. Required fields are marked *