ff6hacking.com wiki

User Tools

Site Tools

You are here: start » ff3 » ff3us » tutorial » events » action
ff3:ff3us:tutorial:events:action

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
ff3:ff3us:tutorial:events:action [2018/05/06 16:16]
lockirby2 [The Actions] 		ff3:ff3us:tutorial:events:action [2019/02/12 10:38] (current)
Line 3: Line 3:
 One question that you may have been asking yourself is "How do I make the characters move?"  Action queues contain a set of actions that you want a character to perform.  For example, you could queue up the actions "walk one step up", "turn left", and "nod head left".  If you set up action queues correctly, you can have multiple characters executing a complex series of actions at the same time.  If you've been following the tutorial so far, action queues will be fairly straightforward to learn. One question that you may have been asking yourself is "How do I make the characters move?"  Action queues contain a set of actions that you want a character to perform.  For example, you could queue up the actions "walk one step up", "turn left", and "nod head left".  If you set up action queues correctly, you can have multiple characters executing a complex series of actions at the same time.  If you've been following the tutorial so far, action queues will be fairly straightforward to learn.
  
-===== Starting an Action Queue =====+==== Starting an Action Queue ====
  
 Starting an action queue works just like executing any other event command, although the number of parameters can vary depending on how many actions you want the character to take.  Any command between $00 and $34 will start an action queue for one character.  The Event Command Document has some information on which character will take action.  This character will fall into one of the following categories: Starting an action queue works just like executing any other event command, although the number of parameters can vary depending on how many actions you want the character to take.  Any command between $00 and $34 will start an action queue for one character.  The Event Command Document has some information on which character will take action.  This character will fall into one of the following categories:
Line 10: Line 10:
   * $10 - $2F: Non-player characters.  Different NPCs will take action depending on what map is loaded.  You can cross-reference the Event Commands Document and FF6LE to figure out which command corresponds to the NPC that you want to move.  According to the Event Commands Document, the $16 command will begin an action queue for NPC 6 in FF6LE.  If you open the LE and select "[014] Narshe, Outside (WOB)", you can see that NPC 6 is a guard on this map.  If you select "[15D] Thamasa, Strago's House", you can see that NPC 6 is a lookalike of Shadow on this map.   * $10 - $2F: Non-player characters.  Different NPCs will take action depending on what map is loaded.  You can cross-reference the Event Commands Document and FF6LE to figure out which command corresponds to the NPC that you want to move.  According to the Event Commands Document, the $16 command will begin an action queue for NPC 6 in FF6LE.  If you open the LE and select "[014] Narshe, Outside (WOB)", you can see that NPC 6 is a guard on this map.  If you select "[15D] Thamasa, Strago's House", you can see that NPC 6 is a lookalike of Shadow on this map.
  
-{{:ff3:ff3us:tutorial:events:action:npc_6_guard.png|}} +{{ :ff3:ff3us:tutorial:events:npc_6_guard.png |}} 
-{{:ff3:ff3us:tutorial:events:action:npc_6_shadow.png|}}+{{ :ff3:ff3us:tutorial:events:npc_6_shadow.png |}}
  
   * $30: The camera.  You can make the camera "walk" around the map, just like any other character.  If you tell the camera to move upwards eight steps, the player's view will shift eight tiles upwards.   * $30: The camera.  You can make the camera "walk" around the map, just like any other character.  If you tell the camera to move upwards eight steps, the player's view will shift eight tiles upwards.
   * $31 - $34: The characters in the party.  Often, the player has the opportunity to pick a party of their choosing, so you won't know what characters are in the party during your event.  By using the $31 command, you can move whomever happens to be leading the party.  Figuring out which character is in the lead (and then moving them manually) would be a lot more difficult.   * $31 - $34: The characters in the party.  Often, the player has the opportunity to pick a party of their choosing, so you won't know what characters are in the party during your event.  By using the $31 command, you can move whomever happens to be leading the party.  Figuring out which character is in the lead (and then moving them manually) would be a lot more difficult.
  
-===== The Second Byte =====+==== The Second Byte ====
  
 The main purpose of the second byte is to tell the game how long the action queue will be.  Most of the time, you should decide what actions you want to put in the queue before filling in this byte.  You can have up to $7F (127 in decimal) actions in a queue, but it's unlikely that you will need anywhere near that many. The main purpose of the second byte is to tell the game how long the action queue will be.  Most of the time, you should decide what actions you want to put in the queue before filling in this byte.  You can have up to $7F (127 in decimal) actions in a queue, but it's unlikely that you will need anywhere near that many.
Line 22: Line 22:
 This byte also allows you to tell the game whether you want to finish the character's actions before moving on with the event.  If you add $80 to this byte (after figuring out how long you want the queue to be), the game will wait for a character's actions to finish before moving on.  Otherwise, the game will not wait.  The latter is useful if you want to make multiple characters move at the same time, among other things. This byte also allows you to tell the game whether you want to finish the character's actions before moving on with the event.  If you add $80 to this byte (after figuring out how long you want the queue to be), the game will wait for a character's actions to finish before moving on.  Otherwise, the game will not wait.  The latter is useful if you want to make multiple characters move at the same time, among other things.
  
