FANDOM


Howl of the Kubrow is an optional Quest introduced in Update 14.0. This short quest tasks players with finding the equipment necessary to create their own personal Kubrow.

ProgressionEdit

  1. Complete the tasks listed in the Junction description on Venus then defeat the specter guarding it. This will unlock the "Howl of the Kubrow" quest.
  2. Once back aboard the Orbiter, go to the Codex and open Quests. Select "Howl of the Kubrow" and choose 'Begin Quest'.
  3. Go to Navigation and choose "Install Segment". A "HOWL OF THE KUBROW" holo-sign will appear over the map console. Lotus will then tell the player to go to Unda, Venus (Survival) to find the Incubation Segment.
  4. Select Unda from the Solar Map and commence the mission.
  5. The player must fight for at least five minutes to find the Incubator.
  6. Once back aboard the Liset, go to the empty stasis pad area near the Arsenal and select "Install Segment". The Incubator will appear on the stasis pad; selecting it will tell the player how to commence incubating a Kubrow.
  7. Select E Prime, Earth (Exterminate) from the Solar Map, Find a Kubrow Egg by destroying Kubrow Dens. It can also be purchased for Platinum64 10. Currently, only one Kubrow Egg can be in the player's inventory! If a second Egg drops in-game while the first Egg is in the inventory, it will be impossible to pick up the second Egg and it will be left behind. Use the first Egg by starting incubation before farming for another Egg.
  8. Once the player has acquired an egg, one must acquire an Incubator Power Core. It can be acquired through the Market ready-made or in the form of a blueprint.
  9. After acquiring the Power Core, the Egg incubation will start and the Egg will hatch after 48 hours. After it hatches, the player can name the Kubrow, and will have to manage the Kubrow's DNA integrity and loyalty.
  10. The player will have to manually mature the Kubrow in order to complete the quest.
  11. The player must then go to Gaia, Earth to obtain a collar from the Grineer via a 5-wave defense mission. The object to protect will be the player's Kubrow itself.
    KubrowCollar
  12. Once the collar has been obtained, the player will be able to deploy the Kubrow.

Intercepted MessageEdit

Upon beginning the Howl of the Kubrow quest, the player will receive an intercepted message in the Inbox. It provides some background/lore on what the Corpus were doing with the Incubation module.

INTERCEPTED CORPUS MESSAGE: Where is my Kubrow?

Dr. Intehb,

You have had the Orokin Incubator Segment for months and still you've produced nothing but genetic rejects. You promised me a Kubrow worthy of an Orokin prince, not a misshapen ball of hair and teeth.

At great expense, I have procured another batch of eggs from the forests of Earth. They will reach your facility on Elara shortly. Do not waste these as you did the last ones.

I will have my Kubrow of my own. If you are not up to the task, I will find someone who is.

Frohd Bek

NotesEdit

  • By default, the Liset has 2 available stasis chambers.
  • It is currently unknown whether the Helminth Charger can be incubated to complete the quest, with results seeming to differ from player to player.

MediaEdit

  • To Pet Baby Kubrow Press Melee Button

Start a Discussion Discussions about Howl of the Kubrow

  • Offline Segment Required???

    10 messages
    • Don't you just love it when you find out about something that was added, and then realize that you don't need it because you pla...
    • 68.8.105.164 wrote:Any real answers...? Offline thread... not pot offline, or crack offline, or even worthless answers offline! Do you e...
  • So about the Howl Of the Kubrow Quest

    2 messages
    • What happens if I used the pink cyst to hatch it into a charger, but here is the question will I progress through the quest if I hatched a Char...
    • no well idk

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.