Leveling a Dragoon after Heavensward - Bye bye Immerson! (MASSIVE SPOILERS INSIDE)

[Odstarva]

Hold on!

If you haven't completed Heavensward and care about the story, turn back now! Otherwise, continue to (yet another) sigh/complain/suggestion thread.



Well, I've been having loads of fun in Heavensward! After getting my weekly from Alex, I decided to go ahead and level a few more classes - to be specific Miner, Fisher, Lancer (Dragoon), Astrologian, Marauder.

Well, after I reached lvl 30 as a Lancer and did my initial job quest, I felt hurt. So hurt.

Estinien is alive and well and the game behaves as if I've never met him or as if indeed he hasn't turned into a HUGE DRAGON. Although I understand that (obviously!) this is an MMORPG and it's impossible to account for every player action and/or in what order the game will be played, Square-Enix has been giving Final Fantasy XIV so much attention to detail that I didn't believe that this could happen.

This didn't kill it for me, I'm still going to keep pushing forward and enjoy the job along with this story portion. It's just that it feels disconnected which is a bit of a shame!

[Raeletta]

It happened before 3.0, even if you did it afterwards. Think of it as playing a memory.

[Kaedan]

If you are doing the Dragoon quests now, you are essentially having a "flashback" of what you did before the events of Heavensward. This is true for all the job quests, like the Culinarian quest which has Nanamo in it, I believe.

[Eidolon]

Hah! I was genuinly curious how they handled this when I saw the end of the 3.0 story. Funny thing is, I'm sure the same people who debated locking jobs behind Ishgard for "Lore Reasons" will likely rationalize this as being "Two different time periods" and say that the events of the cutscenes of DRG 2.0 took place before the events of 3.0. Lul.

Thanks for the information! I was honestly wondering while going through the story if Mr.Azure's armor would be red, and then I got to the end and was like, "I HAVE SO MANY QUESTIONS..."


Edit: Hot ****, see? They've already started with their flimsy excuse. Gotta love that lore narrative only being important when it applies to what you care about o/

[Raeletta]

Hah! I was genuinly curious how they handled this when I saw the end of the 3.0 story. Funny thing is, I'm sure the same people who debated locking jobs behind Ishgard for "Lore Reasons" will likely rationalize this as being "Two different time periods" and say that the events of the cutscenes of DRG 2.0 took place before the events of 3.0. Lul.

Thanks for the information! I was honestly wondering while going through the story if Mr.Azure's armor would be red, and then I got to the end and was like, "I HAVE SO MANY QUESTIONS..."


Edit: Hot ****, see? They've already started with their flimsy excuse. Gotta love that lore narrative only being important when it applies to what you care about o/

Ishgard is totally inaccessible until you manage certain story feats, so jobs only available there were always going to be locked in there. Old job quests were always available and thus, always happened before Heavensward. It's not a flimsy excuse, it's a logical one when it comes to limiting the amount of reworking they would have to do.

I mean, what would they do in my situation? I levelled LNC/DRG to 34, so I've seen Estinien (Who acknowledged he knew me, but unlike others who maxed the class, I have never been recognised as an azure dragoon), but if I go back to it at this moment, it'd make no sense whatsoever unless it's essentially a flashback. To modify the story that first quest set up (Potentially once for each stage someone did / did not do before HW) would be pretty hard. I met the guy and he was a dick, if I go back for the 35 quest and he's simply never seen again, how do they replace him?

TL;DR, think for an additional moment and it works much simpler for all the stuff locked into 2.x to -always- have occured in 2.x

[Eidolon]

TL;DR, think for an additional moment and it works much simpler for all the stuff locked into 2.x to -always- have occured in 2.x

Cheap and flimsy excuse by virtue of the fact that you could easily explain away your feats being completed in 2.0 and 3.0 being the start of its own story. GASP! It works both ways! "I didn't get Ishgard access pre-3.0, just like I didn't become an Azure Dragoon post-3.0."


See how flimsy the logic is when you "Think for an additional moment"? It's such a flimy argumenet that literally the arguement you try to make instantly can be turned around and thrown against it, and succeed.

I do not have any unreasonable expectations of SE. But I do think there are things that could be done far better - the content capping for new jobs, etc. is one of the biggest ones that I'm against. I do think it'd of been AWESOME if we had maybe another way to identify a new Azure Dragoon. Gods know they do things in handwaves saying there was "Another way" the whole time.

