![NieR:Automata Ver1.1a: hun[G]ry for knowledge poster](https://image.tmdb.org/t/p/w780/xYB232tNF2dv6hD9fYdoRkok9aC.jpg)
Episode
NieR:Automata Ver1.1a: hun[G]ry for knowledge
Overview
▶▶ Pod 153 - Report: Communication lost with 9S, the individual of this unit’s accompanying support. While acting alone, 9S encountered a unit appearing to be ＜A2＞ in an abandoned building located in the Flooded City and began pursuit. Strong jamming signal emission confirmed throughout the area at the time. Hypothesis: 9S fell into an untraceable status while trying to restore communications. Proposal: Call 2B for assistance and begin searching.
Details
- Series
- NieR:Automata Ver1.1a
- Season
- Season 1
- Episode
- Episode 9
- Air date
- 2023-07-23
- Runtime
- 24 min
Episode context
hun[G]ry for knowledge is Episode 9 in Season 1 of NieR:Automata Ver1.1a. It aired on 2023-07-23. The runtime is 24 min.
Previous / Next
Episode 8: aji wo [K]utta ?
▶▶ Pod 042 - Report:
In the Forest Kingdom area, wanted YoRHa unit identified as ＜A2＞ was discovered.
The fugitive unit in question abandoned her mission and continues to run away to this day. She is designated as a highly dangerous individual.
Units 2B and 9S receive orders to track and investigate A2 from Command.
Proposal: Contact the Resistance and Pascal to begin collecting information.
Episode 10: over[Z]ealous
▶▶ Pod 042 - Report:
YoRHa Unit 2B has successfully defeated the abnormal machine lifeform identified as ＜Eve＞.
Hypothesis: Machine lifeforms in the region will gradually weaken due to the loss of Eve, the core of the machine network.
9S returns to the Bunker for body repairs and data overhaul.
Hereafter, until the completion of 9S’s repairs, 2B—together with this unit and Pod 153—will carry out the order to destroy ＜Adam＞ assigned by Command.
More episodes from this season
Episode 7: [Q]uestionable actions
▶▶ Pod 153 - Report:
In the mission so far, this unit has encountered many abnormal machine lifeforms – some of which have even progressed as far as engaging in combat.
Each individual’s information has been uploaded to the server as designed.
Proposal: In preparation for future encounters, request information analysis and sharing of results in the Bunker.
―――Entity Identification Signal: ＜Pascal＞ response confirmed―――
A member of a machine lifeform village appears to have gone missing.
Proposal: Begin reconnaissance in the Forest Kingdom area.
Episode 11: head[Y] battle
▶▶ Pod 153 - Report:
Construction of new machine lifeform network confirmed. Hypothesis: The entity ＜Adam＞ is presumed to be the core.
A Goliath-class machine lifeform has begun a hostile rampage during the search for Adam. Analysis: The same phenomenon has been confirmed simultaneously in various regions on the ground. Command has issued an order for all YoRHa Soldiers to intercept the enemy machine lifeforms.
Many YoRHa Soldiers and Resistance members are currently reporting engagements with hostiles and requesting assistance.
Proposal: Commence operation for Resistance Camp rescue with 2B.
Episode 6: [L]one wolf
▶▶ Pod 042 and Pod 153 - Joint Report:
Data discovered. Presumed to be part of a record from the past.
Transferring to shared server.
___________________________________________________________________________________________________________
December 8, 11941.
I’ve encountered androids dispatched to Earth on a top-secret mission.
These unknown androids call themselves ＜YoRHa Soldiers＞.
Command that abandoned us. YoRHa Soldiers with nothing but secrets and full of mysteries.
But you can’t protect your family if all you do is doubt.
…I hope my choice, our battle, will be a breakthrough in this long war of attrition.
_____________________________________________________________________________________________
Episode 12: flowers for m[A]chine
▶▶ Pod 042 and Pod 153 - Joint Report:
Pod 042 Report: The rampant entity ＜Adam＞ was hacked by 9S, intercepted by the Resistance, and was bombarded with support fire from the Bunker. It was ■■■■
―――Communication error―――
―――Communication error―――
―――Communication with Pod 042 is being restored 12 seconds until restoration―――
―――Communication with Pod 153 is being restored 15 seconds until restoration―――
Pod 042 to Pod 153: Temporary communication error occurred due to large-scale ground and air attacks. Currently undergoing restoration processes.
Pod 153 to Pod 042: Same failure for this unit confirmed. No abnormalities in recording systems.
Pod 042 to Pod 153: Agreed. Currently, there are no system abnormalities in this unit. Continuing to carry out investigation mission and recording of 2B, target of this unit’s accompanying support.
Pod 153 to Pod 042: Agreed. This unit will also carry out missions and record 9S.
Episode 5: mave[R]ick
▶▶ Pod 042 - Report:
Verifying the trade information between the Resistance and machine lifeforms in the City Ruins.
Despite the hostile relationship between androids and machine lifeforms, it appears the machine lifeforms they are trading with hold no hostile responses or combat intentions.
This unit will investigate the area together with 2B and 9S, who Lily requested to transport materials to the machine lifeforms.
Episode 13: reckless bra[V]ery
▶▶ Pod 042 - Report:
5012 AD.
Lifeforms from outer space, otherwise known as ＜Aliens＞, suddenly begin their invasion of Earth. Mankind escapes to the moon, and the ground battle between the ＜Androids＞ and the ＜Machine Lifeforms＞ has continued for a long time.
11945 AD.
The ＜243rd Descent Operation＞ has commenced.
＜YoHRa＞ Soldiers ＜2B＞ and ＜9S＞ now engage in the plan to recapture Earth.
While on a mission near the City Ruins, they receive a request from the Resistance to find a missing android. Both 2B and 9S consider that the missing android may be related to their current investigation ordered by Command. Proposal: Begin the search for relevant android.
Episode 4: a mountain too [H]igh
▶▶ Pod 153 - Report:
During the investigation in the Desert Zone, several unique entities not found in previously recorded data were confirmed. Entities confirmed were characterized as “machine lifeforms capable of speech” and “machine lifeforms that closely resemble androids”. Details uploaded to the server.
In addition, both units 2B and 9S received orders from Command to search for YoRHa Soldiers.
It appears that contact has been lost with the missing unit during their ground mission.
Origin of black box signal has been detected. Proposal: Begin search for the target at the corresponding point.
Episode 14: mission [F]ailed
▶▶ Pod 153 - Report:
YoHRa Soldiers 2B and 9S both succeed in destroying machine lifeform core units ＜Adam＞ and ＜Eve＞.
Machine lifeforms are currently confirmed to be in temporary confusion and chaos.
Seeing this as an opportunity to annihilate the enemy, the ＜Army of Humanity＞ issues an order for all YoRHa units to commence an all-out attack on the machine lifeforms.
This unit, in collaboration with 9S, the designated partner of this tactical support unit, will begin its mission to oversee the Type S models in a coordinated mission.
Episode 3: break ti[M]e
▶▶ Pod 042 - Report:
YoRHa units 2B and 9S rescued a Resistance group from being attacked by machine lifeforms. The Resistance unit leader identified as ＜Lily＞ guides them to their base of residence, the Resistance Camp.
During their stay at the camp, units 2B and 9S obtain information about unique machine lifeforms from the Resistance member identified as ＜Jackass＞.
It is determined that this information exists in the same parameters of the investigation mission assigned to 2B and 9S.
Proposal: Begin exploration of the Desert Zone with Jackass.
Episode 15: no [I] in team
▶▶ Pod 042 - Report:
The YoRHa soldiers and the Resistance unite to launch a large-scale operation on Earth to exterminate the machine lifeforms.
However, a larger-than-expected number of machine lifeform units has been confirmed. Each area has requested assistance.
This unit, in collaboration with 2B, the designated partner of this tactical support unit, will provide backup and support to the androids on the ground.
――Warning: EMP attack and logic virus attack from the enemy confirmed ――
――Communication error――