- Joined
- Jun 27, 2014
- Messages
- 2
- Reaction score
- 1
- First Language
- English
- Primarily Uses
RPG Maker MV Plugin Updater
By: EdLolington
Please read the readme or this post before use!
Download
Github (Source code)
Purpose
------------
If you've developing a project using certain plugins, you'll want to keep them up to date to ensure you're getting bugfixes and can develop with the plugins' latest features in mind. But this isn't too easy since you have to go out to various sources online to check for updates all the time, which can get tedious, especially if you have a lot of plugins.
This plugin updater can read which plugins you've installed in a project and check a user-defined internet update source against your local versions each time you run it. You can set it to automatically overwrite your old plugins with new versions if they're found, or download them to a separate folder.
Files
-------
The following files should come with the plugin updater:
- PluginUpdater.exe - The program you run
- updateconfig.ini - Configure PluginUpdater's behavior
- readme.txt - This text explaining how to use the program
Usage
---------
Place PluginUpdater and updateconfig in the same folder. By default the program expects this folder will be a project root folder (the same folder as the Game.rpgproject file). The default config provided will look for your plugins.js file in the /js folder, and for your plugins themselves in /js/plugins.
In addition, updateconfig.ini is set up by default to check for and update any and all installed Yanfly plugins. If you want to place these files somewhere else or add different plugins for update checking, you'll have to edit updateconfig.ini. Explanations of what each setting does can be found as comments in updateconfig.ini
Additional Tips
---------------------
This script does not check for updates for every plugin in your plugins folder. Instead, it will only check plugins you have enabled for the given project you place it in.
If a script is hosted on GitHub, you can directly link to the "RAW" text of a script file. The content hosted at these "RAW" addresses will change when the creator puts a new version up on Github, so they will work with this tool.
This tool can't update scripts whose versions are hosted at different links. For example, if the creator has scripts set up like this:
www.somewebsite.com/content/SuperCoolScriptv1.js
www.somewebsite.com/content/SuperCoolScriptv2.js
you can't update the SuperCoolScript plugin through this tool.
What the program looks like when run properly:
If you have any questions, feel free to ask them in this thread and I'll answer them to the best of my ability.