Let's take a look at Summoner:
Oh, you never actually fought Bahamut in 2.0? It's fine. YOU'RE TOTALLY ABLE TO CHANNEL HIS AETHER BECAUSE YOUR CHARACTER WAS AT CARTANEU.

Seriously? I hated this excuse for SMN. I was looking forward to something AWESOME, and instead got a handwave of an explanation. But you know what? At least contextually, it works. Just like any of the jobs being available pre-50 would've worked.

TL;dr. Think for a moment and it makes sense if all 2.0 stuff occurs in 2.0, and shouldn't be a limiting factor for the player accessing content outside of 2.0.

[TheCurls]

Cheap and flimsy excuse by virtue of the fact that you could easily explain away your feats being completed in 2.0 and 3.0 being the start of its own story. GASP! It works both ways! "I didn't get Ishgard access pre-3.0, just like I didn't become an Azure Dragoon post-3.0."


See how flimsy the logic is when you "Think for an additional moment"? It's such a flimy argumenet that literally the arguement you try to make instantly can be turned around and thrown against it, and succeed.

I do not have any unreasonable expectations of SE. But I do think there are things that could be done far better - the content capping for new jobs, etc. is one of the biggest ones that I'm against. I do think it'd of been AWESOME if we had maybe another way to identify a new Azure Dragoon. Gods know they do things in handwaves saying there was "Another way" the whole time.

Let's take a look at Summoner:
Oh, you never actually fought Bahamut in 2.0? It's fine. YOU'RE TOTALLY ABLE TO CHANNEL HIS AETHER BECAUSE YOUR CHARACTER WAS AT CARTANEU.

Seriously? I hated this excuse for SMN. I was looking forward to something AWESOME, and instead got a handwave of an explanation. But you know what? At least contextually, it works. Just like any of the jobs being available pre-50 would've worked.

TL;dr. Think for a moment and it makes sense if all 2.0 stuff occurs in 2.0, and shouldn't be a limiting factor for the player accessing content outside of 2.0.

I read this like four times and still can't figure out what you're trying to say.

[Eidolon]

I read this like four times and still can't figure out what you're trying to say.

I would love some more substance in your critique. Saying "I don't understand what you're trying to say" is a little but... vague. It makes it difficult to respond, because I don't necessarily know what to respond to. I suppose I will try to outline my thoughts:


1) Content should not be gated behind 3.0 story, because the same arguement that 2.0 content "Appeared in the past" on Dragoon, can be used to likewise say that the story of 2.0-2.55 "occured in the past." It's like watching the prequel to a movie (Even though 9/10 times that creates massive plotholes) after watching the first movie. It should only add to the story.

2) There are noted occurances where cheap excuses are given for things that don't quite make sense by my eye. The summoner being the biggest one I've noticed so far - where before, we fought the primals first and were bathed in their aether through combat, you now have that just being present at Cartaneu (I might be spelling it wrong, sorry) enables you to use Bahamut's Trance.

3) I do not think SE did a bad job. But I do think there are bad decisions made within the game design, which is my biggest thing that I always argue against. There will be various opinions on this, but it is what it is.

[Delily]

Hah! I was genuinly curious how they handled this when I saw the end of the 3.0 story. Funny thing is, I'm sure the same people who debated locking jobs behind Ishgard for "Lore Reasons" will likely rationalize this as being "Two different time periods" and say that the events of the cutscenes of DRG 2.0 took place before the events of 3.0. Lul.

Thanks for the information! I was honestly wondering while going through the story if Mr.Azure's armor would be red, and then I got to the end and was like, "I HAVE SO MANY QUESTIONS..."


Edit: Hot ****, see? They've already started with their flimsy excuse. Gotta love that lore narrative only being important when it applies to what you care about o/

So, what would you have them do? Make multiple lines of DRG quests depending on where in Heavenward you are? Also, the DRK quest draws heavily on events in 2.X, so locking it behind the 2.X story line makes sense.

[TessaJalloh]

Edit: Hot ****, see? They've already started with their flimsy excuse. Gotta love that lore narrative only being important when it applies to what you care about o/

not an excuse when it comes from a community rep. this was handled months ago after 2.55 in relation to the culinarian final quest. in which Nanamo is a key player. They simply said that the quest chronologically took place before Nanamo's 'death' and thus she was hale and healthy.

Infact, if you've done the DRG questline BEFORE heavensward, Estinien gets extra dialog regarding you being the azure dragoon too.