Star Wars: The Acolyte Episode 3: Why Does Mae Try to Kill Osha?
Image Credit: Disney Plus

Star Wars: The Acolyte Episode 3: Why Does Mae Try to Kill Osha?

Star Wars: The Acolyte fans who saw Episode 3 are asking why Mae tried to kill Osha. Despite being twin sisters raised by their mothers Aniseya and Koril at the Force-witches coven, Mae and Osha had diverse upbringings growing up. Osha trained in the ways of the Jedi under Master Sol, while Mae succumbed to the dark side and began serving a mysterious evil master.

But, why did Mae start the fire in The Acolyte? Why did she attempt to kill Osha? Here is your answer.

Why did Mae start the fire in Star Wars: The Acolyte Episode 3?

When Mae learned that Osha wanted to leave her and the Force-witches coven to become a Jedi, she threatened to kill her. Mae then took her book, locked Osha in their bedroom, set the notebook ablaze, and started a fire in front of the door to prevent her departure.

However, the wall lamp that served as the source for the fire Mae started outside their bedroom seemed to be only capable of covering one small area due to its miniature size. Apparently, it could not have caused the ultimate fiery destruction that claimed the lives of Mother Aniseya and the rest of the coven.

Disney+ Has the Best Bundle in the Business

Sign-up today for access to Disney+, Hulu, and ESPN+

Thus, it is possible that Mae did not cause the entire fire and that someone else was responsible, contrary to Master Sol’s claim that it was Mae who did it.

Perhaps Aniseya or Koril had something to do with the destruction. Episode 3 revealed that not all witches were in agreement with letting Osha join the Jedi, more specifically Koril and Aniseya. They disagreed with each other on letting Osha leave, with Aniseya supporting Osha’s decision and Koril being against it. This is supported by how Aniseya was found lying dead in a separate room from the rest of the witches, all of whom were discovered dead in one room. However, Aniseya and Koril are mere suspects and the true culprit is not yet known.

Movie News
Marvel and DC
X