A scary fairy tale

Very bad problem description.

Good idea to use storytelling for explaining why and when to use abstract classes. But the tasks need some specification. Without a proper tasklist, you need luck to get your solution validated.

the wolf ate a little --> does putting this in serve a purpose? is CG trying to teach us not to get fooled?

It changed one of the few found memories I had from when I was a kid.

So, the logic behind this exercise (in the beginning I did not like it at all but ended up understanding and liking) is to realise that the abstract class StoryItem is the main class for all of the characters (subclasses) from the story, ergo, all of the other characters will have these arraylists. After a bit of research about the story and finding out that wolf ate grandma and hood and was killed (in some versions at least lol) by the woodcutter, I had to translate this storyline in the logic of the problem. So, if each character has an arraylist of killed and ate whom do we add where ? Well, the wolf ate the grandma and the hood. We in main, we have to add grandma and hood to wolf's ate arraylist. And the wolf was killed by the woodcutter so we have to add the wolf to the woodcutter's killed arraylist. The end. :)

unexpectedly, the wolf ate the hood too :)

Real pointless challenge. How is anyone supposed to figure out what wolf ate a little means without going through the comments and help section?

ignore pie use killed, ate correctly

Clarifying poorly written conditions: wolf ate grandmother wolf ate hood woodcutter killed wolf. Ignore the nonsense about the pie.

This task is confusing. Please specify what "wolf ate a little" means. Because you can't understand that a little means both hood and grandmother. Also in the story wolf never eats red riding hood!