Follow TV Tropes

Following

History Funny / TheMatrixReloaded

Go To

OR

Is there an issue? Send a MessageReason:
None


* An unintentional example: when Neo meets the Architect, the former asks: "Why am I here?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquaciousness makes his explanations difficult to follow, their exchange comes off as hilarious:

to:

* An unintentional example: when Neo meets the Architect, the former asks: "Why am I here?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquaciousness makes his explanations difficult to follow, their exchange Neo's response comes off as hilarious:hilarious bewilderment:



--> '''Neo''': [[DeadpanSnarker "You haven't answered my question."]]

to:

--> '''Neo''': [[DeadpanSnarker [[FlatWhat "You haven't answered my question."]]
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* This exchange between Persephone and the Merovingian.
-->'''Persephone:''' Where are you going?\\
'''Merovingian:''' Please, ma cherie, I have told you. We are all victims of causality. I drank too much wine, I must take a piss.
Is there an issue? Send a MessageReason:
None


* An unintentional example: when Neo meets the Architect, the former asks: "Why am I hear?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquaciousness makes his explanations difficult to follow, their exchange comes off as hilarious:

to:

* An unintentional example: when Neo meets the Architect, the former asks: "Why am I hear?," here?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquaciousness makes his explanations difficult to follow, their exchange comes off as hilarious:
Is there an issue? Send a MessageReason:
None


* An unintentional example: when Neo meets the Architect, the former asks: "Why am I hear?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquacious makes his explanations difficult to follow, their exchange comes off as hilarious:

to:

* An unintentional example: when Neo meets the Architect, the former asks: "Why am I hear?," to which the Architect explains that Neo is a recurring anomaly in the programming of the Matrix, whose code results in him meeting the Architect every several generations. In other words: the Architect explains ''what'' Neo is and ''how'' they came to meet; but not ''why'' they are meeting. However, because the Architect's SesquipedalianLoquacious SesquipedalianLoquaciousness makes his explanations difficult to follow, their exchange comes off as hilarious:

Top