What kind of logic is this? It's a problem if the pet dies, so remove the pet?consider what happens after the pet dies, or the duration you can have it outside is up? that total performance you talk about will change.
Keeping your pet alive will sacrifice more time and effort. The solution is to make things simple. No splitting or sacrifice of strength and power for a pet. That will equal in maximum performance by the dragoon. So, no to pets. Dragoon is better off without it
Easier solution: Pet's don't take damage and can't die. Problem solved!
Then you have an easily abuse-able system in which the Dragoon can simply kite mobs while the Wyvern kills everything for it.
I think the playerbase's decision on this matter is fairly clear: They would rather NOT have a pet attached to the job.
That doesn't mean there are no alternatives. Why we can't simply put Wyverns on the same optional 'battle mount' content as chocobos is beyond my understanding. That way it's balanced against the likes of Chocobos and Magitek armors instead of balanced against Dragoons.
Look, what I was trying to say is that those problems can be solved without skipping the pet. If you don't want the Wyvern to kite, then don't let them get hate. If you don't want them to attack whithout getting hate while the dragoon is kiting, then only make them attack when the dragoon attacks. There's no shortage of solutions, and there are a thousand ways of implementing a pet.
As someone mentioned before, having a wyvern would be a good way to differentiate the job - even if it's only in appearance. The only reason why it's rejected seems to be
a) because people are lacking basic understanding of math, and
b) because all they can think of is an exact copy of the system in XI
Your solutions only creates more complications. The favorable solution is to simply not divide the Dragoon strength with the pet. Also the sentence I highlighted is irrelevant. My proof is Dragoons in past Final Fantasy games and those after XI. I want to show you some examples.Look, what I was trying to say is that those problems can be solved without skipping the pet. If you don't want the Wyvern to kite, then don't let them get hate. If you don't want them to attack whithout getting hate while the dragoon is kiting, then only make them attack when the dragoon attacks. There's no shortage of solutions, and there are a thousand ways of implementing a pet.
As someone mentioned before, having a wyvern would be a good way to differentiate the job - even if it's only in appearance. The only reason why it's rejected seems to be
a) because people are lacking basic understanding of math, and
b) because all they can think of is an exact copy of the system in XI
FF4 Kain Highwind
FF7: Cid Highwind
FF8: Ward Zabac. (Jump attack)
FF9: Freya Crescent
FF10: Kimahri. Also has Jump Attack
FF13: Oerba Yun Fang.
FF13 Versus: A female dragoon seen in trailers. Jumping on-board an airship.
What do they have in common? Jump, and Lances. Easy to differentiate right? None of them had a pet. sooooo no to pets.
Last edited by Andrien; 11-04-2011 at 06:35 AM.
congratulations you just described lancer.Your solutions only creates more complications. The favorable solution is to simply not divide the Dragoon strength with the pet. Also the sentence I highlighted is irrelevant. My proof is Dragoons in past Final Fantasy games and those after XI. I want to show you some examples.
FF4 Kain Highwind
FF7: Cid Highwind
FF8: Ward Zabac. (Jump attack)
FF9: Freya Crescent
FF10: Kimahri. Also has Jump Attack
FF13: Oerba Yun Fang.
FF13 Versus: A female dragoon seen in trailers. Jumping on-board an airship.
What do they have in common? Jump, and Lances. Easy to differentiate right? None of them had a pet. sooooo no to pets.
i dont have to research anything as i have played every game listed there more than once and have completed them all. save for versus and that i probably will too.
Dragoon is lancer such as it was in tactics the name being localized and what not.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.