Printable View
Started this fight and attacked then my path companion attacked with me after~ but... my path companion died because of 1hit~ on him & its only less than 260hp~ (mission failure) ~ i was @lv.38 ~ why do my path companion had only less than 300hp? i can't do this mission because of him~ he is lalafell cnj but it can't be this low HP ><;;... i could kill all enemies alone~ but couldn't b/c of him .
Is there any solution for this issue?
Well.. i just finished it~ i brought pug.50 + cnj.50 to kill enemies fast and buff my path companion~ then we won.
this mission is all about protecting ur path companion.. no other lol, SE must fix it and rise our path companions lvls.
Weird 2nd thread about this... is there something diferent about this fight after patch 1.19? i did it it before and path companion didn't give any trouble or help =/
that is wierd, my path companion soloed this for me as a miqote conjurer, since i was running it as miner. Something must have changed
I just did this last night, and it took me five tries as a level 38 Lancer, because my Highlander Gladiator companion died so quickly. I figured he should, given his class and race, have had some sort of survivability, but apparently not. I've solo'd every single scenario quest thus far, and this is the only fight I've had trouble with - and it's not even the mobs, it was just keeping my companion alive.
I only fought 3 mobs - 2 Lancers and an Augur. I went in with Provoke and Taunt equipped, and kept all the mobs off my Companion, but the Augur's spells still managed to kill him. I ended up winning by Provoke/Taunting the two Lancers, hitting Heavy Trammel and Leg Sweep early on to keep them focused on me, and killing the Augur as quickly as humanly possible. That seemed to be the key to it; even if all the mobs are focused on you, the Augur's spells are AoE and will still hit your Path Companion. Also, I managed a lucky stoneskin cast on my Companion right before the Amalj'aa fight started, which helped him survive the first AoE spell.
On an only somewhat related note, I crashed right after the "You have failed." message popped up but before I exited the instance, and logged back in.. to a completely empty and un-exitable Bowl of Embers. I had to Teleport to Camp Broken Water to get out again. As if I hadn't been frustrated enough. >:
Im lv 41 gladiator everytime i try this quest(about 17 times now) The path companion dies before i get a chance to heal him or provoke. I tried bringing a friend in to help me, same thing. Once the amaljaa come the path companion dies in ONE hit even with protect and stoneskin on. I cannot beat this quest.. help???/
My reply to another thread:
Quote:
I'm actually having this exact same problem. I started a new Mi'qote Character who is going full DoM. I have the Lalafell GLA companion and from what I can gather of my 12 attempts of this is that, for whatever reason Path Companions in Lord Errant are loading as an extreamly low level. My path companion hits for 0 or misses. and as soon as the Mages or Amal'jaa use Shadowfall, I instantly fail the mission as my path companion somehow gets 1 shot for anywhere from 350-450 damage.
Having done this quest already I know this isn't supposed to be the norm. The path companion should be at or around your level so that he can actually "participate" in the fight.
I sent in a bug report to hopefully see If they can investigate. My guess, they borked the quest post 1.19 since it has some data relating to ifrit. If a dev is reading, please investigate~
win this with 5th try, as Gladiator 39 , npc companion Cojurer ,did Stoneskin , Protect , Shell on him , kiled mages with easy , healed npc when need , also stored 3000 tp for Amal'jaa. When they appear run in with Circle Slash II . they hit my npc once in 5th try but Stoneskin saved him , never hit more so i made it :)
Had this problem on the rank 30 mission. My path companion kept getting one shot for about 200 damage. Was getting tired of parleying so I just had a high level come and one shot all the mobs for me. Freaking ridiculous.
I am having this problem too now. I can not do this quest because of this. The companion dies even before the Amaljaa start.
FIX THIS PLEASE, SO DAMN ANNOYING
Bumping this, complete and utter bullshit, NPC getting one shotted for 600 damage isnt even cool.
I am also stuck on this quest now. Most of the time my path companion is dead before I even finish loading in after cutscean. Anyone know how to beat this fight in its bugged state?
I easily solo it with a MRD lv. 38, my path companion was a great support, I think it should be impossible without her.
I just tried this for over 1 hour, NPC not only dies quick but also chases after the enemy as they run away >< Guess the questing ends here for me untill they fix this mess.
Same prob with "Toll of Warden" had to do that one 20X too. But not wasting any more time on this one.
Same here try 5 times I will back when it fix
OK so i was in the area as a LV41 PUG today and figured I would give it another try since it was right there.
Got the Win 1st try. I killed about 6 mobs before the fight and saving TP after the 5th so I could open with a AOE skill. After that I kept my focus on healing my NPC, AOE skills and making sure the mobs were not facing her as I fought them off. After dropping the 1st one the other two seemed easy.
So I was able to get thru this mission today but I still feel your NPC needs an HP or DEF bump up.
Enlist the help of a MRD50 Have it attack the adds to build TP. Then when the other Amaljaa pop, throw Storms Path
I would prefer they took the path companion and make it like the one in FFXI that you raised from level 1 to cap level, you could give him/her gear to upgrade damage, healing, defense, whatever the role you wanted, it would add a lot and give you more options like if you dont want to use your chocobo or if you have it injured (if they add that option) you may call it anytime and in any case be more useful because will have several pseudo classes. Maybe with the same classes that we have now.
i seem to disconnect every time i try to parley. anyone else having this issue?
edit:
well by the time i posted this, server seems to be highly unstable so i will try again later