Question about JS, Parameters and Plugin Command

shrap_x · 2015-12-24T10:17:31+0900

I am slowly building my understanding of the new JavaScript engine. I wrote a JS to modify the direction my followers are pointing when I stop moving. The JS works fine with a parameter to allow me to turn this function on and off. What I would like to know is how I can programmatically set the parameter to on and off, so I can enable and disable this feature on demand. There appears to be no instructions in the manual on how to use the Plugin Commands event control. Is this what I need? If so, how do I use it? Otherwise, what shall I do?

● ARCHIVED · READ-ONLY

Started by shrap_x Dec 24, 2015, 01:17 AM 24 posts Page 2 of 2 View original ↗

SilverDash

#21 Dec 30, 2015, 08:24 PM Source

Do with it whatever you want, no credit nothing required.

Would appreciate it though if you would rename the Silv variable to your own to avoid conflicts ;)
shrap_x

#22 Dec 30, 2015, 10:17 PM Source
//===========================================================================//Game_Interpreter Plugin Commands//===========================================================================var shrap_x_interpreter = Game_Interpreter.prototype.pluginCommand;Game_Interpreter.prototype.pluginCommand = function (command, args) { shrap_x_interpreter.apply(this); if (command === 'EnableMapDebug') { $gameSystem.EnableMapDebug(args[0]); }};
Code:
//===========================================================================//Game_Interpreter Plugin Commands//===========================================================================var shrap_x_interpreter = Game_Interpreter.prototype.pluginCommand;Game_Interpreter.prototype.pluginCommand = function (command, args){ shrap_x_interpreter.apply(this); if (command === 'EnableFollowerStopLeaderDir') { $gameSystem.EnableFollowerStopLeaderDir(args[0]); }};
Ok, things are shaping up swimmingly except for one lingering issue. How can I make plugin in commands in different javascript files?

So they are appended to each other. Right now I am exceeding the stack size due to duplicates.

I figured this was wrong up front but tried it anyway.

Do I need to modify this with the alias?

Sorry for asking so many questions.

Iavra

#23 Dec 30, 2015, 10:30 PM Source

Do you have your plugin wrapped in an anonymous function?

Code:

var MODULE = MODULE || {};    // Your public namespace(function() {    "use strict";                                  // Your entire plugin.         MODULE.PLUGIN = {                              // Your public API. "PLUGIN" needs to be different for each plugin!    };    })();

Because this is exactly what happens, when you declare public variables and accidently overwrite existing ones.

SilverDash

#24 Dec 31, 2015, 12:26 PM Source

It seems he hints that he doesn't know how to alias and that he is just trying something. So even with anonymous functions he would cause it to crash sooner or later.

If he would have used my template it wouldn't be possible to have a duplicate alias though ;) . No need for an anonymous function. But IF you skip on the anonymous function, you better know exactly what you are doing or things turn ugly. So I would also recommend him using an anonymous function (for now).

I highly recommend any starting plugin writers to use the anonymous function around all of your code at first. When you get more experienced, drop it later on.

Also there is a bug in his code:

shrap_x_interpreter.apply(this);should be:

shrap_x_interpreter.apply(this, arguments);The other possible problem is that if he did not use an anonymous function, he indeed now declared an (probably accidental) public variable called shrap_x_interpreter which also clutters the global window namespace. On top of that it doesn't sound very unique so if he would create another plugin, it would probably conflict already. Each alias must be unique (per scope).