[FE8] The grand eventing wiki/chapter construction guide [WIP]


This guide assumes you are already familiar with the basics of hacking


So there’s not really a big post on how to do FE8 eventing (like Arch’s super great guide for FE7), and that kinda sucks for people who want to hack FE8 because there’s far less resources immediately available for them to use.

It’s uh, going to be a hell of a WIP until everything is properly covered. But the general idea is to have a resource similar to Arch’s chapter construction guide except focused on FE8.

So, before it starts, here’s what you’d need:

Event file template
#include EAstdlib.event



POIN TurnBasedEvents
POIN CharacterBasedEvents
POIN LocationBasedEvents
POIN MiscBasedEvents
POIN Dunno Dunno Dunno
POIN Tutorial
POIN TrapData TrapData
POIN Units Units
POIN $0 $0 $0 $0 $0 $0
POIN BeginningScene EndingScene






WORD $00

WORD $00





// Events

// Manual Movement

// Scripted Fights

// Units

// Shop Data

MESSAGE Events end at offset currentOffset

Free space can be found from b2a610-c00000, as well as the end of the ROM (starting at ???).

Useful Information

This stuff isn’t strictly eventing related but is nonetheless helpful to know.

Apply this patch to your ROM before you start working, it contains a bunch of essential fixes for FE8

##Table of Contents

  1. Key Concepts
  2. Handling Units
  3. The Event Arrays
  4. Scene Construction
  5. Inserting Maps/Tile Changes
  6. More Codes
  7. Conditions
  8. ASM Condtions/Effects
  9. The World Map
  10. Misc Info
  11. Epilogue

And much like Arch’s tutorial, this isn’t designed to explain basic terminology for ROMHacking and eventing shouldn’t be the first thing you try when you want to hack FE.

Now, the thing is, I am by no means an expert when it comes to FE8 hacking, I’m just the idiot who thought making this was a good idea, and it’s a wiki so that other people can edit it and hopefully the other more experienced FE8 hackers contribute to this and fill in the gaps. I just didn’t see something like this for FE8 and people are always saying “It’d be nice if we had something like the FE7 tutorial for FE8”, so if anything, hopefully this will motivate people into making this a reality for future FE8 hackers/people who need a comprehensive reference for FE8 eventing.

It’s going to probably be built upon slowly (mainly because I want to get this out there for other people to edit and all that)

[FE 8] Second Chance
FE Modding: On the State of the Art
FE Modding: On the State of the Art
[FE8] The FE8 chapter construction guide-thing request post
Where Do I Start?

Chapter 1: Key Concepts

###Memory Slots
These are essentially variables you can use to store values up to 0xFFFFFFFF.

#Stores value as a word to $030004B8 + (memory slot*4). Maximum memory slot is 0xD.
#Memory slots are very important for fe8 events!
#Memory slot 0x0 always has a value of zero - don't bother setting it otherwise.
#Memory slot 0xB is where coordinates for many commands are read from.
#Memory slot 0xC is where conditional values are stored - booleans, character IDs, gold count, etc
#Memory slot 0xD indicates the size of a queue (see below); don't modify it with SETVAL

Set them with the following command: SETVAL slot value

You can chain SETVAL entries to use with certain event codes by using this command: SAVETOQUEUE

Use in conjunction with commands like SET_HP (characterID) - this sets the character’s HP to the value stored in Slot 0x1.

You can set the parameters of certain commands to 0xFFFF, which will make the game look at the value in memory slot 2. This is useful if you want to, for example, display a certain text depending on the results of an ASMC.

ASMC Devil_Robe_ASMC|1 //puts the text id to display into slot 2
NOTIFY 0xFFFF 0x5A 0x0 //5A is the "item obtained" noise.

###Event Execution Bitfield

3C | short | Event State Bits: (Can be set/unset using events 0x02 & 0x10 (EVBIT_T/F & EVBIT_MODIFY))
                    bit 0 (& 0x0001): ignores queued event engine calls on destruction
                    bit 1 (& 0x0002): allows skipping? + when set, won't call "ENDA events"
                    bit 2 (& 0x0004): currently skipping (set after start press)
                    bit 3 (& 0x0008): 
                    bit 4 (& 0x0010): prevents skipping? (modified by EVBIT_MODIFY)
                    bit 5 (& 0x0020): (modified by EVBIT_MODIFY)
                    bit 6 (& 0x0040): (modified by EVBIT_MODIFY)
                    bit 7 (& 0x0080): no fade
                    bit 8 (& 0x0100): set when faded in
                    bit 9 (& 0x0200): Enable camera follow on unit movement
                    bit A (& 0x0400): Set when moving to another chapter?
                    bit B (& 0x0800): Set when doing something to GAMECTRL field 0x29?
                    bit C (& 0x1000): Set/Unset by event codes 0x23/0x24, which block/unblock the game's graphics managers

