shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 I used a clean rom, as in there was no inserted map it was the default prologue map. Put your events on 0xD00000 on a clean ROM. If you're telling us that doesn't work it's your event file or pointers. You know what... open up Nightmare. Tell us the offset of where the "Prologue Events" are pointing to. Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 I already put it to D00000 the pointer to prolouge events is 8CA0720 Quote Link to comment Share on other sites More sharing options...
Aura Wolf Posted July 18, 2012 Share Posted July 18, 2012 (edited) I used a clean rom, as in there was no inserted map it was the default prologue map. [7,11] The Y won't work on the prologue map since it's only 15x10. Change it to 9 or lower. Edited July 18, 2012 by Aura Wolf Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 the pointer should be 0x08D00000 which means that you're writing the pointer to your events somewhere weird Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 (edited) it actually worked but the map is just black. http://imgur.com/Pc0XO Edited July 18, 2012 by Brendor the Brave Quote Link to comment Share on other sites More sharing options...
Aura Wolf Posted July 18, 2012 Share Posted July 18, 2012 (edited) Set it to Fade to Map in the Chapter Data editor. Or v :3 Edited July 18, 2012 by Aura Wolf Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 add OOBB before your LOU1 Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 yay Cam fixed it! what does OOBB do exactly? Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 out of beginning blackness aura's solution does the same thing Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 (edited) yay Cam fixed it! what does OOBB do exactly? Out of beginning blackness FE7: OOBB Moves chapter out of the blackness in the beginning. Whether the blackness is there in the first place is controlled by Chapter Data Editor. Primarily used for Chapters that don't have "Fade to Map" in the Chapter Data Editor. Edited July 18, 2012 by shadowofchaos Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 do all the macros and everything from Arch's boot camp way back when still work? I feel like the videos helped me learn a lot more than the written out tutorial. Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 do all the macros and everything from Arch's boot camp way back when still work? I feel like the videos helped me learn a lot more than the written out tutorial. Check the EA Standard Library for a list of your macros. Some of them have been updated. Some have not. Depends on the version you're using. Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 are the earlier versions still around? all I can ever find are the latest ones Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 are the earlier versions still around? all I can ever find are the latest ones You're gonna have to get it from someone who downloaded an earlier version. But there's really no reason to. Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 it'd just be easier because most of the macros I know no longer exist Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 it'd just be easier because most of the macros I know no longer exist Like? For Example? Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 no specific macros come to mind at the moment Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 no specific macros come to mind at the moment I honestly don't see the problem. There aren't any macros I remember actually being scrapped unless they were harmful. Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 then how can oyu know that they don't exist Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 a while back after the playlist I tried event hacking and it said codes weren't found like CURF and the ending commands Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 update ea because commands not existing is entirely different than macros not existing and chances are you used the wrong number of params Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 yeah CURF and the 3 ending conditions never worked for me. OpeningEvent: CURF [6,9] OOBB LOU1 Good ENUN LOU1 Bad ENDA no flash Quote Link to comment Share on other sites More sharing options...
shadowofchaos Posted July 18, 2012 Share Posted July 18, 2012 (edited) the pointer to prolouge events is 8CA0720 Also... I just realized something. That looked familiar. That's the default Prologue Events pointer. 0x8CA0720. Do you have Nightmare open at the same time you have your Event Assembler open? Because if you changed something in Nightmare and saved it AFTER you had already assembled your events... it would explain why stuff was getting messed up. Because after Nightmare opens a ROM, any changes reflected in it after it was already opened in Nightmare get reverted to the state it was in and then saved once you click "save ROM" as if you never changed anything in the first place in between the time you opened the ROM with Nightmare and the time you saved your changes in Nightmare. yeah CURF and the 3 ending conditions never worked for me. OpeningEvent: CURF [6,9] OOBB <---- Uhh... that. LOU1 Good ENUN LOU1 Bad ENDA no flash Uhh... yeah you're duing CURF before your units are loaded onto the map and even before you can actually see anything. Edited July 18, 2012 by shadowofchaos Quote Link to comment Share on other sites More sharing options...
CT075 Posted July 18, 2012 Author Share Posted July 18, 2012 are you sure it's the right coordinates are you sure the coords are on screen are you sure that you're not looking for this CursorFlash(XX,YY) Quote Link to comment Share on other sites More sharing options...
Brendor Posted July 18, 2012 Share Posted July 18, 2012 the flash is fixed now I just had to put it after OOBB and I didn't change anything in nightmare I just used it for reference Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.