Ever wanted to export your RPG Maker scripts to .rb files, make changes to them in another text editor, and then import them back into your project? Look no further, fellow scripters. ESIE is easy to use!

Features

Plug-n-use (not play--this does nothing for your game itself) with minimal configuration

Export your scripts to .rb files; what you do with them now is not my problem

New to Version 4.0: Organize your scripts by putting them in subfolders!

Did you use another text editor? Well import your changes back into RPG Maker!

Playtest your game without having to re-import your scripts every time. Use your favorite text editor, save changes to the script's file, and playtest!

Automatically adjusts to whatever version of RPG Maker you are using; no hassles~

[ Introduction ]++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Ever wanted to export your RPG Maker scripts to .rb files, make changes to them in another text editor, and then import them back into your project? Look no further, fellow scripters. ESIE is easy to use!

[ Instructions ]++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Place this script at the top of your script list to ensure it runs first. Make any changes to the configuration variables below if desired. Run your game and a message box will prompt success and close the game.

If exporting, you can find the folder containing a bunch of .rb files in your project folder. A new file called "!script_order.csv" will tell this script in what order to import your script files back into RPG Maker. As such, you can create new .rb files and include its filename into "!script_order.csv" without ever having to open RPG Maker!

If importing, please close your project (DO NOT SAVE IT) and re-open it.

** As of Version 4.0, subfolders are now possible!

- Script names that start with the character defined in FOLDER_INDICATOR will be subfolders within your exported scripts folder. - You can specify the depth of subfolders by increasing the number FOLDER_INDICATOR characters. - Any scripts below the subfolder will be placed within it. - A script name that only consists of FOLDER_INDICATOR characters indicates "closing" that subfolder; scripts below will now be placed in the previous (i.e. its parent's) subfolder. - You may reuse a folder name multiple times. You can have subfolders named after script authors and keep their scripts grouped together without disrupting your script order (and potentially crashing your project).

[ Compatibility ]+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This script already has methods to ensure it will run properly on any RPG Maker version. This script does not rely on nor makes changes to any existing scripts, so it is 100% compatible with anything.

#******************************************************************************# B E G I N C O N F I G U R A T I O N#******************************************************************************#------------------------------------------------------------------------------# Set the script's mode. Will export the scripts, import the scripts, or do# absolutely nothing.# ACCEPTED VALUES:# 0 = Disable (pretends like this script doesn't even exist)# 1 = Export# 2 = Import# 3 = Playtest (import scripts from folder to playtest game; does not# replace or create a 'Scripts.r_data' file)#------------------------------------------------------------------------------IMPORT_EXPORT_MODE = 1#------------------------------------------------------------------------------# Folder name where scripts are imported from and exported to#------------------------------------------------------------------------------FOLDER_NAME = "Scripts"#------------------------------------------------------------------------------# Character positioned at the start of a script name to indicate a subfolder.# All scripts (or other subfolders) below it will be placed within this folder.# This must only be a one character string.#------------------------------------------------------------------------------FOLDER_INDICATOR = '@'#------------------------------------------------------------------------------# This tag will be added to the end of a script name in the CSV file for any # scripts that do not have code in them. This tag will be removed when imported# back into the project. Note that this does not apply to scripts with no name.#------------------------------------------------------------------------------BLANK_SCRIPT_TAG = '~blank'#------------------------------------------------------------------------------# When exporting, if the folder FOLDER_NAME already exists, it will create# another folder of the same name along with an ID. This will make sure you do# not overwrite the changes you made to your scripts accidentally. If false,# it will erase all the files in the folder prior to exporting. # Useless for importing.#------------------------------------------------------------------------------MAKE_EXPORT_COPIES = true#------------------------------------------------------------------------------# Creates a duplicate of the Scripts.r_data file to ensure you don't break your# project. The duplicate will be placed in the Data folder as "Copy - Scripts".# Useless for exporting.#------------------------------------------------------------------------------CREATE_SCRIPTS_COPY = true#------------------------------------------------------------------------------# If true, converts any instances of tab characters (\t) into two spaces. This# is extremely helpful if writing code from an external editor and moving it# back into RPG Maker where tab characters are instantly treated as two spaces.#------------------------------------------------------------------------------TABS_TO_SPACES = true#******************************************************************************# E N D C O N F I G U R A T I O N#******************************************************************************#------------------------------------------------------------------------------if IMPORT_EXPORT_MODE != 0

It is all explained in the script. For a quick reference, here's the subfolder instructions:

** As of Version 4.0, subfolders are now possible!

- Script names that start with the character defined in FOLDER_INDICATOR will be subfolders within your exported scripts folder. - You can specify the depth of subfolders by increasing the number FOLDER_INDICATOR characters. - Any scripts below the subfolder will be placed within it. - A script name that only consists of FOLDER_INDICATOR characters indicates "closing" that subfolder; scripts below will now be placed in the previous (i.e. its parent's) subfolder. - You may reuse a folder name multiple times. You can have subfolders named after script authors and keep their scripts grouped together without disrupting your script order (and potentially crashing your project).

This script already has methods to ensure it will run properly on any RPG Maker version. This script does not rely on nor makes changes to any existing scripts, so it is 100% compatible with anything. Credits and Thanks

KK20 - made this script

GubiD - referenced his VXA Script Import/Export

FiXato and HIRATA Yasuyuki - referenced VX/VXA Script Exporter

ForeverZer0 - suggesting and using Win32API to read .ini file

Author's Notes

I didn't test this in VX cuz I don't have it. Anyone care to test that for me?Now I can has version control for my Advance Wars Engine.

Updated script again to include a new mode: Playtest (set to 3)Normally you would have to import your files back into RPG Maker to test your code. This process could get pretty tiring (set mode to 2, playtest, close project, open project, set mode to 0, playtest, crap a bug..., fix bug, repeat) so I made this mode to combat it.

After you have exported your scripts, set the IMPORT_EXPORT_MODE to 3. Now you can make changes to your exported scripts in an external text editor, save the changes to that script's file, and instantly click the playtest button in RPG Maker to "soft import" your scripts and test your code. Saves you like 15 seconds.

Okay, that last update makes this thing like 20 times better and much more useful.

Question! Have you tried using characters like ♥☻☺♦♠•◘♣? It's just that the default script editor has no support for these characters. For instance, I wanted to put a ♥ somewhere in a script (to be seen on screen), but then the script changed it to a ?, and it actually displayed on the game as a ?. I hated that ;_;, I can't express my feelings. </3

Are you sure about this? I used to use these kinds of characters without problems. You just have to make sure to export/import with UTF-8 encoding. Zlib doesn't care what you are using, it seems the scripts just as chunks of data.

As I stated, it only affects the Script name, but that's the fault of RMXP, not this script at all.

I've also posted those characters into the body of the script and exported/imported. They still exist and are not converted to question marks.

I also checked the Show Message event command--that will also immediately convert your special characters to question marks (there's nothing this script can do anything about it though; mainly just curious). Using a "print" or "p" will properly display the special characters.

Was thinking back on this script one day and realized "I could make this a little bit better"...so I did.

Updated to version 2.0Some refactoring and added comments. Most important change though is how the scripts are exported and imported. Originally, I had named exported files something like[100]Window_Messagewhere the 100 in this case means this script is located at index 100 in the script list. This was fine and all, but it made adding/removing/changing order of the exported scripts extremely tedious.

Now, I create a CSV file that lists the filenames in order. This completely solves the above problem as you can just edit the CSV file directly to add/remove/move scripts around.

Just needed a good quality-of-life update. I don't see how this script can be improved upon, so this will probably be the definitive version (hence the jump from v1.2 to v2.0).

Updated to Version 3.0 due to some possible human errors that may occur along the way.

New configuration parameter MAKE_EXPORT_COPIES: When exporting your scripts, it will create another folder; for those moments where you accidentally exported and wiped out all your script changes. : ^) kms...

No longer exports itself (nor imports itself), assuming you DID put this script at the top of the scripts list like you're supposed to.

Subfolders are now possible. Organize your exported scripts however you want them without sacrificing script order. Can separate based on Base Scripts and Custom Scripts, and even go deeper like separating scripts by Author.

Scripts with no content in them will not be exported. If you're the type that likes to use dividers (e.g. --------) as script names, they will no longer create .RB files. In the !script_order.csv file, these will be indicated with the tag '~blank' (this tag name can be configured within the script)

Likewise, scripts with no name and no content will be ignored (no ~blank tag required). If it does contain content, the exported file will be named 'no_script_name.rb'

Bug fix: When using Mode 3 to playtest, I discovered how RM actually loads in scripts. If your project was importing MORE scripts than the 'Scripts.r_data' contained, then your game may end before even seeing the title screen. Now it's all eval'd to avoid this. I ensured that a traceback functionality would still work in case of script errors.