Set with EVBIT_T 0xWhatever
###Event IDs

This will become more important once you get to Chapter 3.

These switches can be utilized in a variety of ways, but the important fact to remember is that you’ll generally be associating one event ID per event. However, they do not have to be bound to a specific event, which allows you to use the manipulate the switchboard to perform a variety of tricks (Elibean Nights uses this heavily, but it is similarly applicable to FE8 hacking).

These two commands allow you to set an event ID to true/false at will:

ENUT eventID //sets eventID as "triggered"
ENUF eventID //sets eventID as "not triggered"

###Moving to the Next Chapter

MNCH: Moves to next chapter (shows world map stuff)

MNC2: Moves to chapter directly (no world map)

MNC3: Used by Valni,Lagdou and the Final chapters, Part 1

MNC4: Used by Final chapters, part 2 with parameter 0.

MNTS: Returns to Title Screen


Chapter 2: Handling Units

###Defining Units
UNIT |char ID| |class ID| |leader| Level(lvl, faction, autolevel) [x,y] |flags| 0x00 |number of REDAs| |pointer to REDAs| [Item1, Item2, Item3, ... ] [AI1, AI2] AI3 AI4

  • Known flags: 0x1 is used for enemies in skirmishes and dungeons;
    based on the unit’s stated class, it is reassigned to one of four classes randomly chosen, given 1-2 class-appropriate weapons or loot, and has its level randomized to between -2 and +5 of its stated value.
    0x2 for drop last item.
    0x4 will slightly randomize the unit’s starting position.
  • REDAs: REinforcement DAta, use them to define movement immediately after loading. You can also use the MOVE command.
  • REDA [x,y] Flags Speed Rescuer Delay

###Unit Blocks

So you’ve got your units, but you don’t know where they’re supposed to go so the game knows they’re supposed to be there. Fear not, all will be explained soon!

Sample unit block:

UNIT Owen MageLord 0x0 Level(1,Ally,0) [1,16] 0x0 0x0 0x1 Ow [0x0] NoAI
UNIT Sawyer SawyerLord 0x0 Level(1,Ally,0) [1,17] 0x0 0x0 0x1 Sa [0x0] NoAI
UNIT Aurora Cleric 0x0 Level(1,Ally,0) [1,15] 0x0 0x0 0x1 Au [0x0] NoAI

Remember to always end it with an empty UNIT, otherwise bad things will happen!

###Loading Units

Now it’s time to tell the game to load those units in!

  • LOAD1 0x1 (unit label) - Used to load units the first time they appear
  • LOAD1 0x1 0xFFFFFFFF - loads units from pointer in memory slot 1 (more on that later)
  • LOAD2 0x1 (unit label) - Used to load units in maps they appear in after their first appearance.
    TODO: Figure out LOAD1 0x0

Loading units in your events:

LOAD1 0x1 Label

Don’t forget the ENUN! It pauses the events until the current thing is done running, this way your units aren’t loading while people are trying to talk or anything like that!

Enemies and NPCs will always use LOAD1, player units will only use LOAD1 the first time you load them in the game. If your unit shows up in chapter 4, you LOAD1 him for chapter 4, if he shows up in chapter 5, you use LOAD2. If you are using blue units in a cutscene, load them with LOAD2 as well.

###Specifying units
All unit-targeting codes in FE8 use either the character number or one of the following special codes:

0xFFFF: checks active unit (currently selected for moving/attacking)
0xFFFE: checks unit at coordinates stored to Memory slot 0xB (format is 0x00YY00XX)
0xFFFD: checks unit of ID stored to Memory slot 0x2

Set the values of memory slots using SVAL or SMOV or SETVAL (slot) (value)
(see Chapter 1 for a refresher on memory slots)

###Moving Units

Useful macro: #define Coords(x,y) "x+(y<<6)"

  • MOVE speed character [x,y]
  • For more control over the move you can use MOVEFORCED to chain locations.
SETVAL 0xD 0x0 //clear the queue
  SETVAL 0x1 Coords(x,y) //first location
  SETVAL 0x1 0x0 //separator
    SETVAL 0x1 Coords(x,y) //second location
    SETVAL 0x1 0x0 //separator
      SETVAL 0x1 Coords(x,y) //third location
      SETVAL 0x1 0x0 //separator
MOVEFORCED 0x0 character 0x0
  • MOVEONTO speed character target for “rescuing” mostly


Use the macro:


to load reinforcements for a chapter, it handles moving the camera to where it should be and removing the black flash for you, as well as actually loading the unit. All you need to do is put it into the label for whatever triggers them showing up.

###AI Changing
To Change AI you use this:
SETVAL 0x1 0x0000AI2AI1

##Hiding/Showing Units

CLEA Clears ally units from the map but does not remove them from the party.
CLEE Clears enemy units from the map
CLEN Clears npc units from the map

REMU ID Removes unit from party until next loaded. Used on Eirika/Ephraim at the lord split.


Chapter 3: The Event Arrays

You may find yourself asking, “What in the hell is a POIN array?”

To answer that question, look below:


See ThisChapter? That’s the label for the POIN array, which can be found below:

POIN TurnBasedEvents
POIN CharacterBasedEvents
POIN LocationBasedEvents
POIN MiscBasedEvents
POIN Dunno Dunno Dunno
POIN Tutorial
POIN TrapData TrapData
POIN Units Units
POIN $0 $0 $0 $0 $0 $0
POIN BeginningScene EndingScene

It’s included in the template already, so you shouldn’t have to mess with it at all.

CHAR events

Basic format is:

CHAR EventID label [charID1,charID2] 0x0

There is also a macro for character events that work both ways:


Location Events

CHES 0x0 itemID [X,Y] 0x14 (don’t change the 0x0 and 0x14 unless you want to do an AFEV linked to the event ID (0x0) and if you do, change that to a value higher than 0x7

Money chests:
CHES 0x0 0xXXXX0077 [X,Y] 0x14

XXXX is the amount in hex, and always terminate with 0077



Armories and Shops:
SHOP 0x0 ID [X,Y] 0x16 //armory = 0x16
SHOP 0x0 ID [X,Y] 0x17 //vendor = 0x17

SHLI Item1 Item2 Item3…

Turn Events

The basic format for a turn event is
TURN EventID SceneLabel [Turn,(End_Turn-1)] Phase
0x0 runs the event before the player phase, 0x8 runs it before the enemy phase, and 0x4 runs it before the NPC phase.
There are macros in Main Code Helpers.txt of the EA Standard Library that take the form of:
#define TurnEventPlayer(eventID,pointer,startTurn,amountOfTurns) "TURN eventID pointer [startTurn, startTurn+amountOfTurns-1] 0"

If your chapter is a defend/survive map, this is where you’d put the thing that calls the ending scene.

TURN 0xA EndingScene [7,0] 0x0 would end the chapter at the start of Turn 7. You always want to do the number of turns + 1 for this. So if you have a 6 turn defense map, you’d have this be on turn 7.

Misc Events

The template has CauseGameOverIfLordDies by default, but this is where you specify the thing that tells the game to jump to the ending scene if it is a rout or defeat boss mission (DefeatAll(EndingScene) and DefeatBoss(EndingScene) respectively).

AFEV’s (AFter EVents) can also go here:

AFEV eventID SceneLabel eventIDofPreviousEvent


Chapter 4: Scene Construction

###Loading Backgrounds and Text

Fading in and out:

  • FADI time //Fade-in with black
  • FADU time //Fade-out with black
  • FAWI time //Fade-in with white
  • FAWU time //Fade-out with white


  • To load a background: SETVAL 0x2 (background ID); CALL $9EE2E8

  • You can use the macro SetBackground(backgroundID) for this

  • To remove the background: CALL $9EE2C4

  • There is a macro Text(background,text) which does all this for you, but you can’t change backgrounds mid-conversation.

  • BG to BG transitions
    For BG to BG fading, you need:
    _0x2141 0x1B 0x1 0x4 //does the transitioning. Parameters are backgroundID, unknown, speed of transition REMOVEPORTRAITS

After the first BG and before the text stuff that follows.


  • Do your conversations with TEXTSHOW (text ID) and TEXTEND

  • REMA is used to clear the screen (which you should be doing when you change conversations or end a scene)

  • TEXTCONT is used when you have a [LoadOverworldFaces] in your text.
    [Load units/move units/other things]

###Music change codes

  • MUSC songID plays the specified song (you can also use the song’s name as it appears in your music definitions)
  • MUSS (MUSic Store)
  • MUSM (MUSic Mute)
  • MURE (MUSic REstore)


  • CAM1 [XX,YY]
  • Focuses the Camera at coordinates XX YY
  • CAM1 characterID
  • Focuses the camera on a specific character
  • FlashCursor(X,Y,time)
  • FlashCursor(char,time)

These flash the cursor on a character or area of a map, for time you can use anything, but 60 is equal to FE6/FE7’s automatically timed cursor.

##Prep Screen

To enable the prep screen in your chapter, all you have to do is add GotoPrepScreen to the end of your BeginningScene

##Sample opening scene
ENUT 0xCC //Unlocks guide menu entries

MUSC 0x07
SETVAL 0x2 Forest; CALL $9EE2E8 //BGStart
TEXTSHOW 0x98B //narration
_0x2141 0x1B 0x1 0x4 //does the transitioning. Parameters are backgroundID, unknown, speed of transition
REMOVEPORTRAITS //no idea what this is, but is necessary
MUSC 0x24
//SETVAL 0x2 0x1B; CALL $9EE2E8 //BGStart
TEXTSHOW 0x90D//banter
MUSC 0x0
MUSC Lost_Heart
CALL $9EE2C4 //BGEnd
MUSC 0x0

LOAD1 0x1 Units
LOAD1 0x1 Commander
LOAD1 0x1 NPCGuys
CAM1 [8,8]

MUSC 0x24
SETVAL 0x2 0x25; CALL $9EE2E8 //loads bg, bgstart
TEXTSHOW 0x90E//entering the fort
CALL $9EE2C4 //bgend

CAM1 [8,4]
MOVE 0x10 Sawyer [11,3]
MOVE 0x10 Owen [10,3]
MOVE 0x10 Elijah [10,4]
MOVE 0x10 Eagle [11,4]

MUSC 0x24
SETVAL 0x2 Fort; CALL $9EE2E8
TEXTSHOW 0x90F//talking to commander
MUSC 0x2E0
STAL 100
MUSC 0x25

CAM1 [8,8]
_LOAD1 0x1 BossMan
MOVE 0x10 Sawyer [11,10]
MOVE 0x10 Owen [10,10]
MOVE 010 0x84 [12,10]

SETVAL 0x2 0x25; CALL $9EE2E8
TEXTSHOW 0x910//Leonhardt shows up

MOVE 0x10 0x68 [1,11]//move boss to his spot
MOVE 0x10 0x84 [10,2]//moves commander
MOVE 0x10 Owen [10,3]
MOVE 0x10 Sawyer [11,3]

_LOAD1 0x1 Enemies
EVBIT_T 0x7 //required to stop weird blinking


Chapter 5: Inserting Maps/Tile Changes

  • Most tile changes are handled by Tiled/the map inserter

  • Pick your .tmx map, pick your ROM, pick an offset, and for the map/map change pointers, find the pointer of it from nightmare, open up a hex calculator (the default Microsoft one has one), multiply that number by 4, and add it to 8B363C.

So the pointer for the prologue map is 0x4, and in the hex calculator you’d do 4*4 + 8B363C and put the result in the map pointer box, the same process applies for the map changes pointer.

  • Only manual tile changes need eventing

##Vertical Doors
In LocationEvents:
DOOR 0x00 DoorRemoval [X,Y] 0x12

In DoorRemoval (or whatever you call the label), you just need TILECHANGE 0xTileChangeIDinTiled


Chapter 6: More Codes

###Scripted Fights

StartBattle NormalDamage(combatant,damage) CriticalHit(combatant,damage) MissedAttack(combatant,damage) Silencer(combatant,damage) SureShot(combatant,damage) Pierce(combatant,damage) BigShield(combatant) EndAttack
FIG1 attacker defender 0x0 for normal fight
FIG2 attacker defender 0x0 for map animations only
FIG3 0 0 0 is used for the tutorial and rigs the results of the next battle.(not defined in eastdlib by default, the code is 0x3F42)
If your scripted battle uses the normal fight and one of the units dies, add these after the fighting part is done:

FE8 has those cool sepia flashback scenes, and now you can use them for yourself.

  • _0x2D20 0x4 turns all map sprites sepia toned. Changing to 0x1 is blue, 0x2 is red, 0x3 is green
  • You’ll need to insert your own sepia portraits and any new palettes you want to use (Town & Docks has a flashback palette available by default) and set them using Nightmare’s Chapter Data Editor.


Chapter 7: Conditions

Unlike FE7 the conditional check is in two parts.

  • The first command writes a result to Slot 0xC e.g. CHECK_HARD will store 0(false) or 1(true) to Slot 0xC, while CHECK_MONEY stores your current Gold to Slot 0xC.
  • The second command checks against the result in Slot 0xC.
    • IFNE (conditionID) 0xC 0x0 compares slots 0xC and 0x0. Because Slot 0x0 is always 0, this means “If the previous command returned True…”
    • You can also use IFEQ (equal), IFLT (less than), IFGE (greater or equal to) but remember you are comparing two slots, not a slot and a value.

The typical conditional will look something like:

IFNE  0x1 0xC 0x0
  //Things that happen if Hard Mode
GOTO 0x2
  //Things that happen if not Hard Mode

Here is a macro for the above:
#define IFTRUE(check,conditionid,iftrue,iffalse) "check; IFNE conditionid 0xC 0x0; CALL iftrue; ELSE conditionid+1; ENIF conditionid; CALL iffalse; ENIF conditionid+1"


Chapter 8: ASM Conditions/Effects

ASMC 0xCF461: Enables the use of the Guide for your project, if you want an area for lore or something related (this unlocks the whole guide, if you want to unlock it piece by piece you have to enable each entry manually).

ASMC 0x85375: Triggers a game over


Chapter 9: The World Map

Skipping over the world map:

  • Disassemble the WM events from FE8 with the handy disassembler script (located in the scripts folder in the EA folder)
  • There’s two WM events per chapter, WM Intro and WM1.
  • For WM Intro: replace whatever code is in there with:


You can leave the offset the same since the new stuff is smaller than the old stuff, or you can point it somewhere else (though I’ve had issues when not using the original pointers).

  • For WM1:

EVBIT_MODIFY 0x1 //Don't touch WM_SPAWNLORD 0x0 0x0 0xYY 0xZZ 0x0 // WM_SPAWNLORD 0x0 0x0 0xYY 0xZZ 0x0 YY = main lord. ZZ = just completed chapter WM_LOADLOCATION2 0x0 0xXX 0x0 //Silently and instantly load world map location. All three XX's should be the same. Remember that this XX should be the world map location offset and be the same location the chapter occurs in vanilla FE8 WM_SETDESTINATION 0x0 0xXX 0x0 //Sets WM destination _0xA640 0x0 0x0 0xXX //sets your position to that place SKIPWN ENDA

As with the WM Intro event, you can keep the offset the same or change it to something else.

And the codes for the XX’s are as follows

0x00 Border Mulan 0x01 Castle Frelia 0x02 Ide 0x03 Borgo Ridge 0x04 Za'ha Woods 0x05 Serafew 0x06 Adlas Plains 0x07 Renvall 0x08 Renvall 0x09 Port Kiris 0x0A Teraz Plateau 0x0B Caer Pelyn 0x0C Hamill Canyon 0x0D Jehanna Hall 0x0E Fort Rigwald 0x0F Bethroen 0x10 Taizel 0x11 Za'albul Marsh 0x12 Grado Keep 0x13 Jehanna Hall 0x14 Renais Castle 0x15 Narube River 0x16 Neleras Peak 0x17 Rausten Court 0x18 Darkling Woods 0x19 Black Temple 0x1A Tower of Valni 0x1B Lagdou Ruins 0x1C Melkaen Coast

After you edit the events, just reassemble them in EA and you should be good to go!

Skipping the talk with Hayden after chapter 1

#include EAstdlib.event

ORG $A3C860
IFET 0x88
IFEQUAL 0x1 0xC 0x0
CALL NewEvents


WM_LOADLOCATION2 0x0 0x0 0x0 //Might as well load Border Mulan here (optional)
WM_LOADLOCATION2 0x0 0x1 0x0 //Like CREATENEXTDESTINATION except silent and instant
_0xA640 0x0 0x0 0x01 //like MOVESPRITETO except silent and instant

Just make a new text file, copy that in, pick an offset for the second part, assemble it in EA, and that headache of a scene should be gone!

If you receive an error that says File SkipHayden.txt, Line 5, Column 1: No code named GOTO_IFEF found. change it to CHECK_EVENTID

Manipulating the world map

A start for maipulating the world map can be found here.

Changing skirmish spawn locations and probabilities

There are 3 offsets of interest.

Skirmish Location Table - $206948 Eirika Mode Skirmish Probability Table - $206A48 Ephraim Mode Skirmish Probability Table - $206AAB


Chapter 10: Misc Info

Custom chapter titles
Chapter titles in FE8 are images and require a little more effort to get working compared to FE7, which is just straight text.

So, the easiest way to get your chapter titles in FE8 is to make the chapter title in FE7 and then do a few more things to get it in FE8.

Step 1: Make whatever your chapter title is supposed to be in FE8 in FE7 (using FEditor)

Step 2: Load up FE7 and get to this screen and pause the emulator:

Step 3: (I’m assuming you’re using VBA) Go to Tools -> Map Viewer

Step 4: Find the right BG with the chapter title and click save and name it whatever you want and save it wherever you want.

Step 5: Open it in some sort of image editor (probably Usenti)

Step 6: Crop as little of the image as possible (try to just get the words for the title and a little extra room if you want) and save it as its own thing

Step 7: Open this template in Usenti

Step 8: Drop the chapter title in on top of the template in Usenti, match the background color of the pasted image with the color of the template (inkdropper on template background, then fill bucket on background of the title stuff).


Step 10: Open the ROM in GBAGE, go to image controls and go to the chapter image you need to change (the chapter images should start at 1406/1407)

Step 11: Insert the image by clicking import a bitmap and make sure your checkboxes are the same as mine.

Step 12: Pick a new offset for the image in the event that the new title is bigger than the old one (you should pick a new offset anyway just to be safe).

Assuming all goes well, it should be inserted into the game now!

Remember to open up the ROM and make sure the image is aligned properly, if it’s not open it up in Usenti and move the title to where you think it should be to make it look centered. When you’re satisfied with where you moved it repeat the GBAGE insertion steps.

And if it’s still not lined up right, just keep repeating the process until it looks right in the ROM.

If this sounds like a huge pain in wherever, then don’t worry. Circles has got you covered. This ASM hack allows one to use text entries for titles like FE7. If you want to use pictures in your title cards or something, then the above method still exists.

Pay to Recruit Events

SETVAL 0x4 0x03E8           // this sets the amount of gold that must be paid (in this case, 03E8 in hex=1000)
CHECK_MONEY                 //stores current gold to slot 0xC
IFGE 0x0 0xC 0x4            // Do you have the money? Memory slot 0x4 has the money stored
EVBIT_F 0x3                 // unknown, but necessary
Text(0x0B14)                // this has a [Yes] command. Just use any text with a [Yes] command
SETVAL 0x7 0x1              // Stores 0x1 (yes) to slot 7
IFEQ 0x1 0xC 0x7            // If Slot C matches Slot 7
SLOTS_ADD 0x32              // Slot 2 = Slot 3 (what was in slot 3??)
SLOTS_ADD 0x43              // Slot 3 = Slot 4 (Slot 3 now = price)
GIVETOSLOT3                 // Give Item in slot 1 to char in slot 3?? UNKNOWN
    //CALL events that happen "if you have the money and you choose Yes". Better to include ENDB or things may screw up
ELSE 0x2
ENIF 0x0
    //CALL events that happen "if you don't have the amount of money." The Yes/No choice isn't even displayed.
ENIF 0x1
    //CALL events that happen "if you DO have the money, but you said No".
ENIF 0x2

Glowing Cross

Makes a glowing circle under the specific chracter for the specific amount of time


Changing the 0x100 modifies the quake but for the best earthquake results you might as well leave it be so it looks nice.

Music transitions
So, FE8 is a bit weird with music transitions in text. In FE7, you’d simply use multiple text slots. In FE8; however, you use only one. Here is how you do it.

Start your text events like normal:

Next it gets a bit interesting.

To specify the music you want to change to, use the following events:

If you want the music before the change to fade out a bit, use the following code before the music code:

Now, we’re not done yet, next comes the tricky part. What you need to do next is open up your text editor.

In your text slot you need to add in this code to the specific area you want the music to change:

So, in the end, your text slot should look something like this.
[OpenLeft] So... Mycen said no, did he?[.] What a shame.[.][A][X] [LoadOverworldFaces] [OpenRight] Wait!--[A][0x02] I'll join in my Gramp's place![.][A][X]

Does anyone have a copy of InvdrZim13's FE8 chapter title template?