I Don't care if the game is 16 years old

...

 

...

 

...

 

But you are definitely wrong about that! I can't even describe how wrong you are because that would be like admitting that there is a correct thing about you, that being the amount of wrong that you are.

 

Look at how many times you said wrong in that sentence. Projecting much?

 

...

 

...

 

You are wrong! I only used the word "wrong" three times in that entire post

Not necessarily. From a story perspective, I see Gambits as the lead party member figuring out better ways of explaining various strategies to the rest of the team.

 

Exactly[DOUBLEPOST=1365569496][/DOUBLEPOST]

That's possible, but you're still collecting things that closely resemble actual code

 

...

 

...

 

So here's a video I just made showing the stats and such of my first / main file.

Why I no able to beat Emerald and Ruby Weapons!? :c

 

Gambits have a one big advantage compared to manual imputs.

Let' s say for instance that you chose to launch a healing spell, but that unfortunately your target died before the action gauge got full. Well sucks to be you, you can' t cancel any action manually. If on the other hand you had assigned healing and resurection to gambits while prioritizing resurection, the healing spell would have been cancelled as soon as your character died and life or phoenix down would begin loading instead.

Against the toughest bosses that nuance can save the day.

 

No, not exactly.

So then, you would call saying, "Hey, if you're feeling up to it (HP >75%), attack the nearest enemy to you," something that resembles actual code?

 

And that's why gambits are so handy for allies, but in my opinion, if you're going to set your main character to auto pilot, there's no point in playing in the first place.

 

Why in the world would you choose that color scheme?

 

No, because it's casual enough to not be a code. Gambits are sterile, so they remind you more of code. Everything in the game is code, but it's weird when they remind you it is.
For example, in this case, the 75% thing provides a threshold, but if it was just HP >75% <action> nearest, then it's more like code.

 

...

 

It's still probably closer to what the character is thinking than:

Code:

if
    HP.Balthier >= 0.75
then
    Attack [referrer to the part of Balthier's AI that determines which enemy is closest]
if
    HP.Balthier < 0.75
then
    initiate [referrer to the part of the program that makes Curaga work]
else
    Attack [referrer to the part of Balthier's AI that determines which enemy is farthest away]

 

...