Sorry if i did not word everything greatly XD ![]() Since Teshin is a Dax he was created by the orokin (Ballas), cannot defy his master/creator (Explains when umbra kills Ballas how you the operator is holding umbra's arm which means that you basically took umbra's arm with sword in hand and impaled Ballas), can use warframes as long as he is physically inside of them (When teshin is consumed by the infested it makes him look fugged up so he decides to use the warframe). During Ballases final moments he says to umbra once again "i created you" and then dies like a It basically ends there. You then gain umbra and proceed to go and kill Ballas. When going through the (this is the best i can do to describe this) Black and Gold sorta abyss thing you continue to her issah's voice untill you get to umbra. But in the last one you go into umbra's memory yourself and tell him that he "did not kill him" refering to when ballas then makes teshin kill issah. Then you go through chasing him down in different missions re-living his memory's blah blah blah. You then build umbra and his dumbass escapes. Ballas then says to umbra that he created him before the lotus comes in and destroys umbra. So then going back to where umbra is distressed then trys to kill ballas. Also in the memory sequences the scene continues to become even more infested the further you get (Indicating what happened to Teshin). So then Teshin jumps out at Issah and kills him. Teshin then can't fight back his illness any longer and he turns into one infested boi Ballas then orders Teshin to kill his son. Throughout the memory's teshin is incapable of speeking.Later Ballas tells Issah that it is time then proceeds to tell you you through telepathy that he will watch him die. During each memory sequence we see Ballas, Teshin's son (Issah), and Teshin. For this to make sense you have to remember that throughout the quest you have to chase down umbra and use transference to access his memory. Ballas then comes out behind a rock and tells him to "Howl all you won't" and "it won't bring him back". We see umbra who looks at himself and then howls (cries maybe). I am editing this post every time I find some new information from other players to try to keep it concise.So lets start at the beginning of the sacrifice quest. When I placed arcane fury on config B the issue started again permanently causing the bug on that config as well removing or replace the arcanes does not resolve the issue I had a max rank arcane fury on config A and a max rank arcane guardian but on config B I only had a max rank guardian ![]() Then I found that for me the bug wasn't happening on config B but I had an almost identical build same mods that were slotted in the same slots the only difference was 1 arcane Then a user posted about the bug happening once the mod capacity exceeds 60. We thought the bug was caused by hunter adrenaline/rage mods. It happens 100% of the time on every mission so replicating this bug is not difficult. If Umbra AI character takes too much damage and becomes "still" or regular non-AI character he can be healed to max HP and remains at 100% HP on transference in. When I heal him with life strike mod he heals to 100% because it doesn't require me to leave the warframe. Whenever I try to heal my Excalibur Umbra with my operator with the Magus Repair operator arcane it doesn't heal the playable warframe character to max HP (but to 300 or base health) only the AI specter that Umbra becomes on "transference out". ![]() On transference Excalibur Umbra drops to 300 health. I noticed It 1 day ago (02/09/22) maybe something from last updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |