The Script Manager

The Script Manager is a tool that was initially designed to automate script installation and get rid of the troublesome copy/paste process. If you:

• have only one RPG Maker project
• don't mind copying.pasting scripts in the first place
• aren't a scripter yourself
• don't understand the first thing about this post

Then don't bother trying it, it is no longer needed to use my scripts like it used to be.

It is useful, however, if you:

• wish to use the same script(s) in a variety of projects/demos and keep all of them up-to-date at all times
• wish to experiment with installing or uninstalling scripts without actually modifying your projects
• are a scripter and wish to test scripts in development withtout actually modifying your projects
• have lots of scripts and wish to automate their extraction/installation

---

What's That?!

---

The Script Manager is a developer's tool that is useful when you wish to share scripts across several projects. Using it, instead of having a copy of your scripts in each and every project of yours, you can install a single, central copy all projects will then feed upon, pretty much like the RTP packages do with multimedia resources.

---

What For?

---

I initially designed the Script Manager to make my life as a scripter easier. I had this pack of scripting tools I called Moonpearl's Common, I kept updating (and am still updating every now and then) and I found it annoying to copy the newer version to all of my demos with each tiny change - plus, I sometimes wasn't able to tell which project had which version. Now I don't have this problem anymore because there's only one copy of those scripts on my hard disk, which all of my projects use at any time.

---

Should I Use It?

---

The Script Manager is essentially a scripter's tool. This means that as a casual RPG Maker user, trying and get it to work is probably too much trouble for you. It used to be a necessary feature for hits blog's demo, but starting with the latest update, it isn't anymore. Demos are now hybrid - that is, they have their own built-in copy of the custom scripts they use, which you can simply copy/paste to your own projects, and also meaning that they are stand-alone - but on the other hand, if a Script Manager is present on your system, they can also use it and override their internal scripts, allowing you to take advantage of its benefits.

For example, when I update one of my scripts, you can simply download the new version and replace your older copy with it in your RTP folder, and all Script Manager-using projects will automatically run the newer version instead of the older one they still have in memory, which saves you a lot of copying & pasting. In the end it's completely up to your own preference, now both ways work without hindering each other.

---

Will I Be Able to Distribute My Project?

---

Of course. While using the Script Manager, your project shall feed on script that are installed in your shared folder, meaning they're not in the project as such. However the Script Manager Project Builder will automatically (re)install all scripts into your project's script editor. So you can safely experiment with adding/removing scripts without changing your project's scripts until you're sure.

---

Can I Make My Own Scripts Compatible With the Script Manager?

---

Of course! And I would be delighted if you would do so! Especially considering it's not that difficult, you just have to make each entry into a .RB file (plain text file with the .RB extension) and write a setup file which will tell the Script Manager in which order the entries need to be loaded (if it matters at all). Since projects are now hybrid, you can release both your regular demos with built-in scripts, and a separate scripts package for people who want to use the Script Manager.

---

Known Issues

---

• There's a stupid bug when forcing game exit (clicking the red cross or pressing Alt+F4). This doesn't bring any harm since you were going to exit the game anyway. I promised I would fix this issue but  I still don't have the faintest idea as to why it occurs.

---

Instructions

---

1. Go to your RTP folder (default Program Files/Common Files/Enterbrain/RGSS/Standard) and create a new folder called Scripts. This will be referred to as the shared scripts folder.
2. Download the ZIP file and extract it to the shared scripts folder.
3. Go to your project's folder and create a new folder called Scripts. This will be referred to as the local scripts folder.
4. If you already have scripts installed in your project, drag-and-drop your project's folder onto the Script Manager Project Exporter shortcut. This will create a Local folder in your local scripts folder.
5. Create a new file called Script Manager.ini inside the local scripts folder.
6. Download the script bundles you wish to install to your projects and unzip them to the shared scripts folder.
7. Edit your project's Script Manager.ini file and name the scripts you wish to install to your project (one per line). At this time your project's scripts have not been modified
8. Drag-and-drop your project folder onto the Script Manager Project Loader shortcut to run it.This will load your project using the scripts you have previously named - this will not modify your project's scripts.
9. When everything works fine and you are ready to replace your project's scripts with the selection you have made with the Script Manager, drap-and-drop your project's folder onto the Script Manager Project Builder shortcut. From then on loading your project with the Script Manager or running the Game.exe file will have the same outcome.

---

Downloads

---

Download Script Manager

You can find all scripts bundles of mine on the My Scripts Compilation page. You should download those three first since they will be required by virtually any of the others:

RPG Maker XP Base Engine
Moonpearl's Scene_Base
Moonpearl's Common

Note: remember to update the Common bundle once in a while, as it may potentially be expanded with each new release of mine. An outdated Common bundle is a common cause of problem.