-===== The Actions =====+==== The Actions ====
  
 This is the meat of the action queue, containing the actions that you want the character to perform.  There is a list of actions [[ff3:ff3us:doc:asm:codes:movement_codes|here.]]  The vast majority of these are self-explanatory.  Many just tell the character to strike a pose or walk somewhere.  The commands between $C0 and $C4 allow you to change how fast the character walks when they move.  Ignore the commands related to branching or setting event bits for now; these will be covered in later sections of the tutorial. This is the meat of the action queue, containing the actions that you want the character to perform.  There is a list of actions [[ff3:ff3us:doc:asm:codes:movement_codes|here.]]  The vast majority of these are self-explanatory.  Many just tell the character to strike a pose or walk somewhere.  The commands between $C0 and $C4 allow you to change how fast the character walks when they move.  Ignore the commands related to branching or setting event bits for now; these will be covered in later sections of the tutorial.
  
-By default, a character will actually take footsteps when they are told to move somewhere.  If you execute the $80 command (Move character up 1 tile), then the $82 command (Move character down 1 tile), the character will take one step upwards and one step downwards.  If your intention was to make a character float up and down while facing towards the camera, these footsteps would need to be disabled by placing a $C7 command in the character's action queue.  In other words, the middle of your action queue might contain the following commands: CE C7 80 82.+By default, a character will actually take footsteps when they are told to move somewhere.  If you execute the $80 command (Move character up 1 tile) and then the $82 command (Move character down 1 tile), the character will take one step upwards and one step downwards.  If your intention was to make a character float up and down while facing towards the camera, these footsteps would need to be disabled by placing a $C7 command in the character's action queue.  In other words, the middle of your action queue might contain the following commands: CE C7 80 82.
  
-You should also take note of the E0 command.  Delays tend to be very important in action queues because it takes a very short amount of time for characters to strike poses.  Let's say that you want a character to shake their head back and forth.  You may be tempted to alternate between $23 and $63.  Unfortunately, the game will switch between $23 and $63 so quickly that the player won't be able to see it!  Inserting a short delay between these poses will fix the issue.  Instead of using 23 63 23 63, you might want to use 23 E0 01 63 E0 01 23 E0 01 63.  Unfortunately, even the shortest delay ($01) is too long for some purposes.  To create a very tiny delay, we can create four tiny action queues in a row, instead of creating one action queue with all four head-shaking poses in it.  You will see an example of this below.+You should also take note of the $E0 command.  Delays tend to be important in action queues because it takes a very short amount of time for characters to strike poses.  Let's say that you want a character to shake their head back and forth.  You may be tempted to alternate between the $23 and $63 commands.  Unfortunately, the character will alternate so quickly between the "Front, head turned (left)" and "Front, head turned (right)" poses that the player won't be able to see it!  Inserting a short delay between these poses will fix the issue.  Instead of using 23 63 23 63, you might want to use 23 E0 01 63 E0 01 23 E0 01 63.  Unfortunately, even the shortest delay ($01) is too long for some purposes.  To create a very tiny delay, we can create four tiny action queues in a row, instead of creating one action queue with all four head-shaking poses in it.  You will see an example of this below.
  
-All action queues need to be ended with the $FF command.  Once you have finished the body of your queue, don't forget to count how long it is and  fill in the second byte.  The $FF command at the end should also be included in this count.+All action queues need to be ended with the $FF command.  Once you have finished the body of your queue, don't forget to count how long it is and  fill in the second byte.  The $FF command should also be included in this count.
  
-===== Our First Action Queue =====+==== Our First Action Queue ====
  
-It's finally time to fix our problem from earlier.  In order to prevent the event from repeating, we want the party to step off the event tile before the event ends.  We could use $00 to begin an action queue for Terra, but we don't know who will be leading the party when the player steps on the event tile.  If the player were to switch Biggs to the front of the party, our event would fall apart.  Therefore, we should begin the queue with the $31 command.+It's finally time to fix the repetition of the cutscene.  In order to prevent the event from repeating, we want the party to step off the event tile before the event ends.  We could use $00 to begin an action queue for Terra, but we don't know who will be leading the party when the player steps on the event tile.  If the player were to switch Biggs to the front of the party, our event would fall apart.  Therefore, we should begin the queue with the $31 command.
  
 We'll come back to the second byte later. We'll come back to the second byte later.
Line 45: Line 45:
 {{:ff3:ff3us:tutorial:events:action_queue_1.png|}} {{:ff3:ff3us:tutorial:events:action_queue_1.png|}}
  
-===== A Larger Example =====+==== A Larger Example ====
  
