FF6Tools - Browser-Based ROM Editor

Wow! This tool is looking much better as you've been working on it. Last time I tried messing around with it I found some difficulty using it for FF4 on the Super Famicom. My hope is to be able to port my Namingway Translation to it instead of using the US version.

This tool seems amazing. Sorry for the noob question, is there a resource somewhere that describes the different script actions that are available and how to use them?  I can figure out a lot of it from context, but docs would make it easier. Just as one example, looking at map 19. Narshe: South Exterior (Intro) I see the action "Set Object Position" a lot in these object scripts, but I don't see a position argument so I'm not sure how the position is controlled.

This tool seems amazing. Sorry for the noob question, is there a resource somewhere that describes the different script actions that are available and how to use them?

Hello, you can check the Hacking FAQ under "Events". Lockirby's event command list describe each event command in detail as an example:

https://www.ff6hacking.com/wiki/doku.php?id=hacking_faq

Some of the event commands don't have editable parameters yet. Sorry, the event editor is still a WIP. For now, you can use a hex editor to modify the parameters manually (after saving with FF6Tools).

Improving the event editor is next on my list of things to do. Hopefully I will get to it soon.

Improving the event editor is next on my list of things to do. Hopefully I will get to it soon.

Two things that were mentioned on Discord regarding this;

1) Have a sanity check to make sure to not overwrite what comes after the Events (dialogue pointers?) when you add bytes to the $CA-$CC banks.

2) Being able to disassemble/edit what is called with a B2 command outside the regular event banks (which happens often in romhacks).


These two things combined with what you plan for it would make it the best tool to do event hacking.

Thanks for the heads up madsiur. I'm trying to decide the best way to implement this in FF6Tools. Currently, if you expand the event script so that it overflows into the dialogue pointers, it will give a warning when you save. I can understand why it might be helpful to check for overflow continuously while editing, but I'd like to leave it the way it is for now.

For expanding events outside of the regular event banks, what if we relocate the dialogue and dialogue pointers instead? That would leave the entirety of banks CA through CD available for events. This would be nice because the expanded event space in bank CD would be accessible from NPC event pointers (so you wouldn't need to rely on command B2). It would also be a lot easier to implement in FF6Tools because fragmented data is difficult to deal with (FF4 Advance does this a lot ). Expanding the ROM and relocating the dialogue to the expanded area is relatively easy (although you wouldn't be able to edit dialogue with e.g. FF3usME afterwards). I'd love to get some feedback on this idea from folks who are interested in using FF6Tools for event editing.

As I start to improve the event editor, it would be helpful to find some folks to help me test it. If anyone is interested in testing (regardless of past experience with event editing), please let me know here or DM me on Discord. Some things I'd like to improve:

• Allow import/export of binary/text event script data
  
• Add missing parameters for all event commands (thanks to Kaxon for pointing one out)
  
• Improve command descriptions in the script editor
  
• Add cut/copy/paste of event commands
  
• Allow selection of multiple commands
  
• Double click an NPC or event trigger to open the corresponding event
  

Edit: crossed off things that are done now

For expanding events outside of the regular event banks, what if we relocate the dialogue and dialogue pointers instead? That would leave the entirety of banks CA through CD available for events. This would be nice because the expanded event space in bank CD would be accessible from NPC event pointers (so you wouldn't need to rely on command B2). It would also be a lot easier to implement in FF6Tools because fragmented data is difficult to deal with (FF4 Advance does this a lot ). Expanding the ROM and relocating the dialogue to the expanded area is relatively easy (although you wouldn't be able to edit dialogue with e.g. FF3usME afterwards). I'd love to get some feedback on this idea from folks who are interested in using FF6Tools for event editing.

I think that's a good idea, especially if the $CD bank is directly available for NPC events and event triggers. The only downside of this is breaking compatibility with FF3usME, but it's not an issue if you plan to support what FF3usME allows regarding dialogues such as the optimize dialogues function and more importantly some expansion for them. Then FF3usME would no longer be a serious option to edit them.

For expanding events outside of the regular event banks, what if we relocate the dialogue and dialogue pointers instead? That would leave the entirety of banks CA through CD available for events. This would be nice because the expanded event space in bank CD would be accessible from NPC event pointers (so you wouldn't need to rely on command B2). It would also be a lot easier to implement in FF6Tools because fragmented data is difficult to deal with (FF4 Advance does this a lot ). Expanding the ROM and relocating the dialogue to the expanded area is relatively easy (although you wouldn't be able to edit dialogue with e.g. FF3usME afterwards). I'd love to get some feedback on this idea from folks who are interested in using FF6Tools for event editing.

I think that's a good idea, especially if the $CD bank is directly available for NPC events and event triggers. The only downside of this is breaking compatibility with FF3usME, but it's not an issue if you plan to support what FF3usME allows regarding dialogues such as the optimize dialogues function and more importantly some expansion for them. Then FF3usME would no longer be a serious option to edit them.

I have my own very basic dialogue-editing tool that I had to create to compensate for FF3usME not being compatible with relocated dialogue banks.  My tool assumes the FF3usME town dialogue expansion patch has been applied and then just reads the section of the code where the dialogue bank address is fed into the ASM code to figure out where the dialogue banks are instead of checking a hard-coded address, so it allows you to relocate the dialogue banks wherever you want and it'll find them.  I can share the source code for reference if that would be a useful capability.

I have my own very basic dialogue-editing tool that I had to create to compensate for FF3usME not being compatible with relocated dialogue banks.  My tool assumes the FF3usME town dialogue expansion patch has been applied and then just reads the section of the code where the dialogue bank address is fed into the ASM code to figure out where the dialogue banks are instead of checking a hard-coded address, so it allows you to relocate the dialogue banks wherever you want and it'll find them.  I can share the source code for reference if that would be a useful capability.

It could be something useful to host on the wiki. You can sent it to me by dm if you want.

Thanks for the heads up madsiur. I'm trying to decide the best way to implement this in FF6Tools. Currently, if you expand the event script so that it overflows into the dialogue pointers, it will give a warning when you save. I can understand why it might be helpful to check for overflow continuously while editing, but I'd like to leave it the way it is for now.

For expanding events outside of the regular event banks, what if we relocate the dialogue and dialogue pointers instead? That would leave the entirety of banks CA through CD available for events. This would be nice because the expanded event space in bank CD would be accessible from NPC event pointers (so you wouldn't need to rely on command B2). It would also be a lot easier to implement in FF6Tools because fragmented data is difficult to deal with (FF4 Advance does this a lot ). Expanding the ROM and relocating the dialogue to the expanded area is relatively easy (although you wouldn't be able to edit dialogue with e.g. FF3usME afterwards). I'd love to get some feedback on this idea from folks who are interested in using FF6Tools for event editing.

As I start to improve the event editor, it would be helpful to find some folks to help me test it. If anyone is interested in testing (regardless of past experience with event editing), please let me know here or DM me on Discord. Some things I'd like to improve:

• Allow import/export of binary/text event script data
  
• Add missing parameters for all event commands (thanks to Kaxon for pointing one out)
  
• Improve command descriptions in the script editor
  
• Add cut/copy/paste of event commands
  
• Allow selection of multiple commands
  
• Double click an NPC or event trigger to open the corresponding event
  

That would incredible if it all could be done with not only FF6, but the other games FF6Tools is compatible with. Especially the other two SNES games.