3vrB257ncl4qg9s

SOTET Battle

Aug 21st, 2026
48
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 80.74 KB | None | 0 0
  1. Star Ocean 3 - Till the End of Time
  2.  
  3.  
  4.  
  5. Battle System & Mechanics
  6.  
  7.  
  8. - I suppose I should preface this by pointing out that the game features
  9. a *very* substantial margin of error. You certainly don't need to become
  10. particularly familiar with the game's systems in order to make progress,
  11. but you might enjoy the game more if you do. If nothing else, you should
  12. at the very least have a look at the AI sections to learn about things
  13. like self-preservation, stealth, and magic attract.
  14.  
  15.  
  16. Contents
  17.  
  18. Normal Attacks Parrying
  19. Fury Frame Advantage
  20. Targeting Damage Calculation
  21. Skill Setup Death
  22. Canceling / Chaining Healing
  23. Skip-Canceling Misc.
  24. Blocking Status Ailments
  25. Sidestepping Characters
  26. Magic Battle Bonus
  27. AI Battle Trophies
  28. Enemy AI Difficulty Levels
  29. Hitstun Bugs
  30.  
  31.  
  32. Normal Attacks
  33.  
  34. - There are two attack buttons - Do you follow? - assigned to Confirm
  35. and Cancel (commonly referred to as 'Minor' and 'Major' or 'weak' and
  36. 'strong'). Aside from the two buttons, attacks will vary depending on
  37. the distance to the enemy. Most characters also have attacks that are
  38. triggered when the target is in the air.
  39. - Attacks performed with Confirm are fast but can be blocked. Many of
  40. them have a base damage multiplier of 1,0 (meaning, the base damage is
  41. simply the difference between your ATP and the enemy's DFP). Attacks
  42. performed with Cancel are stronger and unblockable but also slower.
  43.  
  44.  
  45. Fury
  46.  
  47. - All actions consume Fury. Your max Fury is 100 and cannot be increased.
  48. You will quickly recover Fury at a rate of 100 per second while "resting,"
  49. as in, while you're standing still and doing nothing. If your guard is
  50. broken, it takes two seconds before you start to recharge. You will also
  51. slowly recover Fury when flinching, at a rate of about 10 per second.
  52. It's possible to reduce Fury consumption with certain skills and equipment.
  53. Killing an enemy gives you 30 Fury. Enemies don't always recover their
  54. Fury when standing still. When moving, max Fury is 99.
  55. - There are many attacks that can deal Fury damage. Fury damage done by
  56. enemies is always 50.
  57. - During battle, you can see the enemy's Fury as indicated by a green bar.
  58. Try to learn to acknowledge the enemy's Fury at least when it's full.
  59. - Enemies have a minimum Fury value of maybe 10, meaning they can always
  60. perform certain attacks without running out of Fury.
  61.  
  62.  
  63. Targeting
  64.  
  65. - When using Auto targeting, you will automatically target the closest
  66. enemy during battle. Manual targeting requires you to switch targets
  67. manually by pressing the Disintegration button. The action will not
  68. pause while doing so. As a result, you should *absolutely* stick to
  69. Auto *unless* you're using ranged attacks that don't easily hit multiple
  70. enemies, or you're up against a boss fight with multiple enemies and
  71. you need to focus on a specific one.
  72. - If you have the battle menu open, you can press and hold the Disinte-
  73. gration button to check the targets.
  74.  
  75.  
  76. Skill Setup
  77.  
  78. - You have four slots for battle skills (SR Confirm, LR Confirm, SR
  79. Cancel, LR Cancel) and two slots for support skills. Once a skill has
  80. been set (and it's something that actually requires activation), you
  81. can initiate it by holding down the corresponding button (as the game
  82. keeps reminding you) at corresponding range. The activation occurs once
  83. the button has been held down for about 0,2 seconds.
  84. - Just like with normal attacks, battle skills performed with Confirm can
  85. be blocked, while those performed with Cancel cannot be. Unlike before,
  86. using battle skills now (typically) consumes HP. Skills set to Cancel
  87. gain an additional multiplier, but also consume more HP/MP and Fury, the
  88. HP/MP consumption being proportional to your max HP/MP. With moves that
  89. use HP, it's no big deal; if you're running low, all you need is a quick
  90. healing spell (either during or after a battle). When it comes to moves
  91. that use MP, though, you need to be more mindful.
  92. - The power or activation rate of battle skills increases as they are
  93. used and gain levels. Lv10 damage multipliers are 1,5 times that of the
  94. base Lv0 values (which are never used, since moves start at Lv1 and
  95. already have a 5% bonus). Most skills require 1674 uses to reach Lv10.
  96. Reaching Lv10 organically takes a good while. Grinding is, of course,
  97. an option, and you can get to Lv10 in 2-3 hours or so. This kind of
  98. boosting is certainly not necessary, however.
  99. × Charge and Aerial do not increase in power as they level up.
  100. - All battle skills use a certain amount of CP. CP maxes out at 15 and
  101. there's no way to increase it beyond that.
  102. - A small number of skills have range restrictions. Specifically, the
  103. following skills are limited to SR only: Charge, Aerial, Lightning Blast,
  104. Earth Glaive, Efreet, and Southern Cross.
  105. - Just like in previous installments, in order to truly excel in battle,
  106. you need to take full advantage of hissatsuwaza / battle skills (or at
  107. least the good ones). You can find my assessment of all the waza in the
  108. misc file. Everyone has their favorites, though, so, regardless of what
  109. I may say about them, I encourage you to experiment with different moves
  110. and different characters yourself. Just make sure your setup allows you
  111. to chain properly (explained below).
  112. - The single most useful support skill is No Guard, without which many
  113. of your chains would be interrupted.
  114.  
  115. - SP is not allocated into IC-related skills this time around. Instead,
  116. they are used for the four status skills: HP, MP, Attack and Defense.
  117. It bears repeating: the Attack and Defense skills do *not* increase your
  118. ATP or DFP. They merely affect the behavior of AI-controlled characters
  119. (see the AI section a few pages below). This is probably the simplest
  120. and most common misconception people have about the game.
  121. - I consider HP to be the highest priority, although I do raise most
  122. fighters' (all except Nel and Maria's) MP to Lv5 before focusing on HP.
  123. After maxing out HP and MP, I go for Attack. I keep Defense at Lv1 so
  124. as not to enable self-preservation, which simply isn't useful.
  125. - SP gained per level is about the same as your level figure (Lv + 1~3)
  126. up until Lv39. After Lv39, it's about 0,55 times the character's level.
  127. - You can reach max HP and MP skill levels around Lv45 (HP at Lv31-32).
  128. The total boost is 6850 HP and 1260 MP. You can have HP, MP, and Attack
  129. maxed out by Lv70+ (all four by Lv87+).
  130.  
  131. - Tactical skills are the only ones you can customize mid-battle. These
  132. include things like Anti-Attack Aura and Berserk.
  133. - Berserk is eventually learned by every character and greatly increases
  134. your offensive capabilities at the cost of a DFP penalty. The DFP penalty
  135. makes little difference until you start customizing your weapons with BoP,
  136. which shouldn't be until the post-game. Berserk is particularly vital for
  137. AI-controlled characters, whose chaining ability is severely crippled
  138. without it.
  139. - Then there's Scan Enemy and Taunt, which are used through the Tactical
  140. Skills menu during battle.
  141.  
  142.  
  143. Canceling / Chaining
  144.  
  145. - Activating battle skills in succession will allow you to greatly
  146. increase damage thanks to the cancel chain multiplier. Doing so simply
  147. requires you to input the command for the next move during the current
  148. move. However, there's a pattern that needs to be followed.
  149.  
  150. 175% 200% 250% 300% (max)
  151. a. Confirm normal -> Confirm waza -> Cancel waza -> Confirm waza ->Cancel waza
  152. b. Confirm waza -> Cancel waza -> Confirm waza -> Cancel waza (etc.)
  153.  
  154. - As you can see above, a chain can only be started with a Confirm attack
  155. whether it's a normal attack or a battle skill. If it's a normal attack,
  156. it can be followed by a Confirm skill. Beyond that, you just alternate
  157. between Confirm and Cancel.
  158. - Battle skills and blockable normal attacks have a cancel window (or,
  159. possibly, multiple cancel windows) and a cancel queue window. The cancel
  160. queue window is the entire time window from the very start of the move
  161. up to the start of the actual cancel window. During this window, you can
  162. input the command for the next move in the chain, but the move is not
  163. ended. The cancel window is the time during which inputting the command
  164. will indeed initiate the next move in the chain. If the command was queued,
  165. the move is initiated as soon as the cancel window begins. Eg. Nel's
  166. Shisentou is 1,6 seconds long with a cancel window that starts at the
  167. 1,1s mark. Keep in mind, it takes about 0,2 seconds to input a waza
  168. command, so you have to take that into account. If you start holding
  169. down the button when there's less than ~0,2s left on the window, then
  170. it's too late.
  171. × Attacks do *not* have a cancel queue window in the NTSC-versions.
  172. If you're not holding down the button for the next move during the
  173. actual cancel window, nothing happens. This makes manual control of
  174. multiple characters *much* harder.
  175. - Many of the best moves cause knockdown, so delaying the canceling will
  176. be needed to avoid losing hits due to knockdown invincibility.
  177. - Once the target is dead, you can't chain any further.
  178. - Besides just straight up multiplying damage, chaining is also useful,
  179. since it cuts recovery time and is more cost efficient, as the resource
  180. consumption (HP/MP, Fury) stays the same.
  181. - Since blockable attacks are a significant liability, it's preferable
  182. that your blockable battle skills are quick and minimalistic, with low
  183. CP and Fury costs and no knockdown. The term 'cancel fodder' is often
  184. used to refer to these moves.
  185. - A typical chain involves using the 'heavy hitter' (the move set to
  186. Cancel) twice, first at 200%, then 300%. Using it a third time in the
  187. same chain (in a so-called 'triple chain') is possible in some cases,
  188. but many of the top moves require the Fury use -2 or -3 factor to pull
  189. that off.
  190. - Fury use -x stacks up to -4. The most you can get out of a single
  191. factor is -3, but -3 is fine. -4 would mainly be useful for multi-hit
  192. moves that consume Fury continuously.
  193.  
  194.  
  195. Skip-Canceling
  196.  
  197. - Skip-Canceling involves exploiting the cancel window bug that is
  198. *only* present in the PAL-version (or, at the very least, only reliably
  199. exploitable in the PAL-version). Performing it is rather simple. There
  200. are two requirements:
  201. 1. Must input the commands for the next two moves in the chain during
  202. the cancel queue window of the current move. The Cancel button must
  203. be held at the end of the cancel queue window, whereas Confirm must
  204. not be.
  205. 2. Must be in optimal range for the next move (the move you want to
  206. skip) at the end of the cancel queue window.
  207.  
  208. - When these two requirements are met, the next move in the chain is
  209. essentially skipped, and you will instead initiate the one after that.
  210. This is useful because it allows you to skip cancel fodder and, thus,
  211. eliminate the possibility of getting blocked. The skipped move is not
  212. ignored, however; it will still consume HP/MP and Fury, but it will
  213. also increase the cancel multiplier (and gain proficiency). The only
  214. difference is that the move ends *very* quickly after it's initiated.
  215. - Skipping the initial cancel fodder can be tricky because of the small
  216. cancel queue windows that normal attacks have. You'll need to work on
  217. your timing and technique. Do *not* use the default button settings.
  218. I use Square as Confirm and X as Cancel myself. You can simply hold
  219. down both buttons and, when the normal attack begins, release Confirm.
  220. I myself only hold Confirm and then do this kind of wavy motion with my
  221. thumb.
  222. - 'Heavy skipping' involves skipping the first heavy hitter instead of
  223. the cancel fodder. In some cases, this could result in higher DPS than
  224. normal skip-canceling, although the difference is small. It's also harder
  225. to pull off, since you need to convince the enemy to not interrupt you
  226. when you're going through the double cancel fodder (although No Guard
  227. helps).
  228. - If you queue up a skip cancel and then switch to another character,
  229. the skip will not occur.
  230. - Charge and Aerial cannot be skipped, although the same skip-canceling
  231. method can be used to trigger, and possibly exploit, the Charge bug,
  232. which you can read about in the last section.
  233.  
  234.  
  235. Blocking & Counter Auras
  236.  
  237. - Blocking occurs when anyone with 100% Fury is hit by a blockable
  238. attack. For every hit blocked, the attacker loses 30 Fury. Unblockable
  239. attacks are easy to recognize, as the enemy is surrounded by a purple
  240. aura when using them, just like your characters.
  241. - Aside from not taking any damage, blocking results in the subject emitting
  242. a counter aura or Anti-Attack Aura / AAA (if they have one). There are 7
  243. different ones, most of which are obtained from Textbooks that are found
  244. throughout the game, while one of them requires an accessory.
  245. × Selling a Textbook doesn't make you lose any counter auras that have
  246. already been learned. However, this will prevent any future characters
  247. from learning that aura.
  248. - The most common counter aura used by the enemy is the basic one that
  249. stuns you (for 4 seconds or until you get hit with a physical). Enemies
  250. with damaging counter auras (Homing and Wide Area Homing) become common
  251. after Disc 1. Getting blocked by these enemies can result in some pretty
  252. devastating self-ownage. If you gain control of your character before they
  253. hit you, you can potentially avoid the damage by sidestepping.
  254. - The first counter aura you get is indeed the basic stun one. However,
  255. inflicting stun on a tougher enemy doesn't mean it's safe to attack them.
  256. Force resistance still applies, meaning they could easily attack you the
  257. moment your attack lands.
  258. - I find the best counter aura to be Homing (obtained quite early), which
  259. not only reflects half of the damage you would have received, but, more
  260. importantly, also floats the enemy, rendering them pretty much completely
  261. vulnerable, if only for a short while.
  262. - Some attacks are not actually interrupted when blocked.
  263. - Magic and counter auras cannot be blocked.
  264. - If anyone at 100% Fury is hit by an unblockable attack, their guard
  265. is broken and they lose 50% Fury.
  266. - There are situations where you may want to use a PC as a "shield;" set
  267. them on Manual and simply have them stand next to an enemy while you attack
  268. them with another character.
  269. - A blockable attack can break a subject's guard if the subject is
  270. inflicted with any type of special stun (such as grapple or the spinning
  271. effect of Whirling Heat).
  272. - If an elemental attack is blocked and the blocker would have fully
  273. absorbed the damage, the counter aura will deal no damage. While the
  274. elemental variable is taken into account when an attack is blocked, the
  275. resulting counter aura is always non-elemental.
  276.  
  277.  
  278. Sidestepping
  279.  
  280. - Sidestepping makes your character invulnerable to physical attacks
  281. and counter auras for a very short period of time (about 0,25 seconds),
  282. allowing you to avoid damage when used skillfully. The invincibility
  283. occurs at the very beginning of the sidestep. As a whole, the sidestep
  284. is about 0,65 seconds long.
  285. - While hardly vital for your survival, sidestepping is a nice, little
  286. tool, nonetheless. Anytime you get hit when not in the middle of an
  287. action or not flinching, know that sidestepping could have allowed you
  288. to avoid the hit. It's less useful against multi-hit moves, but even
  289. avoiding one hit is still something.
  290. - While sidestepping will not protect you from magical damage, it does
  291. prevent you from flinching from it. This allows you to eg. avoid getting
  292. your guard broken by Fire Bolt or (mostly) avoid Lightning Strike.
  293. - By default, sidestepping requires you to hold L2 while moving the
  294. analog stick, but you should switch it, so that it's set to the d-pad.
  295.  
  296.  
  297. Magic
  298.  
  299. - Aside from the usual method of casting magic through a menu, it's now
  300. possible to set spells as battle skills, albeit only offensive magic
  301. and only for Sophia (and Adray to a *very* limited degree). When set as
  302. battle skills, spells can be used without any casting time, although
  303. there's still a slight delay (1,5s). The Major multiplier for spells
  304. is always 1,3. Even when set to Confirm, spells can't be blocked.
  305. - Magic is not a good source of damage except possibly for Sophia and
  306. Adray. Other characters will learn some offensive spells as well, but
  307. they should not be used. Disable them in the Symbology menu, so the AI
  308. won't cast them. They should be disabled for Sophia and Adray as well.
  309. If you want them using offensive magic, it should be set as battle skills.
  310. Disabling a spell in the Symbology menu won't prevent the AI from using
  311. it when set as a battle skill.
  312. - Adray can only set five spells as battle skills: the four most basic
  313. elemental spells and Southern Cross (who Adray can learn by leveling up,
  314. unlike Sophia, who doesn't get it until the post-game). By comparison,
  315. the only spell Sophia can't set as a battle skill is Crush.
  316. - Unlike physical skills, spells will remain active when cancelled.
  317. - Casting time can be reduced at most by 75% (with both a Star Necklace
  318. and Quick Symbol). However, because of the way the animations work (ie.
  319. the actual casting time being only a part of process), spells with a
  320. short casting time don't really get much, if any, faster.
  321. - When casting spells through the menu during battle, it's possible to
  322. try casting a spell even if you don't have enough Fury to do so. In this
  323. case, the spell will fail. Enemies will never start casting a spell
  324. without having enough Fury, but you can still force the spell to fail
  325. by dealing Fury damage.
  326.  
  327.  
  328. AI
  329.  
  330. - Fighters have five AI settings (found in the Tactics menu):
  331. 1. Attack enemy with all your might (AWAYM)
  332. 2. Act in a well-balanced manner
  333. 3. Conserve Fury
  334. 4. Focus your attacks (FYA)
  335. 5. Don't use coups de grace (ie. battle skills)
  336. 6. Off (manual)
  337.  
  338. - As always, don't expect much from the AI. Aside from the Tactics setting,
  339. you can alter the AI's behavior by spending SP on the Attack and Defense
  340. skills, which does make them suck less (at least Attack does), but even
  341. then, their performance leaves much to be desired. Then again, if the AI
  342. was actually competent, then the game would be playing itself to a large
  343. extent. A fundamental issue in party-based Action-RPGs.
  344. - Increasing Attack gradually makes chaining more likely for the AI, but
  345. it doesn't become consistent until very high levels. It takes a *lot* of
  346. SP to get there, however (820 SP to Lv10), and if you're not putting that
  347. SP into HP (and MP) instead, your characters will be rather fragile, with
  348. tougher enemies easily taking out huge chunks of your health with even a
  349. single, solitary attack. As such, I strongly recommend you max out HP and
  350. MP before you move on to Attack.
  351. - Increasing Defense above Lv1 enables self-preservation (on settings
  352. other than AWAYM), and I *have* to recommend keeping it at Lv1. The AI's
  353. efforts at self-preservation are far too often meaningless, with many
  354. enemies easily able to catch the sidestepping AI characters. especially
  355. once they hit a wall. Besides that, it's just a pain in the ass to try
  356. to keep the AI above the thresholds, mainly because of the MP threshold
  357. that's simply too high, possibly even higher than the character's max MP.
  358. And taking a couple of sidesteps away from the enemy when low on Fury
  359. just isn't necessary when using chains that leave the enemy knocked down.
  360. - Below, you can see the effects that some specific levels have.
  361.  
  362. Atk Lv2 | - May sidestep during self-preservation. (w/ Def Lv3)
  363.  
  364. Atk Lv6 | - Refrain from attacking invincible enemies
  365.  
  366. Atk Lv10| - Chain without fail when the attack deals damage
  367.  
  368. Def Lv2 | - Self-preservation (HP/MP)
  369. - Avoid enemies targeting you (Sophia & Adray)
  370.  
  371. Def Lv3 | - Avoid enemies when low on Fury
  372. - Avoid enemy when casting magic (for a while)
  373. - May try to avoid unblockable attacks with either a sidestep
  374. or normal movement. While Def Lv3 enables this, the odds of it
  375. happening are defined by the Attack level. At Lv1, it never
  376. occurs. After Lv3, override variable c starts to occur, and
  377. the character has a chance of also attacking the enemy in
  378. retaliation. At Lv6, it pretty much always happens.
  379.  
  380. - At the start of battle, the AI chooses an enemy as its main target and
  381. will not seek a new main target until the current one has been dispatched.
  382. However, the AI can also temporarily target and attack an enemy as a result
  383. of one of the five 'override' variables seen below. The detection range for
  384. these variables is a bit larger than the AoE of the Explosion spell.
  385. a. An enemy flinches
  386. b. An enemy attacks them with a blockable attack
  387. c. An enemy attacks them with an unblockable attack (req. DefLv3 & AtkLv3+)
  388. d. An enemy is stunned
  389. e. An enemy is casting a spell
  390.  
  391. - Due to variables a and b (and possibly c), the override target is indeed
  392. often the same as the main target.
  393. - Variables a, b, and c will not activate if the incoming attack can't
  394. deal any damage.
  395. - The AI trying to avoid an unblockable in variable c is admirable, but,
  396. again, far too often meaningless, as they might not even succeed in avoiding
  397. the attack (it's usually just one sidestep after all) or they'll just end
  398. up interrupting the attack. Either way, variable c isn't triggered all
  399. that much.
  400. - Flags for healing and support spells will also override main targeting.
  401. - When backing away to cast attack magic, a fighter may give up on the
  402. spell and use a physical attack instead (and not because of override
  403. targeting).
  404. - A fighter's avoidant behavior when casting magic stops after a little
  405. while into a battle, but can be briefly re-triggered by changing AI settings.
  406. Either way, it occurs on any AI setting.
  407. - A fighter won't back away from the enemy when casting spells with limited
  408. effective range (ie. Ice Needles, Lightning Blast, Earth Glaive).
  409.  
  410. - When searching for a new main target, the AI ignores enemies that are
  411. moving or immobilized by a status ailment. The exception is when using FYA.
  412. - When using FYA, the AI will choose a new main target from the enemies
  413. your controlled character has recently attacked. This allows a degree
  414. of control over the AI's targeting, as you could potentially attack an
  415. enemy once just to paint it as a target for the AI. However, the logic
  416. here seems to have some issues, as sometimes the AI enters a state where
  417. they fail to acknowledge any painted targets, but they may still respond
  418. to override variables a and b. This issue will remain even if you switch
  419. AI settings. This doesn't happen very often, though.
  420. × Switching characters also results in target painting.
  421. × Until you attack any enemy, FYA AI will target enemies normally.
  422.  
  423. - One of the AI's biggest flaws is Fury management, which severely
  424. impacts both their offensive and defensive capabilities (ie. chaining
  425. and blocking).
  426. - On most settings, the AI is set to act when above 39 Fury (the nFUp
  427. threshold, as seen below). As such, they don't really let their Fury
  428. recharge much higher than 40. While the AI may well idle for longer than
  429. needed (maybe the enemy is (temporarily) invincible or the AI is waiting
  430. to acquire a new main target or there's some other delay caused by the
  431. intricacies of the action logic), generally, they don't have more than
  432. 40-50 Fury to work with. That means they can only boost their heavy hitter
  433. to 175 or 200% (with Berserk). That's not *terrible*, but it could clearly
  434. be better (with the possible exception of moves that are difficult to chain
  435. beyond 200 anyway). There's nothing you can do to completely fix this,
  436. though. You can remedy it to a fair degree with Max Fury or you can just
  437. try to manually compensate. Max Fury is unfortunately often mutually
  438. exclusive with No Guard, which is far more important.
  439. - There's a separate Fury threshold when it comes to using "follow up"
  440. attacks, ie. chained attacks or continuation attacks. Furthermore, if
  441. the character's Defense skill is at least Lv3, the character will get
  442. away from enemies targeting them when below a certain threshold. They
  443. generally don't move as far away as with health self-preservation.
  444. - Once you've gotten your Attack level up, you should probably start
  445. using Well-balanced or FYA. A common problem with AWAYM is that the AI
  446. will use their leftover Fury after a chain for the cancel fodder move.
  447. You won't see that all that much on Well-balanced or FYA. You do have
  448. to be more mindful of the AI's MP, though, due to self-preservation (if
  449. enabled, which you shouldn't).
  450. - The AI may ignore Fury recharging if override targeting occurs.
  451. - The AI has no explicit blocking logic.
  452.  
  453. Fighter Mage
  454. FUp SelfP nFUp FUp SelfP nFUp
  455. 1 | - | <25 | <40 | any | - | <40 | <40 |
  456. 2 | <25 | <40 | <40 |
  457. 3 | <60 | <50 | <50 |
  458. 4 | <25 | <40 | <40 |
  459. 5 | <25 | <40 | <40 |
  460.  
  461. - When not attacking through override targeting, the AI will always use
  462. unblockable attacks on an enemy with 100% Fury. They'll primarily use
  463. unblockable attacks when the enemy is between 80-99% Fury, but also have
  464. a small chance of using a blockable (and this isn't because of an override
  465. variable (although that does happen as well)). Below 80%, the AI will only
  466. use blockable attacks (unless chaining occurs). For enemies casting magic,
  467. the AI will use unblockable attacks regardless of the enemy's Fury.
  468. - The insistence to try to break the enemy's guard is another one of
  469. the AI's great flaws, resulting in the AI spamming unblockables, often
  470. without even succeeding in breaking the enemy's guard. This is *horribly*
  471. inefficient. It's particularly regrettable for characters who can easily
  472. deal Fury damage at short range. If you're controlling a character who
  473. can easily deal Fury damage, consider softening up the enemy with some
  474. Fury damage to help the AI perform. The only other way to remedy the issue
  475. is to take matters into your own hands. At Attack Lv10, all the AI needs
  476. is that first blockable hit, so even if you're not going full-on manual,
  477. you could at least start battles controlling one character, start a chain,
  478. and then switch to your usual character. Naturally, if the AI is using
  479. anything with knockdown, their chain will be cut short without further
  480. manual compensation.
  481.  
  482. - The AI treats anti-air normal attacks as follow up attacks to floater
  483. normal attacks and will use them regardless of the enemy's Fury. Indeed,
  484. this often results in the character getting blocked, since those floaters
  485. are unblockables. Fayt, Cliff, and Mirage have normal attacks that enable
  486. this behavior. Fayt at least has a chance of using his unblockable anti-
  487. air attack (which can also deal Fury damage).
  488.  
  489. - If available, fighters will frequently use attack magic regardless
  490. of the enemy's Fury. As noted, this is very crippling to a character's
  491. performance. Therefore, it is best to disable the spells in the Symbology
  492. menu (out of battle only).
  493.  
  494. - The AI won't move from short range to long range in order to use long
  495. range skills (although it happens incidentally if attack magic is available
  496. and the character has Def Lv3+). As such, the only fighters who can be
  497. (*somewhat*) effective at long range in AI control are Maria and Adray.
  498.  
  499. - As already mentioned, increasing Attack makes the AI more likely to
  500. utilize cancel chains. At Lv1, they will only occasionally do so. At Lv10,
  501. the AI will not fail to cancel a move so long as it deals damage to anyone.
  502. This consistency is double-edged, as the AI will indeed never cancel if
  503. there's no damage (either because of a miss, knockdown invincibility,
  504. special attack invincibility, high DFP or elemental resistance). Even at
  505. lower levels, canceling is only possible when damage is dealt.
  506. × Moves that knock the enemy down are indeed problematic for the AI,
  507. although usually they won't have enough Fury to continue the chain
  508. anyway. If they do have enough and you're not too preoccupied. you can
  509. try to manually compensate.
  510. × There are some moves that the AI never cancels.
  511. × Technically, canceling is triggered by dealing damage regardless of
  512. the method. Eg., hypothetically, if Fayt was using an elemental weapon
  513. that was absorbed and then cast a spell that wasn't absorbed, the damage
  514. from the spell would briefly enable chaining.
  515. - Berserk is all but required for the AI to use their heavy hitter in a
  516. chain (or even outside of a chain). Without it, they simply won't have
  517. enough Fury to do so, at least not with anything resembling consistency.
  518. - Because the game considers Charge and Aerial to be normal attacks,
  519. AI-controlled characters have trouble using them in a cancel chain.
  520. - The AI won't use elemental waza or magic on an enemy if the damage is
  521. nullified or absorbed unless it's in a chain (Attack level doesn't matter).
  522. - If a character is equipped with an elemental weapon, the AI will attack
  523. enemies normally even if the damage is nullified or absorbed, but they'll
  524. prioritize attacking enemies who aren't resistant, if there are any.
  525.  
  526. - Self-preservation: The AI will disengage and avoid the enemy if they're
  527. using any AI setting besides AWAYM, their Defense skill is at least Lv2,
  528. and their health falls below a certain threshold. They'll start attacking
  529. again either after one minute has passed or if they're healed above the
  530. threshold. If the timer expires, further damage will not re-trigger
  531. self-preservation unless the character is healed above the threshold.
  532. The timer will keep running even if you switch to control the character,
  533. but will reset if you change AI settings in any way.
  534. - These thresholds are:
  535. a. <17,5% HP
  536. b. <x+5% HP, where x is the amount of damage received that was between
  537. 1/8 and 2/3 mHP.
  538. c. An MP threshold that equals mHP/20 + mMP/16. At Lv255, these are:
  539. 3790 | Cliff, Roger
  540. ~3500 | Mirage, Fayt, Albel
  541. ~3350 | Nel, Peppita, Adray
  542. 3015 | Sophia, Maria
  543. d. c + (dmg/MP - 0,05)*MP
  544.  
  545. - There's no upper limit to the MP threshold, so it's very possible for
  546. it to be higher than the character's max MP (at least until you max out
  547. the MP skill).
  548. - Again, I highly recommend keeping Defense at Lv1, so you can use Well-
  549. Balanced or FYA without having to worry about the MP threshold. The HP
  550. threshold can be an issue as well. It's all well-intentioned, but in
  551. practice, it doesn't quite work. Against weaker enemies, you should have
  552. little trouble healing the character in time even if they don't disengage,
  553. whereas against tougher enemies, it can be a huge pain in the ass to keep
  554. your health figures above the thresholds.
  555. - When using an AI setting besides AWAYM, the AI will stop using waza when
  556. below 20% HP (even if it consumes MP, not HP).
  557. - You can press L1 and R1 to switch the character you control, in which
  558. case the AI will immediately take over the PC you switched away from
  559. (unless they're set to Manual / Do Nothing). Pressing R2 during battle
  560. will toggle the character's tactics setting between Manual (Do Nothing)
  561. and AI.
  562. - I play large parts of the main game without using the AI at all, not
  563. just because of how ineffective the AI is below Attack Lv10, but also
  564. because it gives me more stuff to do, more action. I would *not* recommend
  565. this all-manual approach to first-time players, however (except when
  566. otherwise noted).
  567.  
  568. - Mage AI settings:
  569. 1. Act in a well-balanced manner
  570. 2. Concentrate on healing/recovery
  571. 3. Concentrate on attacking
  572. 4. Support your party
  573. 5. Don't use symbology (or battle skills)
  574.  
  575. - No healing or status recovery spells on settings 3 and 4.
  576. - No support spells (Power Up, etc.) on settings 2 and 3.
  577. - On setting 3, the AI prefers to cast offensive magic normally rather
  578. than use anything set as a battle skill.
  579. - When it comes to attacking, mages have no override variables.
  580. - If a mage's Defense skill is at least Lv2, they'll move away from
  581. nearby enemies who are targeting them (the detection range is the size
  582. of the AOE of Blood Scylla). If the mage's Attack skill is also at least
  583. Lv2, they'll also use some sidesteps to get away from the enemy instead
  584. of just normal movement. This isn't really an improvement, so you should
  585. consider keeping the mage's Attack skill at Lv1. Either way, the mage
  586. can easily end up trapped against the wall, as they don't really try to
  587. circle around the enemy.
  588. - As if that wasn't bad enough, there's also the issue of mages spacing
  589. out. If a mage is trying to get away from an enemy while a flag for a
  590. spell is active, there's a solid chance the AI will space out and fail
  591. to cast the spell even if the enemy's no longer close or even pursuing
  592. them. It's even more likely to happen if the character's health self-
  593. preservation has been triggered. After a while, they'll snap out of it,
  594. but you really don't want to wait. Fighters can space out the same way
  595. as well, but it's not as likely (unless they're in self-preservation).
  596. - The practical upshot of all of this is that you simply can't rely on
  597. the AI to keep you healed. Then again, even without the above issues,
  598. it would still hardly be ideal, as it's often quite dangerous to hang
  599. around 33-50% HP. It would also negatively impact No Guard.
  600.  
  601. - When a flag for a healing or support spell is set, the AI tends to
  602. respond very quickly. However, if the AI is interrupted when casting a
  603. support spell, the flag will already be gone, and, as such, the AI won't
  604. try again (unless the flag is recreated). If a healing spell is interrupted,
  605. it might take a little while before the character tries again, but the
  606. healing target doesn't need to take any more hits.
  607. - If you're familiar with the conditions for casting spells, it's possible
  608. to keep your support character away from the enemy (on Manual) and control
  609. another character while still receiving support without manually choosing
  610. the spells; Switch to the support character and turn the AI on, switch
  611. back, then back again to turn the AI off, then back once more.
  612. - If you're using Maria as a healer instead of Sophia or Adray, you can
  613. generally expect her AI to do a pretty good job at healing (so long as
  614. Power Up and Angel Feather are disabled).
  615.  
  616. - Healing spells
  617. × A character becomes a valid target for a healing spell if
  618. a. the character's HP falls below 1/3, or
  619. b. the character's HP falls below 50% and the character has received
  620. damage that is greater than 10% of their max HP at some point during
  621. a given battle.
  622. × Faerie Light will be used instead of Healing if
  623. a. there's more than one valid target, or
  624. b. Healing is disabled.
  625.  
  626. - Support spells: Once a condition for a support spell or spells is met,
  627. it sets a casting flag that will remain in effect for the rest of the
  628. battle (meaning the character will always re-cast the spell(s) once the
  629. effect wears off).
  630. - The AI will cast ATP boosting spells if a character deals damage that's
  631. below a certain threshold.
  632. a. Less than 1/32 mHP: Power Up.
  633. b. Less than 1/24 mHP: Angel Feather.
  634. × These overlap, so triggering a also triggers b, causing the AI to cast
  635. Angel Feather in addition to Power Up, even though it can't boost the
  636. target's ATP any further.
  637. × Echo damage and fireworks are ignored.
  638. × MP and MP damage are not taken into account. As such, attacks that
  639. deal MP damage only will trigger the flags, since they deal 0 HP damage.
  640. - A flag for DFP boosting spells (Protection, AF) can only seem to be set
  641. in response to attacks that deal MP damage. However, most enemies either
  642. don't have attacks that deal MP damage or don't have attacks that deal
  643. *enough* MP damage. The enemy's max MP also seems to be a factor. All in
  644. all, there are only a handful of enemies that can trigger the flag. As
  645. such, I highly doubt it works as intended.
  646. - Support spells won't take effect if the character is knocked down when
  647. hit by the spell.
  648. - The AI will cast Acid Rain if the mage itself has Power Up in effect and
  649. deals less than 1/30 mHP damage to an enemy. This doesn't occur with all
  650. enemies.
  651. - The AI will cast Silence on most enemies that are currently capable of
  652. casting magic (ie. the spell isn't locked behind a health threshold), but
  653. not if it's a fighter set to AWAYM. The AI doesn't care if the target is
  654. immune and, as such, can easily end up casting it in vain.
  655. - The AI will cast Gravitation on some of the fastest enemies (Centaur
  656. Statues, Imps). Even when it's used, it's used very inconsistently.
  657. - Furthermore, Acid Rain, Silence and Gravitation are only used by the
  658. AI if the enemy party is at a higher level than your party.
  659. - I've never seen the AI cast Reflection.
  660. - The flags for Power Up, Angel Feather and Acid Rain can't trigger if
  661. the attack deals no damage. On the other hand, the flags *can* trigger
  662. from magical damage (which seems like an oversight).
  663.  
  664.  
  665. Enemy AI
  666.  
  667. - Enemies are generally more likely to use unblockable (Major) attacks
  668. when they haven't received any hits from the character they're targeting
  669. during or since their previous action, and blockable (Minor) attacks when
  670. they have. Enemies also tend to switch to blockable attacks if they manage
  671. to break your guard.
  672. - When trying to predict which attack the enemy is going to use, you can
  673. possibly eliminate certain moves based on how close the enemy is trying
  674. to get to you.
  675. - Enemies are likely to target a character casting a spell or using an item
  676. as a result of an element I've dubbed 'magic attract/item attract,' which
  677. has an area of effect that is slightly larger than the AoE of Explosion.
  678. - Using magic attract to intentionally distract the enemy is certainly
  679. an option.
  680. - Some enemies are susceptible to stealth, ie. they're unable (or, rather,
  681. unlikely) to lock on to moving characters or characters that are in the
  682. middle of performing an action. On 4D, every enemy is susceptible. Below
  683. 4D, a good number of enemies are susceptible, although effectiveness varies.
  684. - Enemy behavior changes when their HP or MP falls below certain thresholds
  685. (usually 60%, as seen in the enemy move list). Typically, this means gaining
  686. access to additional, generally more powerful, attacks.
  687. - Most enemies have an 'anti-backstab' attack that they may use when you're
  688. performing actions or simply situated roughly behind them. If you were to
  689. imagine the enemy to have 180 degree field of view, then anyone outside of
  690. that FoV would be considered 'behind' them. How likely an enemy is to use
  691. their anti-back attack varies depending on the enemy.
  692. - Enemies are unlikely to cast a spell if the damage is either nullified
  693. or completely absorbed.
  694. - 4D: If an enemy is hit multiple times in a short amount of time, the
  695. enemy will enter a state during which they'll usually only use blockable
  696. attacks and will ignore stealth until they manage to hit someone. I guess
  697. we should have a name for this state. Er, how about... miffed?
  698.  
  699.  
  700. Force of impact & Hitstun
  701.  
  702. - One of the key elements driving power dynamics in many melee action
  703. games, including Star Ocean, is the hitstun caused by attacks and how
  704. it interrupts any possible current action and makes the target unable
  705. to act until they recover. Previous installments employed very simple
  706. hitstun mechanics, wherein it was possible for a subject - player or
  707. enemy - to be so overwhelmed by rapid, consecutive attacks that they
  708. would simply not be able to recover, resulting in what is known as a
  709. stunlock.
  710. - In addition to the limitations imposed by Fury, blocking, and chaining
  711. restrictions, SO3 rebalances stunlocking even further by employing
  712. hitstun RNG, wherein your attacks have varying force values and enemies
  713. have varying force/hitstun resistance values. The higher the resistance,
  714. the less likely your attacks are to result in hitstun. Bosses always
  715. have high resistance, whereas normal enemies with high resistance become
  716. more common as you progress through the game. Your average, normal enemy
  717. can still easily be stunlocked by a single character using a chain, up
  718. until the character runs out of Fury, gets blocked, or gets hit by another
  719. enemy. A single successful chain is often all it takes, however.
  720. × I wish I could provide actual, hard numbers on the force values, but,
  721. sadly, no, no such data is available. The amount of damage certainly
  722. has no impact on the calculation (when it's above 0).
  723. - While your characters have no native resistance to hitstun, by using
  724. the absolutely vital No Guard support skill, a character will be able
  725. to avoid hitstun so long as the damage is physical in nature and the
  726. amount of damage incurred doesn't exceed a value that is 1/15 of the
  727. character's current HP. Eg. if a character has 15 000 cHP, any physical
  728. attack dealing less than 1001 pod will not cause them to flinch. In
  729. practice, this generally allows you to shrug off blockable attacks, most
  730. of which have a 0,8x damage multiplier and which, indeed, the enemy is
  731. most likely to respond with when you attack them. While No Guard comes
  732. with a heavy CP cost of 5, it is well worth it.
  733. × No Guard always works for attacks that deal MP damage only.
  734. × With a Blue Talisman, it's possible to resist flinching even when your
  735. HP isn't high enough. Particularly useful on higher difficulty levels.
  736. × No Guard ignores Convert Damage (which converts HP damage into MP
  737. damage or the other way around),
  738. - Not all attacks are interrupted if the subject is interrupted.
  739.  
  740. - The effects of force of impact can basically be divided into seven
  741. different kinds:
  742.  
  743. × Flinch. The most common type. The (possible) result of most attacks
  744. in the game. The most common flinch duration for enemies is 1,0s.
  745.  
  746. × Knockdown. The target is knocked off their feet. When a subject is
  747. knocked down, they cannot be damaged until they're back up. This is
  748. often bad news if you're in the middle of a chain or a waza with
  749. multiple hits (depending on how fast the enemy gets back up). The
  750. invincibility extends slightly beyond the recovery animation.
  751. × Your characters recover from knockdown in about 2 seconds with very
  752. minimal variation between different characters. Enemies have more
  753. variation, but it's still around 2 seconds most of the time.
  754.  
  755. × Float. The target is launched into the air. When they hit the ground,
  756. they will bounce a little bit before entering knockdown state (similar
  757. to Virtua Fighter). If a floated subject touches the boundaries of the
  758. battlefield or another subject, they will enter knockdown state. While
  759. in the air, enemies are unable to resist hitstun and can potentially be
  760. 'juggled' for an extended period if you land further, successive hits
  761. with the float property. Some multi-hit attacks do this natively. However,
  762. if a floated enemy is hit by an attack that causes regular flinch, the
  763. enemy's floated status is canceled (and there's no knockdown on landing)
  764. and their hitstun resistance becomes active again.
  765. × Floating can occur in varying degrees depending on the attack used.
  766. Indeed, in some cases, the effect is so minimal that it's practically
  767. just a knockdown (take Hammer of Might, for instance).
  768.  
  769. × Blocking. A subject will always flinch when they block an attack. The
  770. only action it's likely to interrupt is casting a spell.
  771.  
  772. × Getting blocked. Most blockable attacks are interrupted when blocked.
  773. The ones that are not are usually of the energy projectile / blast variety.
  774.  
  775. × Body impact. Occurs if a subject falls on or is pushed against another
  776. subject.
  777.  
  778. × Parrying (see below)
  779.  
  780. - The actual flinching animation is the same in some of the above cases.
  781. - If an attack causes knockdown or float, the enemy may semi-resist it,
  782. resulting in a regular flinch.
  783. - If an attack stuns a subject, the knockdown/floating properties of
  784. the attack are ignored.
  785. - Offensive items (Fire Crystals, bombs) always cause hitstun.
  786. - For some reason, items and spells that increase your stats or grant
  787. special conditions also seem to be affected by knockdown invincibility.
  788. - You won't flinch when taking physical hits from an enemy whose ATP
  789. is lower than your DFP or if the attack is elementally nullified or
  790. fully absorbed.
  791.  
  792.  
  793. Parrying
  794.  
  795. - Parrying is the possible result of a Hit (Dex) vs Evade (Agi) roll.
  796. The formula still seems to be one used since 1995: (Evade - Hit)/255.
  797. When an attack is parried, no damage occurs, although the subject that
  798. parries will flinch (although enemies will only flinch if the attack had
  799. caused them to flinch if the attack hadn't been parried). On Earth and
  800. Galaxy, parrying only really occurs if there's a significant level gap.
  801. - Parrying is not possible when attacked from behind or when using certain
  802. waza. It also won't occur if the attack breaks the target's guard.
  803.  
  804.  
  805. Frame Advantage/Disadvantage
  806.  
  807. - A faster attack may beat a slower attack on an equal footing, but
  808. rather than try to beat the enemy in raw attack speed - which may not
  809. even be enough due to force resistance - you should strive to create
  810. situations where you have a more significant frame advantage (not that
  811. anyone is actually counting frames when it comes to SO3), such as after
  812. baiting the enemy into attacking (ie. feinting) and then avoiding the
  813. attack. Indeed, the simple whiff punish will likely be the single most
  814. common offensive tool you'll utilize to start your chains. Blocking and
  815. sidestepping are other options, as is simply attacking an enemy currently
  816. targeting another character. With magic attract, you can easily distract
  817. enemies that were just targeting you a second ago. Again, due to hitstun
  818. resistance (and blocking), having the advantage doesn't necessarily
  819. guarantee a successful chain, but it does still increase your odds of
  820. success.
  821. - Observe the enemy to get familiar with their attacks. Learn when and
  822. from which directions they're vulnerable. Practice some sidestepping
  823. while you're at it. Check the enemy move list for data like damage
  824. multipliers and health thresholds. There are over 400 enemies, with many
  825. enemies belonging in a certain family. Enemies in the same family have
  826. mostly, if not completely, identical movesets, but even then, the same
  827. move may have different attributes between two members. Eg. a move may
  828. be blockable for one and unblockable for another.
  829. - A higher movement speed is, of course, a significant advantage. You
  830. can increase your movement speed at most by 30% with the help of either
  831. a Ring of Haste or Bunny Shoes.
  832. - Being low on Fury doesn't necessarily serve as a disadvantage for the
  833. enemy, since, as already mentioned, enemies have at least one attack they
  834. can still use even at minimum Fury and they don't have to pull off chains
  835. like you do. Also, enemies with high force resistance can recover Fury
  836. at full speed even as you're attacking them.
  837. - When needed, you can use feinting and sidestepping to get the time you
  838. need to recover Fury. Another option is Max Fury, which will randomly
  839. fill the character's Fury to 100 when on neutral, but, like I said, it's
  840. usually mutually exclusive with No Guard, and No Guard is much more useful
  841. for general purposes. Either way, it would be more useful for the AI, not
  842. just because of their poor Fury management, but also because they can
  843. react to Max Fury activating at speeds that humans can't.
  844.  
  845.  
  846. Stats
  847.  
  848. Hit Points (HP)
  849. Magic Points (MP)
  850. Strength (Str) | Base Attack Power (ATP)
  851. Constitution (Con) | Base Defense Power (DFP)
  852. Agility (Agi) | Base Evade
  853. Dexterity (Dex) | Base Accuracy/Hit
  854. Stamina (Stm)
  855. Capacity Points (CP)
  856. Skill Points (SP)
  857.  
  858.  
  859. Damage Calculation
  860.  
  861. - The physical damage calculation formula looks something like this:
  862.  
  863. ((ATP - DFP)(d + i)bmachsr)e
  864. d: Basic multiplier (typically increases with proficiency)
  865. i: Increase HP/MP Damage bonus
  866. b: Berserk multiplier (1,3)(HP only)
  867. m: Major multiplier
  868. a: Cancel bonus multiplier (1,75; 2,0; 2,5; 3,0)
  869. c: Critical hit roll a (Critical Hit HP/MP (HP: 1,5; MP: 1,2)
  870. h: Critical hit roll b (Critical Hit)
  871. s: Stun multiplier (2,0)(vs. enemies only)
  872. r: Random variable
  873. e: Elemental multiplier (1,0; 2,0; 0,5; 0; -1,0)
  874.  
  875. - Put simply, the random variable increases HP damage at most by approx.
  876. 12,5% and MP damage by about 6%.
  877. - During battle, ATP can be affected by the following (maxes out at 9999).
  878. Power Up (1,5)
  879. Angel Feather (1,2)
  880. Might Tablets (1,2; 1,4)
  881. Power Dance
  882. Anger (2,0)
  883.  
  884. × If Angel Feather is in effect, casting Power Up will replace the 1,2
  885. with 1,5.
  886. × Might Tablets remain in effect for the rest of the battle even if the
  887. character is killed. The others are temporary (unless you have Auto-Anger
  888. equipment).
  889. × As before, Anger may be triggered when an ally dies. It lasts 45 seconds.
  890.  
  891. - During battle, DFP can be affected by:
  892. Protection (1,5)
  893. Angel Feather (1,2)
  894. Acid Rain (0,5)
  895. Reducer (0,7)
  896.  
  897. - Enemies' critical hits have a small chance of inflicting Stun.
  898. - Your characters cannot perform critical hits natively, while the enemy
  899. can. Critical hits from the support skills Critical Hit HP/MP don't have
  900. a chance of inflicting stun. Enemies have varying critical hit rates, with
  901. 8% being the most common. A few of them are as high as 34%. The critical
  902. hit multiplier for enemy attacks is 4/3.
  903. - The basic multipliers for normal attacks used by enemies are usually
  904. 0,8 for blockable attacks and 2,0 for unblockable ones (as seen in the
  905. enemy move list).
  906. - Enemies generally don't have all that much DFP. Even late in the
  907. post-game, you're usually looking at figures between 50 and 200.
  908.  
  909. - If an attack has multiple elements, higher level resistance takes priority
  910. over lower level resistance (weak < halve < immune < absorb).
  911. - However, due to a programming error, neutral resistance will take priority
  912. over anything else if it occurs later in the damage calculation sequence.
  913. The four elements are processed in this order: Earth, Water, Fire, Wind.
  914. Consequently, Wind neutrality takes priority over any other elemental
  915. resistance, Fire neutrality takes priority over Earth and Water resistance,
  916. and Water neutrality takes priority over Earth resistance.
  917. - Ultimately, the bug is neither particularly useful nor harmful, and a lot
  918. of that has to do with how unreliable elemental attacks are to begin with.
  919.  
  920.  
  921. Death
  922.  
  923. - Death, or 'incapacitation,' occurs when either HP *or* MP is reduced to
  924. 0. Petrified characters are also considered dead, but paralyzed characters
  925. are not (Paralysis now wears off after a while).
  926. - The game uses the following colors to indicate damage and healing figures:
  927. White | HP damage
  928. Green | HP healing
  929. Red | MP damage
  930. Blue | MP healing
  931. - If a character is HP killed by an attack that deals both HP and MP damage,
  932. no MP damage is sustained.
  933. - When using attacks that deal both HP and MP damage, you can easily tell
  934. whether you performed an HP or MP kill, as the MP damage will not be visible
  935. in the event of an HP kill.
  936. - There are plenty of normal enemies on Disc 1 and Disc 2 post-game that
  937. are vulnerable to an MP kill (those being enemies with an HP:MP ratio
  938. well above 10:1), potentially making an MP kill (much) faster than an
  939. HP kill. However, you also need to take your whole team's damage output
  940. into consideration. If you have two or three fighters engaging the same
  941. target, and only one of them is doing (significant) MP damage, the result
  942. could easily be an HP kill. Later in the game, the old MP killers are
  943. easily outclassed by the characters' best moves, despite mostly being HP
  944. damage only. It doesn't even matter that only about 10 enemies on Disc 2
  945. main game (outside of the Arena) are particularly vulnerable to MP damage.
  946. Whether the enemies have low MP or not, the MP killers just can't compete
  947. with the sheer dps and stopping power of the best waza.
  948. - Enemy attacks only have a limited chance of actually killing you when
  949. you sustain lethal damage. The odds vary, but are generally pretty high.
  950. If the roll fails, the character is left with 1 HP/MP. Having that little
  951. health doesn't affect the roll in any way, so characters can potentially
  952. survive multiple lethal hits consecutively.
  953. - If a subject is killed while one of their attacks is still active, the
  954. attack will become harmless.
  955.  
  956.  
  957. Healing
  958.  
  959. - The most common healing items:
  960.  
  961. Blueberries | 30% HP Physical Enhancer | 50% HP
  962. Blackberries | 30% MP Mental Enhancer | 50% MP
  963. Fresh Sage | Revive w/30% HP/MP Analeptic | Rev. w/30% (all)
  964. Ripe Berries | 30% HP (all) Aquaberries | Poison
  965. Perfect Berries | 60% HP (all) Basil | Paralysis
  966. Magical Berries | 90% HP (all) Sage | Petrification
  967. Lavender | Freeze
  968.  
  969. - Enhancers and Analeptics become available on Disc 2.
  970. - The multi-target berries are only available in limited numbers.
  971. - There's no item that would heal MP for multiple characters at the same
  972. time (unless they're dead, and you're reviving them).
  973. - The best way to heal moderate amounts of MP is through MP regeneration.
  974. On Disc 1, the only source of MP regeneration is the Regeneration Symbol
  975. accessory, which is dropped by a handful of enemies and can easily be
  976. farmed in the second dungeon.
  977. - Other types of healing items can be created mainly through Compounding.
  978. Many healing items can also be refined to boost their effects, and the
  979. Compounding Elixirs required in the process are readily available at stores.
  980. - There are numerous Food healing items, most of which can be created
  981. through Cooking, but they can only be used outside of battle (with a few
  982. exceptions).
  983. - The support skills First Aid and Standby Healing can also heal you
  984. (both 1 CP).
  985. - Standby Healing heals a small amount of HP (20 at Lv1, 400 at Lv10)
  986. every 4 seconds when on neutral. The amount is far too little, so don't
  987. bother. You can't even level it up easily, as the proficiency gain is
  988. capped at 8 points per battle.
  989. - First Aid gives you a small chance of recovering 20% HP when receiving
  990. physical HP damage. At Lv10, the activation rate is about 10%. A fairly
  991. useful skill if leveled up, but at low levels, it makes little difference.
  992. Fortunately, you can auto-level it easily on Disc 2.
  993.  
  994. - Healing spells:
  995. Lv10
  996. Healing | 1224 | Heal 30-38% HP (Lv1) / 80-87% HP (Lv10)
  997. Faerie Light | 1224 | Heal 33-36% HP (all) (Lv1) / 60-66% HP (all)(Lv10)
  998. Restoration | 269 | Revive w/ 10% HP/MP (Lv1) / 50% HP/MP (Lv10)
  999. Antidote | - | Heal Poison
  1000. Cure Condition | - | Heal Poison, Paralysis and Petrification
  1001.  
  1002. - Healing spells gain proficiency only when cast during battle.
  1003. - Boosting your healing spell levels is helpful, but hardly necessary
  1004. (at least on lower difficulty levels). You can do it if you feel like it.
  1005. - Don't forget that casting spells consumes Fury like any other action.
  1006. - The two mages, Sophia and Adray, are the only characters who can learn
  1007. advanced healing magic. Nel is the only fighter who natively has Healing.
  1008. - You can teach Healing and Antidote to any fighter by using one of the
  1009. four Decrepit Tomes found throughout the game (two very early). To use
  1010. the spells during battle, you need to set Common Support Symbols as a
  1011. support skill (2 CP).
  1012.  
  1013. - Hypothetically, if you needed to heal your whole party non-stop, items
  1014. and magic (ie. Faerie Light) would be roughly equally effective, both
  1015. allowing you to heal every 5 seconds (with minimized casting time). Both
  1016. methods have their advantages and disadvantages.
  1017.  
  1018. Items
  1019. + Can be used by anyone.
  1020. + Locks you in place for a shorter period of time.
  1021. +/- Item attract
  1022. - Limited supply, especially for 60% and 90% heals.
  1023. - Need to be created/refined.
  1024.  
  1025. Faerie Light
  1026. - Can only be used by Sophia and Adray.
  1027. - Needs to be leveled up to reach full potential.
  1028. - Locks you in place for a longer period of time.
  1029. +/- Magic attract
  1030. + Unlimited use
  1031.  
  1032.  
  1033. Misc
  1034.  
  1035. - There are only 4 elements: Fire, Water, Wind, Earth, and Heart (?).
  1036. Elemental resistance is common as you can see in the enemy list. As
  1037. such, elemental attacks should not be used indiscriminately. If you
  1038. don't want to worry about it, just don't use any.
  1039. × Lightning is considered part of the Wind element. Ice is the same
  1040. as Water.
  1041. - There are no spells or actions that freeze time
  1042. - Body armor is the only type of armor in the game. There are no more
  1043. shields, helmets, etc. Armor is largely split into three categories:
  1044. light, medium, and heavy. Each character can only equip armor of one
  1045. of these types.
  1046. - Exp is still divided among active party members.
  1047. - The command menu during battle is rather poorly designed, as not all
  1048. commands are visible at a given time. Well, technically they are, but
  1049. because of the translucency effect, they're difficult to read. In any
  1050. case, the six commands are:
  1051. Escape
  1052. Tactics
  1053. Tactical Skills
  1054. Equipment
  1055. Items
  1056. Symbology (default)
  1057. - You still can't enable or disable spells during battle.
  1058. - You can't switch party members mid-battle.
  1059. - The following actions have a 5 second cooldown during battle: using
  1060. an item, changing equipment, and using a Tactical Skill action (Taunt
  1061. or Scan Enemy).
  1062. - As mentioned, items are sorted alphabetically during battle, which is
  1063. *far* from ideal. You also can't see the effect of an item until you
  1064. select one to bring up the sub-menu, and even then, it only shows the
  1065. effect of the currently highlighted one. If you've done some refining,
  1066. you could easily have copies of the same item with different effects.
  1067. To avoid cluttering up your inventory, you should get rid of items that
  1068. you have no use for (Fire Crystal, Eldritch Fire Stone, Battle Sphere,
  1069. Reducer, etc.).
  1070. - In a given battle, the game remembers the last selected item on an
  1071. individual character basis.
  1072. - Stamina is now a hidden stat. Post-battle recovery rate is remaining
  1073. Stamina divided by 12 when below 6500 HP and 400 MP, and Stamina / 18
  1074. when above (they change independently).
  1075. - The recovery maxes out at 2000 HP and 500 MP. Post-battle recovery is
  1076. really not that important this time around, since battle skills generally
  1077. consume HP instead of MP.
  1078. - Like before, there are a number of different formations to choose from,
  1079. 10 to be exact. The formation menu is also where you can change the default
  1080. controlled character.
  1081. - There are no random encounters. Instead, enemies are visible on the
  1082. field, and you'll be drawn into a battle when you come into contact with
  1083. one. Enemies will usually pursue you when you get close, but some of
  1084. them are "blind" and will not react to your presence.
  1085. - Each 'field enemy' can usually give you one of two or three different
  1086. encounters (possibly including the same set of enemies in a different
  1087. formation). These encounters are rolled when you enter an area.
  1088. - If you run away from a battle, Fayt will be flashing for 3 seconds,
  1089. during which time you can touch enemies without triggering a battle.
  1090. - The time it takes to escape from battle is defined by the difference
  1091. between your active party's average level and the enemy's average level.
  1092. At equal levels, it takes 2 seconds to run away. For every level the
  1093. enemy is above yours, the time required increases by about 0,25 seconds,
  1094. up to a maximum of 7 seconds. Conversely, being just a few levels above
  1095. the enemy will drop the required time down to a minimum, which is about
  1096. a second.
  1097. - Characters temporarily immobilized by a status ailment won't be able
  1098. to escape until they recover.
  1099. - When you run away from battle, all spoils are forfeit.
  1100. - Careful not to select the Escape command accidentally.
  1101. - Some enemies (mainly bosses) have 'boss benefits' that make them immune
  1102. to Fury damage, status ailments and special stun effects, and partially
  1103. immune to scan.
  1104. - Spectacles have been replaced with the Scan Enemy tactical skill. It no
  1105. longer gives you the HP and MP values of bosses. Any level of elemental
  1106. resistance is simply referred to as 'resistant.'
  1107. - An enemy that can drop two different items can technically drop both
  1108. of them at the same time.
  1109. - Impact freeze: Time freezes during battle for a small fraction of a
  1110. second (~0,05-0,2s) when any of the following actions occur and it involves
  1111. either your controlled character or an enemy getting hit by your controlled
  1112. character: flinching, blocking, parrying, critical hits, guard break. Not
  1113. all attacks cause freezing when flinching occurs. Command input for battle
  1114. skills still registers during the freeze, which is why it can help you
  1115. with tricky skip-cancels.
  1116. - Because of all the random variables at play and your own (possibly
  1117. varying) actions, the same battle can play out in many different ways
  1118. even if you're using the exact same setup. Once you factor in all the
  1119. different characters and different skills, the posibilities are endess.
  1120.  
  1121.  
  1122. Status Ailments
  1123.  
  1124. - Stun: Unable to act. Fury drops to 0 but immediately starts to recover
  1125. at normal speed. Lasts 5 seconds. Removed if hit, and that hit will do
  1126. double damage on enemies.
  1127. - Poison: 4,166% (1/24) every 3 seconds in battle, 0,5% on the field.
  1128. - Paralysis: Unable to act. Lasts 16 seconds (resets at the end of a
  1129. battle or if killed).
  1130. - Freeze: Unable to act. Lasts 6 seconds. Most physical attacks cause
  1131. Instant Death on a frozen subject. Enemies may be resistant to being
  1132. shattered. An attack can't shatter a subject if it's an attack that
  1133. causes freezing.
  1134. - Petrification: Unable to act.
  1135. - Confusion: The subject moves randomly without doing anything else
  1136. while losing some HP and MP (1/45 mHP, 1/90 mMP, 5 times). Lasts 9
  1137. seconds. May disappear if the character is hit. If a character is
  1138. confused mid-chain, they're still able to continue the chain.
  1139. - Silence: Unable to cast spells through the Symbology menu (can cast
  1140. spells set as battle skills). Lasts 16 seconds
  1141. - Instant Death: Instant HP death. That's it. Not exactly an ailment,
  1142. but it's sort of related.
  1143.  
  1144. - Similar to before, many enemies have a chance of inflicting status
  1145. ailments with their attacks, but this time it's mostly limited to specific
  1146. attacks.
  1147. - Even if you can't see the character, you can tell when a character
  1148. has an ailment, as an icon is displayed on top of their portrait.
  1149. - Poison, Paralysis and Petrification are not removed at the end of a
  1150. battle, the others are.
  1151. - Aside from Stun, each ailment will remain on a character if they are
  1152. killed (Freeze being a possible exception; Freeze will remain if the
  1153. PC is killed by an attack that can't shatter them). You can't heal the
  1154. ailments of a dead PC.
  1155. - Equipment can protect you from the following ailments: Stun inflicted
  1156. by critical hits, Poison, Silence, Paralysis, Freeze, and Petrification.
  1157. - Using a Medicine Bottle will protect you from up to five status ailments,
  1158. starting with Poison. The effect lasts until the end of battle.
  1159. - You don't have to worry about Petrification as much as you did in
  1160. previous installments.
  1161. - A physical attack will not cause a status ailment if it deals no damage.
  1162. - Water-elemental spells can still freeze a subject even if the damage
  1163. is nullified or absorbed.
  1164. - Most enemies can be frozen and, thus, can easily be freezekilled.
  1165. - The only way to petrify an enemy is by using an item.
  1166.  
  1167.  
  1168. Characters
  1169.  
  1170. - There are 6 mandatory characters and 4 optional characters.
  1171. × Mandatory: Fayt, Cliff, Maria, Sophia, Mirage, Adray.
  1172. × Optional: Nel, Albel, Roger, Peppita.
  1173. - You can get two optional characters at most. At least one of Nel, Albel,
  1174. or Roger will join you permanently (at the beginning of Disc 2) in every
  1175. playthrough. By default, this is Nel, but you can have Albel or Roger join
  1176. you instead if you trigger an optional event at the end of Disc 1, Early
  1177. in Disc 2, you'll be given one opportunity to add Peppita to your party.
  1178. If you choose not to, you can get one of the other characters instead.
  1179. - Your active party consists at most of three characters. With 10 different
  1180. characters, this means you can have 120 different character combinations
  1181. for your active party.
  1182. - To find out what characters you should use, you really need to just
  1183. try them all out. Don't get fixated on using only Fayt as your controlled
  1184. character, though. All the characters are good if used skillfully (except
  1185. Maria, who doesn't require any skill).
  1186. - Personally, the only three characters I'd never keep in my active party
  1187. for the entire playthrough are Cliff, Adray, and Maria. Cliff and Adray,
  1188. because they have better alternatives with largely the same abilities.
  1189. Maria, because she's just too slow and I just don't want to use ranged
  1190. attacks that much.
  1191.  
  1192. - Pros and cons:
  1193.  
  1194. Fayt
  1195. + Fastest movement speed
  1196. + Fast item user
  1197. - Doesn't learn decent waza until Lv25 (Shotgun Blast).
  1198. + Air Raid (Lv40) is quite effective.
  1199. - Can't use Air Raid as effectively in the NTSC-versions due to the lack
  1200. of skip cancels.
  1201. - His ultimate weapon is obtained very late in the post-game and isn't
  1202. worth using unless you're feeling obsessive.
  1203.  
  1204. Cliff
  1205. - Lowest MP
  1206. + His mid-range Confirm attack always deals Fury damage.
  1207. - Said attack has the hardest skip cancel timing.
  1208. - Doesn't have any low CP cancel fodder.
  1209. + Can deal great MP damage with Aerial Assault (mainly of use on Disc 1).
  1210. - Largely obsoleted by Mirage (once she eventually joins)
  1211.  
  1212. Nel
  1213. - Has the longest flinch and slowest sidestep of all fighters.
  1214. - Doesn't learn No Guard until Lv40.
  1215. - Third slowest item user
  1216. + Her mid-range Confirm attack has a fair chance of dealing Fury damage,
  1217. whereas the long range one always does.
  1218. + Can do juggling with Kyoumensatsu and ranged HP&MP damage with Kokuyousen.
  1219. - The AI can't make proper use of her long range skills.
  1220. + The only fighter who can cast Healing natively (unless you count Adray).
  1221. - Her strongest main game weapon is elemental.
  1222. + Her ultimate weapon is obtained fairly early in the Sphere.
  1223.  
  1224. Roger
  1225. - Lowest MP
  1226. - Slow movement speed
  1227. + Has the second shortest flinch of all characters.
  1228. + Fastest item user
  1229. + His mid-/long range Confirm attack has a decent chance of dealing Fury dmg.
  1230. + Raging Helmet (Lv50) can deal heavy damage to multiple enemies.
  1231. + Has two fodder moves with special stun (Whirling Heat and Flying Torpedo).
  1232. + His weapons have the highest ATP.
  1233.  
  1234. Maria
  1235. - Lowest HP
  1236. - Slowest movement speed by far
  1237. + Has the shortest flinch and fastest sidestep of all characters.
  1238. + Fastest spellcaster
  1239. + Has a few ranged dps options that even the AI might be able to use well.
  1240. - Using ranged attacks from a safe distance (or the ridiculously powerful
  1241. Scatter Beam) is something of a cop-out and not very exciting.
  1242. + Learns Protection, Power Up and Angel Feather (which you could supplement
  1243. with a Decrepit Tome).
  1244. - Her weapons have the lowest ATP.
  1245. - Her ultimate weapon is obtained fairly late in the Sphere.
  1246.  
  1247. Albel
  1248. - Second slowest item user
  1249. - His SR skip cancel tends not to work if the enemy doesn't flinch.
  1250. - His mid-range Confirm attack and best cancel fodder are Wind-elemental,
  1251. which prevents the AI from chaining when the enemy takes no damage from Wind.
  1252. - His best move, Goumashou / Hand of Doom (Lv45). doesn't combine well with
  1253. other characters' waza.
  1254. + Still a solid character overall.
  1255.  
  1256. Sophia
  1257. - Lowest HP and DFP
  1258. - Slow movement speed & the longest flinch and slowest sidestep of all PCs.
  1259. - Slowest spellcaster
  1260. - Doesn't join until Disc 2 (not that she's really needed before that).
  1261. + Has healing spells...
  1262. - that the AI can't be trusted to use effectively.
  1263. - Offensive magic can only do moderate HP damage at best, and nearly all
  1264. spells are elemental.
  1265. + Offensive magic is still often good for long range interruption
  1266. (especially Thunder Flare).
  1267.  
  1268. Peppita
  1269. - Low DFP, especially later in the post-game
  1270. - Slow movement speed and long flinch
  1271. + Fast item user
  1272. - Doesn't join until Disc 2.
  1273. +/- Can break the game with Power Dance.
  1274. - The AI can't chain any of the dances.
  1275. + The only character with counters / reversals.
  1276. - Her two best moves, Kaboom and Faerie Friend, both have their issues.
  1277. - Her strongest main game weapon can't be obtained reliably (not without
  1278. Bunny Racing).
  1279. - Her 2nd post-game weapon is obtained very late and only has 5 empty slots.
  1280.  
  1281. Adray
  1282. - Low DFP
  1283. - Slow movement speed, long flinch, and godawful acceleration
  1284. + His wazas allow you to deal good MP damage from a distance.
  1285. - All of these wazas are elemental, however.
  1286. + Has healing spells...
  1287. - that the AI can't be trusted to use effectively.
  1288. - Can only set 5 spells as battle skills.
  1289.  
  1290. Mirage
  1291. + Short flinching time
  1292. - Slowest item user
  1293. - Doesn't join until late in the game.
  1294. + Her mid-range Confirm attack always deals Fury damage.
  1295. - Said attack has the hardest skip cancel timing.
  1296. - Doesn't have any low CP cancel fodder.
  1297. + Can use Triple Kick in a defensive Homing setup, if needed.
  1298. + In the post-game, she can do juggling with Infinity Kick, which does both
  1299. good HP and MP damage.
  1300. + Her ultimate weapon is obtained early in the Sphere.
  1301. + Hot
  1302.  
  1303.  
  1304. Battle Bonus
  1305.  
  1306. - Landing hits on the enemy increases the battle bonus gauge at amounts
  1307. that is relative to the growth rate figure seen next to the gauge. The
  1308. growth rate is a value between 0-300%. It's always divisible by 10 and
  1309. drops by 10 points every 3 seconds. The figure it starts off at is
  1310. dependent on the difference between your active party's average level
  1311. and the enemy's average level. For every level you're above the enemy's
  1312. level, the default rate drops by 10%. If the enemy is at a higher level
  1313. than you, the default rate increases as seen below. Average levels are
  1314. included in the encounter list.
  1315. 4+ | 110% 45+ | 210%
  1316. 8+ | 120% 54+ | 220%
  1317. 12+ | 130% 62+ | 230%
  1318. 16+ | 140% 70+ | 240%
  1319. 20+ | 150% 79+ | 250%
  1320. 24+ | 160% 87+ | 260%
  1321. 27+ | 170% 95+ | 270%
  1322. 31+ | 180% 104+ | 280%
  1323. 35+ | 190% 112+ | 290%
  1324. 39+ | 200% 120+ | 300%
  1325.  
  1326. - At 100% rate, it takes 50 physical hits or 100 magical hits to fill the
  1327. gauge. With the bonus +5 factor, it's 26 / 35.
  1328. - Hits that deal no damage won't increase the gauge.
  1329. - When the gauge hits max, you'll obtain one of four beneficial variables
  1330. depending on what type of attack was used last.
  1331. Confirm | Triple Exp
  1332. Cancel | Double Fol
  1333. Confirm waza | Increased chance of item drop
  1334. Cancel waza | Double post-battle recovery
  1335.  
  1336. - The support skill Lucky Star can also be used to fill the gauge.
  1337. - Fighting 5 battles while keeping the gauge intact will add one of the
  1338. other bonuses at random until you have all four of them.
  1339. - The Bonus Battle gauge breaks if...
  1340. × the character you control dies.
  1341. × the character you control is hit by a critical hit (even if no damage
  1342. is taken).
  1343. × you run away from battle.
  1344. × you load the game.
  1345. - Pretty much the only way to reliably maintain the bonus is to keep the
  1346. controlled character away from the action. Earlier in the game, you can
  1347. often afford that, but later you really can't, as your input will be vital
  1348. for survival. Besides, I'm sure you'd rather take part in the action than
  1349. stand in a corner.
  1350. - If the increment rate starts at 0%, then you should probably just move
  1351. on. However, if you really want that bonus, then you can either use Lucky
  1352. Star (available late in the main game) or you can bring in a low level
  1353. character to get your average level down.
  1354. - Because the game considers Charge and Aerial to be normal attacks (more
  1355. or less), using those will give you either Triple xp or Double Fol.
  1356.  
  1357.  
  1358. Battle Trophies
  1359.  
  1360. - Battle Trophies - or just BTs - are obtained by completing various tasks
  1361. and reaching certain milestones during battle. There are a total of 300 of
  1362. them and the (unimpressive) rewards for getting them are listed below.
  1363.  
  1364. 45 (15%) | Second set of costumes / skins (changed in the status screen)
  1365. 75 (25%) | Universe difficulty level
  1366. 120 (40%) | Third set of costumes
  1367. 165 (55%) | Music Mode (accessed through the BT menu)
  1368. 195 (65%) | 4th Dimension (4D) difficulty level
  1369. 240 (80%) | Fourth set of costumes
  1370. 285 (95%) | Full Active Mode (FAM)
  1371.  
  1372. - As already mentioned, the Battle Trophy data takes up 1167 kb of space.
  1373. I suspect the reason it takes up so much space is because of the useless,
  1374. little screenshot that the game takes when you obtain one. You can only
  1375. have one BT data file on one memory card, and it can't be copied. If you
  1376. have BT data files on both memory cards, you have to manually choose which
  1377. one to load whenever you load a save file. (As mentioned, the PS4 version
  1378. automatically creates BT data on both virtual memory cards, and there's
  1379. nothing you can do about it.)
  1380. - I won't be going into detail about many BTs, just a few here and there
  1381. (the BT guide on Gamefaqs already has a lot of good information). These
  1382. notes are collected in the BT Help section in the misc. file along with
  1383. some information on a few additional BTs I don't bring up during the
  1384. walkthrough.
  1385. - Regarding the two BTs you can get from most main game bosses ('Defeat
  1386. (boss) in under x minute(s)' (usually 1) and 'Defeat (boss) without
  1387. taking damage'), the time limit trophy regrettably counts any time you
  1388. spend in the battle menu, whereas the no damage trophy, on the other hand,
  1389. isn't as hard as it sounds. This trophy simply requires that you don't
  1390. take any damage with the character you control. Note that you will lose
  1391. the trophy if you switch to a dead character.
  1392. - In the few cases where the boss is accompanied by normal enemies,
  1393. killing the boss is the only thing required to trigger the BTs. When
  1394. going for the time limit BTs for these bosses, you might actually want
  1395. to switch to Manual targeting for once.
  1396. - The single most time-consuming BT is getting into 50 000 battles. A
  1397. typical playthrough (post-game included) is not likely to give you even
  1398. 2000 battles. If you want to reach 50 000 (semi-)organically, you really
  1399. just have to fight loads and loads of battles, at least 100 battles per
  1400. dungeon. Something along those lines. Aim at 5000 battles per playthrough
  1401. (about 2000 on Disc 1), so it'll take 10 playthroughs. If it sounds like
  1402. too much, then, yeah, just forget it.
  1403. - Note the difference between BT-related stats (number of battles, number
  1404. of button presses, etc.) and the actual BT data file. The stats are tied
  1405. to game save files, *not* the BT data file. The only information in the
  1406. BT data file is which BTs you've obtained, when (although the dates are
  1407. hidden), and the little screenshots. Furthermore, the game technically
  1408. tracks two different sets of BT-related stats: one that ignores whether
  1409. or not you have BT collecting enabled and one that only tracks the stats
  1410. when you *do* have BTs enabled.
  1411. - Here's one hypothetical scenario: You start a new game, don't load any
  1412. stats from a pre-existing save file, and don't load the BT data file in
  1413. the Battle Simulator, but do *have* a BT data file present. You could
  1414. play this save file and increase your battle count, but as soon as you
  1415. load the game for whatever reason, the game will automatically load the
  1416. BT data file as well (unless there are two of them and you choose neither),
  1417. at which point your battle count will appear to reset to 0. That's simply
  1418. because the game is now pulling the battle count from the other set of
  1419. stats, which hadn't increased yet, since BTs weren't enabled.
  1420. - If you disable BT collecting in the Config menu, your battle count will
  1421. appear to freeze, as it can't switch the displayed stat mid-game. Even
  1422. then, it will automatically enable it again when you load the game.
  1423. - You can't get BTs on Easy (Earth) and you can't transfer BT stats from
  1424. an Easy save file to a non-Easy playthrough.
  1425. - Trophy note: You only need to get 80% of BTs for all the trophies.
  1426. This is quite easy. If you're diligent enough, you won't even have to
  1427. do post-game on higher difficulty levels.
  1428.  
  1429.  
  1430. Difficulty Levels
  1431.  
  1432. - By default, you only have access to the lower difficulty levels: Easy
  1433. (Earth) and Normal (Galaxy). Collecting BTs is the only way to gain access
  1434. to the higher difficulty levels, Universe and 4D.
  1435. - Universe is still manageable, but 4D is going off the deep end. If you
  1436. try to fight enemies on 4D, you're probably dead. I'd say the main reason
  1437. is the increased speed (it's not just their movement, their attacks are
  1438. faster as well). Even so, if you're experienced enough with the game, you
  1439. should be able to handle it without resorting to Ori, RD, or stun bomb spam.
  1440.  
  1441. HP MP ATP DFP
  1442. Earth | 0,7 | 0,7 | 0,75| 0,8 |
  1443. Galaxy | 1,0 | 1,0 | 1,0 | 1,0 |
  1444. Universe | 1,5 | 1,5 | 1,4 | 1,4 |
  1445. 4D |~1,8 |~1,8 |~1,85| 1,7 |
  1446.  
  1447.  
  1448. Bugs
  1449.  
  1450. - The game suffers from occasional loading issues. This can result in
  1451. a crash, but it's very rare. At this point, these issues are likely
  1452. exacerbated by the deteriorating condition of the console.
  1453. - Cancel window bug (already covered).
  1454. - Attribute change bug. Some of the attributes of an attack may transfer
  1455. to another attack if the preceding attack is still active when you
  1456. perform another action. Eg. if you use Fuujin and then use a normal
  1457. attack with IHPD or Critical Hit, the Fuujin will gain the effects of
  1458. IHPD or Critical Hit but only for the duration of the normal attack.
  1459. In case of skills with a limited activation rate (like Critical Hit or
  1460. Stun), the activation roll is only made once, and the result then applies
  1461. to all hits during the normal attack.
  1462. - Cancel multiplier reset: The cancel multiplier will reset if you land
  1463. a normal hit on an enemy after canceling. Any contact with an enemy is
  1464. enough (ie. doesn't matter if the attack is blocked or nullified by
  1465. knockdown invincibility). This can only occur with characters who have
  1466. ranged normal attacks, ie. Maria, Sophia, and Adray. While not very likely
  1467. with Maria, it's sadly easily triggered when starting LR chains with a
  1468. normal attack with Sophia or Adray. You can also easily avoid it by
  1469. delaying the cancel, but that means you can't start with a skip-cancel
  1470. (not an issue in NTSC).
  1471. - Charge/Aerial bug: When Charge and/or Aerial are set to both slots, the
  1472. HP and Fury costs of the move can be transferred to the other. This happens
  1473. if you have to move before executing the attack and try to activate the
  1474. other attack before the queued move is executed. Used properly, this allows
  1475. you to increase the length of a chain while also consuming much less HP
  1476. (resulting in similar input as when skip-canceling). I've dubbed this
  1477. 'Hyper Charge.' Another possible (and purely cosmetic) effect is that
  1478. the game displays the other attack's name (ie. Charge becomes Aerial,
  1479. Aerial becomes Charge). (PAL-version only)
  1480. - If you're using Charge or Aerial in a chain, it's possible, although
  1481. unlikely, to end up switching targets mid-chain. Another situation that
  1482. can result in mid-chain target switching is if you end up hitting another
  1483. enemy instead of the intended target. Even then, the target indicator
  1484. remains on the original target.
  1485. - If the AI uses Aura Wall, they won't use any battle skills again
  1486. during that battle unless you take control of Albel and execute some
  1487. other battle skill. Even then, as soon as the AI uses Aura Wall again,
  1488. the issue re-emerges.
  1489. - Neutral element priority bug (already covered).
  1490. - Not really a bug, but some skill descriptions are quite inaccurate.
  1491. - If you equip the Lightstone during a battle in the Bequerel Mine, it
  1492. won't actually register unless you visit the menu or move to another area.
  1493. - There are a few weapons that can't be refined (eg. Crest Gauntlet,
  1494. Fragile Metal Pipe).
  1495. - Jemat's Chain Smash sometimes deals absolutely ridiculous damage, as
  1496. if his ATP was increased tenfold or something.
  1497. - Defeating a beholder-type enemy during Misery Circle has a very small
  1498. chance of triggering a bug where the battle ends, but the beholder is
  1499. still seemingly alive, and you won't gain any xp or fol. Possibly the
  1500. result of receiving lethal damage and being healed on the same frame.
  1501. - It's possible to end up out of bounds, but it's incredibly rare.
  1502. It's never happened to me.
  1503. - Once, I encountered a bug where Confusion didn't wear off and didn't
  1504. do any damage after the character had been killed by Confusion damage
  1505. and then revived.
  1506. - I once saw Sophia cast Explosion even though it was disabled.
  1507. - Ghost target bug: If you kill the AI's target while the AI was casting
  1508. a spell at the enemy and also switch the AI's tactics to FYA, the AI will
  1509. fail to acknowledge that the target is down and will continue casting
  1510. magic at where the enemy used to be.
  1511. - Ghost BT Bug: If you have empty BT data files in both memory cards,
  1512. save BTs to one card, and then to the other during the same session,
  1513. you will end up with a sort of messed up BT data file with "ghost" BTs.
  1514. The total number of BTs will be updated to what it would have been if
  1515. you'd saved to the original slot, but the actual visibly acquired BTs
  1516. will be limited to the BT(s) you obtained in the battle where you saved
  1517. to the other slot. This prevents you from re-triggering the BTs, which
  1518. could make it difficult to discern which ones you're actually missing.
  1519. The bug can easily be triggered on the PS4-version, since it automatically
  1520. creates empty BT data files on both slots. I haven't actually tested if
  1521. it occurs on a real PS2, but it probably does.
  1522. - A mage's AI can become semi-idle if you petrify an enemy mid-attack,
  1523. and the enemy was targeting the mage. The mage will act normally until
  1524. they get too close, at which point they go idle. They're supposed to move
  1525. away from the enemy, but since the enemy is petrified, it messes it up.
  1526. - Faerie Light is misspelled as Fairie Light in the Symbology menu.
  1527. - The Striker's Lightning Blade is misspelled as Lighting Blade.
  1528.  
  1529.  
  1530.  
  1531.  
  1532. e
Add Comment
Please, Sign In to add comment