-Right now, the event uses a red flash to indicate that the guards are approaching.  To improve on this, we can script some guards to physically approach the party.  Since the battle includes two guards, we want two guards to be part of the event as well.+Right now, the event uses a red flash to indicate that the guards are approaching.  This would be improved if guards were to physically approach the party.  Since the battle includes two guards, we want two guards in the event as well.
  
 As before, our first goal is to determine which action queue to begin.  The guards are NPCs, so we definitely need to use a command between $10 and $2F.  To narrow it down further, we need to look in FF6LE.  It might not be obvious at first glance, but the map that we need to look at is "[013] Narshe, Outside, Beginning (WOB)".  This map is loaded at the beginning of the game, and it is distinct from the map that is usually loaded when you enter Narshe. As before, our first goal is to determine which action queue to begin.  The guards are NPCs, so we definitely need to use a command between $10 and $2F.  To narrow it down further, we need to look in FF6LE.  It might not be obvious at first glance, but the map that we need to look at is "[013] Narshe, Outside, Beginning (WOB)".  This map is loaded at the beginning of the game, and it is distinct from the map that is usually loaded when you enter Narshe.
Line 53: Line 53:
 The NPCs aren't easily noticed because they are all in the top-left hand corner.  Spreading them out, we can see that there are two guards, two dogs, and an old man whose purpose isn't obvious.  Since there are only two guards, it appears that they are reused for all the cutscenes in this area.  We can follow the lead of the vanilla designers and do the same.  Clicking on the guards, we can see that they are NPC #0 and NPC #1. The NPCs aren't easily noticed because they are all in the top-left hand corner.  Spreading them out, we can see that there are two guards, two dogs, and an old man whose purpose isn't obvious.  Since there are only two guards, it appears that they are reused for all the cutscenes in this area.  We can follow the lead of the vanilla designers and do the same.  Clicking on the guards, we can see that they are NPC #0 and NPC #1.
  
-{{:ff3:ff3us:tutorial:events:action:narshe_npcs.png|}}+{{ :ff3:ff3us:tutorial:events:action:narshe_npcs.png |}}
  
 Now we can cross-reference this with the Event Commands Document, which states that we can use $10 to move NPC #0 and $11 to use NPC #1.  We will need to create a separate action queue for each of the two guards. Now we can cross-reference this with the Event Commands Document, which states that we can use $10 to move NPC #0 and $11 to use NPC #1.  We will need to create a separate action queue for each of the two guards.
  
-First of all, we need to move the two guards to the bottom of the screen, which can be accomplished by using the $D5 command in the action queue.  Playing around with the LE and the emulator, I determined that I want to place the guards at (37, 58) and (39, 58).  Then I want the guards to walk onscreen from the south.  You can use the LE to see the tiles that these coordinates point to.  These coordinates become ($25, $3A) and ($27, $3A) when converted to hexadecimal.  The final commands are D5 25 3A and D5 27 3A.+First of all, we need to move the two guards to the bottom of the screen, which can be accomplished by using the $D5 command in the action queue.  By playing around with the LE and the emulator, I determined that I want to place the guards at (37, 58) and (39, 58).  Then I want the guards to walk onscreen from the south.  You can use the LE to see the tiles that these coordinates point to.  These coordinates become ($25, $3A) and ($27, $3A) when converted to hexadecimal.  The final commands are D5 25 3A and D5 27 3A.
  
 Presumably, the guards would be running towards the Magitek Armour, ready for attack.  We should set their movement speed to "fast" with the $C3 command. Presumably, the guards would be running towards the Magitek Armour, ready for attack.  We should set their movement speed to "fast" with the $C3 command.
Line 90: Line 90:
 === Finishing up === === Finishing up ===
  
-Now that we have the action queues themselves sorted out, we need to look at some of the nuts and bolts to make it all work.  Before the action queues are started, the NPCs need to be "created", which presumably loads their data into the game's memory.  This is done with the $3D command.  We also need to use the $41 command to make their sprites visible to the player.+Now that we have the action queues sorted out, we need to look at some of the nuts and bolts to make it all work.  Before the action queues are started, the NPCs need to be "created", which presumably loads their data into the game's memory.  This is done with the $3D command.  We also need to use the $41 command to make their sprites visible to the player.
  
-After the queues have been run, there is one issue to be sorted out.  We want to wait for both guards to reach the player before initiating the dialogue box.  As of yet, we don't know which guard's actions will finish first.  If NPC #0 finishes first, the game will wait for NPC #1 to finish anyways because we added $80 to the second byte of NPC #1's action queue.  However, if NPC #1 finishes first, the dialogue will start before NPC #0 is in position.  You might prefer this as a stylistic choice anyways, but if you don't, you can use the $35 command to wait for NPC #0's action queue to finish before continuing.+After the queues have ended, there is one issue to be sorted out.  We want to wait for both guards to reach the player before initiating the dialogue box.  We wait for NPC #1's action queue to finish before continuing, but we don't wait for NPC #0.  For all we know, NPC #0 will still be walking when NPC #1 finishes moving.  You might prefer this as a stylistic choice anyways, but if you don't, you can use the $35 command to wait for NPC #0's action queue to finish before continuing.
  
 Finally, we want to erase the NPCs after the battle is fought.  We can delete the NPCs using the 3E command.  This should be done before fading in the screen with the $96 command. Finally, we want to erase the NPCs after the battle is fought.  We can delete the NPCs using the 3E command.  This should be done before fading in the screen with the $96 command.
ff3/ff3us/tutorial/events/action.1525623377.txt.gz · Last modified: 2019/02/12 12:52 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki