a bit of a vague question, but: What information is there on setup events?
Can you be a bit more specific? What info do you need about them? To my knowledge, they're just needed before each event. That said, I haven't really looked at them in-depth.
I guess, how does one make a setup event?
Offset(00###000)
EventEnd()
Yup.
EasyVent Editor Super Perfect will crap these out for you by default when you first turn it on.
http://ffhacktics.com/smf/index.php?topic=4067.msg89796#msg89796
I'm not exactly sure what you want, but if you just want how to make your event not screw up (and display nothing), Kokojo's tutorial covers this.
As for how you setup a pre-battle event, it depends on what you want. If you just have a straightforward linear sequence with talking only before and after combat, you just need:
{63}(rC9)
Camera(+01000,+00000,+00615,+00302,+02560,+00000,+04096,+00001)
Camera(+01000,+00000,+00615,+00302,+02560,+00000,+04096,+00128)
{4D}(r78)
Camera(+01000,+00000,+00615,+00302,+02560,+00000,+04096,+00128)
...
Your stuff here
...
{1C}(r02)
DarkScreen(x00,x01,012,064,x00,004)
WaitForInstruction(x36,x00)
DisplayConditions(x08,060)
WaitForInstruction(x38,x00)
DisplayConditions(x00,060)
WaitForInstruction(x38,x00)
RemoveDarkScreen()
WaitForInstruction(x36,x00)
{1C}(r01)
EventEnd()
This ending displays the conditions. Of course, the above is the generic kill all enemies one, but you can find others as well.
If you have dialogue and/or choices during battle, then each additional scene requires its own event + the setting of the check variable to whatever you check for in ATTACK.OUT (usually 1).
You end battles with
{1C}(r02)
DarkScreen(x00,x01,012,064,x00,004)
WaitForInstruction(x36,x00)
DisplayConditions(x02,120)
WaitForInstruction(x38,x00)
DisplayConditions(x03,120)
WaitForInstruction(x38,x00)
DisplayConditions(x04,120)
WaitForInstruction(x38,x00)
DisplayConditions(x05,120)
WaitForInstruction(x38,x00)
DisplayConditions(x06,120)
WaitForInstruction(x38,x00)
DisplayConditions(x07,120)
WaitForInstruction(x38,x00)
RemoveDarkScreen()
WaitForInstruction(x36,x00)
{1C}(r01)
EventEnd()
This ending displays the conditions. Of course, the above is the generic win condition. Removing some of the above may cause you to not be healed in between battles and other weird things.
The following may also be necessary. If so, put them after the above sequence, but before the EndEvent().
{49}()
{82}()
{4A}()
Wait(00110)
//{6A}(r15280000ID)
//{60}(r00ID)
//{3E}(r02000000FFFFFFID00)
WaitForInstruction(x0C,x00)
{63}(rA8)
{4B}()
If you have further questions, ask me, Raven, or Kokojo, or study FFT's events. The source material is usually the best teacher, I find.
EDIT: Of course, Raven's new tool does a lot of the above for you, but it's still helpful to know what you are doing before you use the tool.
I already know all that. I'm trying to learn about the things marked "(Setup)" here: http://ffhacktics.com/wiki/Event_Scripts_and_Scenario_Order_correlationr
Quote from: RavenOfRazgriz on September 10, 2011, 02:40:54 am
Offset(00###000)
EventEnd()
Yup.
EasyVent Editor Super Perfect will crap these out for you by default when you first turn it on.
Raven already answered this :P Literally the set up events look like...
// __________________________________________________________________
//| Event Script x030 | Event Offset: x060000 | Text offset: x060005 |
// ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Offset(x003D4000)
//Remove the previous line if you wish not to override the offset in CONFIG.INI.
Text(x00000005)
//Remove the previous line if you wish text to compile directly after instructions.
EventEnd()
//INSTRUCTION SECTION END - TEXT START
//Message x01
Oh... well, that's pleasantly simple.
EDIT: Wait, Raven posted that here? Geeze, how'd I overlook it?