8,288
edits
XML talk:TRAM: Difference between revisions
m
no edit summary
Paradox-01 (talk | contribs) mNo edit summary |
Paradox-01 (talk | contribs) mNo edit summary |
||
| Line 53: | Line 53: | ||
{| class="wikitable" width=100% | {| class="wikitable" width=100% | ||
|- | |- | ||
! rowspan=2 | names | ! rowspan=2 width=240 | names | ||
! rowspan=2 width=40 | key combo | ! rowspan=2 width=40 | key combo | ||
! colspan=4 | context | ! colspan=4 | context | ||
| Line 288: | Line 288: | ||
If the never used Thrown type can be applied as type 18 the table looks much more complete. "Restoring" forward tackles (face-to-face, src run + tgt run) can be ommitted as the AI would most often stop movement for actual combat? | If the never used Thrown type can be applied as type 18 the table looks much more complete. "Restoring" forward tackles (face-to-face, src run + tgt run) can be ommitted as the AI would most often stop movement for actual combat? | ||
All important header data of STRCOMrun_thw_fw_p and STRCOMrun_thw_fw_pl | All important header data of STRCOMrun_thw_fw_p and STRCOMrun_thw_fw_pl is identical. That means the engine picks the correct TRAM by using an unkown context, possibly this is similar or part of the distiction of "forward" (face-to-face) and "backward" (face-to-back). | ||
: '''Maybe the algorithm checks always tgt's rotation and relative position to src at the same time but for most cases only tgt's rotation (facing) is relevant.''' | : '''Maybe the algorithm checks always tgt's rotation and relative position to src at the same time but for most cases only tgt's rotation (facing) is relevant.''' | ||