Preserved forum archive. This topic stores the original first post and locally mirrored RPG Maker Web attachments when available. It is posted by the BMMPlay archive account, not by the original creator.
Original Source
- Original title: PluginManager Extender
- Original author: nio kasgami
- Original date: August 11, 2016
- Source thread: https://forums.rpgmakerweb.com/threads/pluginmanager-extender.66694/
- Source forum path: Game Development Engines > RPG Maker Javascript Plugins > JS Plugin Releases (RMMV)
Summary
Extended PluginManager Author: Nio Kasgami Version: 1.00 License: https://github.com/niokasgami/EmojiEngine/blob/master/LICENSE under the Tool Plugin EULA
Archived First Post
Extended PluginManager
Author: Nio Kasgami
Version: 1.00
License: https://github.com/niokasgami/EmojiEngine/blob/master/LICENSE under the Tool Plugin EULA
Description:
We all works on Plugins since a years. Many peoples have theirs owns ways to do it and it's nice ALTHOUGH.
They have many flaw in the plugin Managers who makes sometime not easy or annoying to make some parameters for our plugins.
Example the fact we can't use proper Array in the Manager and can be result to really clunky and overload parameters in the pluginManager.
as we can notice for doing position X we have to
do
/*:
* @param x
* @desc the x value
* @default 10
*
* @param y
* @desc the y value
* @default 0
*/
// TOTALLY non efficient when having more than 10 window to setup.
So this plugin add new Method to the pluginManager for hold your param in a cleanest ways
They have many flaw in the plugin Managers who makes sometime not easy or annoying to make some parameters for our plugins.
Example the fact we can't use proper Array in the Manager and can be result to really clunky and overload parameters in the pluginManager.
as we can notice for doing position X we have to
do
/*:
* @param x
* @desc the x value
* @default 10
*
* @param y
* @desc the y value
* @default 0
*/
// TOTALLY non efficient when having more than 10 window to setup.
So this plugin add new Method to the pluginManager for hold your param in a cleanest ways
Features:
Notice : ALL method should be call with PluginManager.MethodName();
-> toNumberArray(plugin, parameters) && toStringArray(plugin, parameters)
descriptions : Both of those method encapsulate the parameters in a array (one is for Number and the other is for String)
Syntax in pluginManager : [number,number,number,AgainANumber] or [string,string,string,againANumber]
plugin : The plugin variable (the one called for holds your plugin params)
parameters : The parameters name (it's a string)
Use: Useful when having to store a parameters with Multiples data (such equip slot, etc)
Syntax in pluginManager : [number,number,number,AgainANumber] or [string,string,string,againANumber]
plugin : The plugin variable (the one called for holds your plugin params)
parameters : The parameters name (it's a string)
Use: Useful when having to store a parameters with Multiples data (such equip slot, etc)
-> toNumberList(plugin, parameters) && toStringList(plugin, parameters)
description : Similar to toNumberArray and toStringArray these methods do the same thing but remove the forced syntax "[ ]" to the pluginManager in case you only want to input a list.
Syntax in pluginManager: number,number,number,againANumber or string,string,string,againAString
plugin: The plugin variable (the one called for hold your plugin params)
parameters: The parameters name (it's a string)
Use: Useful when having to store parameters with multiples data (such equip slot, window position, etc
Syntax in pluginManager: number,number,number,againANumber or string,string,string,againAString
plugin: The plugin variable (the one called for hold your plugin params)
parameters: The parameters name (it's a string)
Use: Useful when having to store parameters with multiples data (such equip slot, window position, etc
-> toBoolean(plugin, parameters)
description: Auto convert a parameter to a boolean since normally string are always recognized as "true". Also throw a error if the user don't write a actual valid boolean value (true or false)
Syntax in pluginManager: just write true for make it true or false for make it false.
Plugin: The plugin variable (the one called for hold your plugin params)
parameters: The parameters name (it's a string)
Use: Cleanier ways for make sure the parameter return a boolean.
Syntax in pluginManager: just write true for make it true or false for make it false.
Plugin: The plugin variable (the one called for hold your plugin params)
parameters: The parameters name (it's a string)
Use: Cleanier ways for make sure the parameter return a boolean.
-> getPluginID(plugin)
description: Method created by lavra for get the plugin by a ID written in the Plugin description instead of the pluginName avoiding error.
Syntax in plugin: <"pluginID"> in the @plugindesc description (Input in the third lines for avoid the plugin ID to appear in the plugin description.)
Plugin: The plugin variable (the one called for hold your plugin params)
Use: Use it for make the plugin independant of his filename.
Syntax in plugin: <"pluginID"> in the @plugindesc description (Input in the third lines for avoid the plugin ID to appear in the plugin description.)
Plugin: The plugin variable (the one called for hold your plugin params)
Use: Use it for make the plugin independant of his filename.
Planned Features :
- toPoint(plugin,parameters) : convert the parameters in a point value
Get the plugin: here
ScreenShot: Not needed.
Term of use : Read the License notice on the top
Conclusion:
On this I made this plugin for helps peoples and I do hope and suggest to people to use this Plugin for make code more cleans.
I also hope This "extension" would be added in the next rpg maker Update for help peoples.
Features Mentioned
- Notice : ALL method should be call with PluginManager.MethodName();
- > toNumberArray(plugin, parameters) && toStringArray(plugin, parameters)
- Spoiler
- descriptions : Both of those method encapsulate the parameters in a array (one is for Number and the other is for String)
- Syntax in pluginManager : [number,number,number,AgainANumber] or [string,string,string,againANumber]
- plugin : The plugin variable (the one called for holds your plugin params)
- parameters : The parameters name (it's a string)
- Use: Useful when having to store a parameters with Multiples data (such equip slot, etc)
- > toNumberList(plugin, parameters) && toStringList(plugin, parameters)
- description : Similar to toNumberArray and toStringArray these methods do the same thing but remove the forced syntax "[ ]" to the pluginManager in case you only want to input a list.
- Syntax in pluginManager: number,number,number,againANumber or string,string,string,againAString
- plugin: The plugin variable (the one called for hold your plugin params)
- parameters: The parameters name (it's a string)
- Use: Useful when having to store parameters with multiples data (such equip slot, window position, etc
- > toBoolean(plugin, parameters)
- description: Auto convert a parameter to a boolean since normally string are always recognized as "true". Also throw a error if the user don't write a actual valid boolean value (true or false)
Downloads / Referenced Files
Log in to download
Log in, then follow the RPG Maker Developers Group to see these download links.
Log in to downloadLicense / Terms Note
License: https://github.com/niokasgami/EmojiEngine/blob/master/LICENSE under the Tool Plugin EULA Description: Spoiler We all works on Plugins since a years. Many peoples have theirs owns ways to do it and it's nice ALTHOUGH.
Creator Claims / Removal
If you are the original creator and want this listing reassigned, edited, or removed, join BMMPlay and contact the moderators with proof that matches the original RPG Maker Web profile, linked GitHub, itch.io page, or another public creator identity.
Replies (0)
No replies yet.
0
replies
1
view
Topic Summary
Loading summary...