{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by LahDsai:
2/9/2019 2:40:21 AM
5
[i]Disgaea[/i] comes to mind.
I'd say [i]Final Fantasy Tactics[/i] but you'd have to keep track of character speeds to determine who goes when, which could be a bit of a hassle.
[Edit:] [i]Valkyria Chronicles[/i] would be another amazing tabletop game. Hell, it could practically go unchanged.
English
-
Edited by Rhynerd: 2/9/2019 5:39:10 AMResponse to the edit: I do remember comparing Valkyria Chronicles to this one tabletop skirmish game called Infinity. Probably wouldn’t be too hard to translate that into a Valkyria Chronicles tabletop.
-
Honestly, the character speed tracking sounds kind of like something from Star Wars: X-Wing.
-
"Speed" in [i]FFT[/i] isn't distance over time though, it's time between actions and, as a result, play order. A ninja has a higher speed than a knight, so there's the possibility it could attack twice before the knight could. For example, let's say the ninja's speed is 7 while the knight's is 5. That would make the play order: - Ninja - Knight - Ninja - Knight - Ninja - Ninja - Knight With 5 characters on each side that's a lot of math, particularly when you add status effects like haste, slow, stop, etc. into the mix If you're deciding all your characters' moves in the same phase, then you're taking out a big part of what seperates [i]FFT[/i] from others Tactical RPGs like [i]Disgaea[/i] (which is why I suggested [i]Disgaea[/i] over [i]FFT[/i]).
-
Okay, I see what you mean there. So it would be less like “okay, this unit is the only one with an 8 for speed so they can move first” and more “okay, this unit has an 8 for speed so I can activate them every phase of this combat.”
-
There aren't really "phases" per se. It's more like incrementing each characters turn count by whatever their speed is per each tick of the clock, then figuring out who would reach 100 first (and thusly hold their turn). In the previous example (knight = 5 / ninja = 7) the math would be: - by tick 15 K = 70 N = 105 Ninja takes turn then resets to zero - by tick 20 K = 100 N = 35 Knight takes turn then resets to zero - by tick 30 K = 50 N = 105 Ninja takes turn then resets to zero - by tick 40 K = 100 N = 70 Knight takes turn then resets to zero - by tick 45 K = 25 N = 105 Ninja takes turn then resets to zero - by tick 60 K = 100 N = 105 Ninja speed > Knight speed Ninja takes turn then resets to zero Knight takes turn then resets to zero More simply put, the ninja can take an action every 15 seconds while the knight can every 20 seconds (and the game pauses while someone is taking an action). With 10 characters on you'd need an excel spreadsheet to keep up with who activates in what order and it would need to be adjusted each time someone was hasted (double speed), slowed (half speed) or stopped (no speed) and you'd need to keep track of how many ticks of the clock each status effect would last so you'd know when they wore off. Alternatively, you could have a stopwatch for each character but that would be a hassle. The other option would be to scrap the ATB system in lieu of something else but then you might as well use a game that already uses alternative systems such as [i]Disgaea[/i], [i]X-COM[/i] or [i]Valkyria Chronicles[/i].
