FANDOM


Oko Jr. & Oglop are recurring enemies in the Momodora series.

Momodora I Edit

Momo I Oko Jr. & Oglop

Oko Jr. & Oglop is a duo of enemies and can be first encountered in Area 2 of Momodora I.

The two consist of a box with an eye in the middle (Oko Jr.) and four more eyes, that are used like wheels to drive around a block (Oglop). The fact that they are unable to attack by themselves makes them more of a nuisance than an actual enemy.

Upon taking damage, Oko Jr. will disappear, leaving Oglop to spin around the surface its stuck to. The four eyes then can be destroyed with an additional attack.

Momodora II Edit

Momo II Oko

Two Okos racing against each other.

Oko is an enemy that can be encountered in Momodora II.

Unlike in Momodora I, Oko counts as only one enemy in the second game of the series and not as a team of enemies. The design, however, didn't change: Oko still consists of a box with a large eye and four smaller eye at the sides and still drives around blocks.

The attack plan Oko has didn't change either: Their only way to attack the player is by passing through the character, damaging on contact.

Momodora III Edit

Eye Box

Both enemies as one unit in Momodora III.

Oko Jr. & Oglop is a duo of enemies and the first enemy encounter in the Ishlith Shrine in Momodora III.

Momodora handles the two in the same way they worked in Momodora I: The two are seperate enemies again consisting of the eye box (Oko Jr.) and the four additional eyes (Oglop). The behavior stayed the same aswell, driving circles around blocks and beingunable to attack by themselves.

When using the charge attack to throw one paper seal, the box in the middle can be destroyed and Oglop will continue to spin around the surface its stuck to. The four eyes then go down with one more attack.

Gallery Edit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.