Help! Broken plugins.js.

[Damaris]

Solved; issue was an invalid parameter. Human error.


So... shortest way to explain the situation. I have a fairly script heavy project. I installed a new plugin (VE_DirectCommands.js), and it seemed it was incompatible with another plugin I was using (SRD_BattleStatusCustomiser.js). So, I disabled VE_DirectCommands.js, however the problem persisted (The project acted as though the SRD script didn't exist). I had made no other changes. I had also run a quick test before installing the plugin, everything was perfect beforehand.


During troubleshooting, I strategically replaced my entire js folder with a backup of the same project from 14 days ago (I backup every two weeks, and was going to do another backup when I finished tonight -.-). Naturally this fixed this issue. I discovered the specific file I had to replace to revert whatever changes installing VE_DirectCommands.js made was js/plugnis.js. This seemed odd to me, so I compared the changes between the files in Sublime text and couldn't find what was causing it the issue. I've included the comparison file contents in a spoiler below if anyone's interested.


Basically I have three questions;


Plugins.js tells me not to edit the file directly. Is there a reason for this, or consequences to doing this? I have yet to do so, but It's pretty tempting.


Any idea how I can go about reliably fixing this issue? It's probably only going to take me an hour or two to manually input the data again - the variables will be the same so it's literally just data input (Thankfully).


Has anyone else encountered anything like this, or know how I can prevent this happening in the future? 


Really made me appreciate my backups. =]


Any advice would be appreciated. Thanks in advance.

 

[Andar]

plugins.js is the file that stores the data you place in the plugin manager window, and nothing else.


As such, it gets rewritten every time you save your project - any manual changes that are not also stored within the plugin manager will be lost.


If that file is the only one "causing" the problem, then in reality you made some other changes in the plugin properties of a different plugin or something like that - basically finding that difference would be either pure guesswork, or you checking every single property in every single plugin that you set in your plugin manager.


As a result you can only copy the plugins.js into the project when the editor is closed (so that the new values are loaded when the editor opens the project), and then it's a fast way of setting every plugins properties, because it does nothing else. If you edit or change that file while the editor has the project open, it will automatically be overwritten with the then-current plugin settings on project save.

 

[Damaris]

checking every single property in every single plugin that you set in your plugin manager.

This was my past 3 hours. =]
I was so sure that I had made no changes to the parameters. But I found one. A backslash where it shouldn't be.
Chalk this one up to human error.
Thanks for your input.