Incompatability between Mog's and Yanlfy's plugins

[deathsia]

Talking about this guy and this dude.


Anyways, I'm here to ask for help in making the two compatible or more specifically, their combat plugins.


I'm not coder savy or I would have most likely already figured out what's wrong and fixed it myself so does anyone have


any idea which of yanfly's and Mog's combat plugin's don't like each other?


I'm making this thread to try to as a community, pull together which combat plugins we know work together and which ones do not and to figure out how to make the ones which don';t like one another to like one another. 


Known Incompatibilities: 


YEP_Selection_Control and Mog_Combat_Hud + Mog_Combat_Commands (Fix: Disable Yep_Selection_Control) 

 

[_Shadow_]

I'm not coder savy or I would have most likely already figured out what's wrong and fixed it myself so does anyone have


any idea which of yanfly's and Mog's combat plugin's don't like each other?

It isn't so simple even for coders. You see, to make two plugins compatible with each other, you should care about such compatibility.


Since most of the coders focus on sets of their own plugins, most of the time is like asking them to rewrite a plugin from scratch.


Javascript flexibilities do not help that either, there are seriously a lot of things that can go wrong.


If you got developer A with scriptA and developer B with scriptB, being incompatible scripts, it is easier for developer A to make a similar script to scriptB from scratch, than making scriptA compatible. The question is, who will accept making such a script. 


It's not like they are obligated to do that. Anyways, incompatible scripts is a common issue, the more complex the scripts are, the worse it hapens, hopefully there can be an easy solution to your problem, maybe a third script as hotfix I don't know.

 

[deathsia]

It isn't so simple even for coders. You see, to make two plugins compatible with each other, you should care about such compatibility.


Since most of the coders focus on sets of their own plugins, most of the time is like asking them to rewrite a plugin from scratch.


Javascript flexibilities do not help that either, there are seriously a lot of things that can go wrong.


If you got developer A with scriptA and developer B with scriptB, being incompatible scripts, it is easier for developer A to make a similar script to scriptB from scratch, than making scriptA compatible. The question is, who will accept making such a script. 


It's not like they are obligated to do that. Anyways, incompatible scripts is a common issue, the more complex the scripts are, the worse it hapens, hopefully there can be an easy solution to your problem, maybe a third script as hotfix I don't know.

I narrrowed it down to two speicific plugins yanfly's plugin's don't like, his commands plugin and his hud plugin.

 

[_Shadow_]

I narrrowed it down to two speicific plugins yanfly's plugin's don't like, his commands plugin and his hud plugin.

I really don't understand what you mean by that. I feel the urge to copy - paste my previous answer.


I can not answer on behalf of @Yanfly, but I tagged him to take a look at this. The most I can do really.


Just keep in mind that what you ask might be very simple or very complicated.

 

[Shaz]

Raise your hand if you're shocked that Mog's stuff is once again notoriously incompatible with Yanflys's?

That's a bit rude.  People are not required to make their plugins/scripts compatible with each other.  That'd be like telling all the artists that they have to make resources in the same style.  Just be glad there are people willing to write this many scripts for the community, and prepared to figure out ways to overcome problems.  If someone said that about me, I'd throw my hands up and be done with it.

 

[deathsia]

That's a bit rude.  People are not required to make their plugins/scripts compatible with each other.  That'd be like telling all the artists that they have to make resources in the same style.  Just be glad there are people willing to write this many scripts for the community, and prepared to figure out ways to overcome problems.  If someone said that about me, I'd throw my hands up and be done with it.

Wasn't intended to be rude but I suppose it can be taken as such, sorry.

 

[Yanfly]

This has more to do with the way Mog builds his plugins/scripts. Mine tries to accommodate for any changes made previously by other plugins (mine or other creators alike). Mog's plugins/scripts just straight up overwrite the process and/or use his own which use completely different functions, which causes incompatibilities.


My advice to you: if it doesn't work, don't get hung up over it. Pick one or the other and move on. Waiting for a compatibility patch requires getting a third programmer into the mix because neither I nor Mog have the time to work out every intricate detail of our works and a third programmer is a chef too many.

 

[Johnboy]

I narrrowed it down to two speicific plugins yanfly's plugin's don't like, his commands plugin and his hud plugin.

Which HUD and commands plugins? Because I use a bunch of Yanfly's plugins and I also use MOG's Battle HUD and Battle Command plugins and they work almost flawlessly, with only a minor adjustment to MOG's Battle HUD required to accomodate YEP Selection Control. Perhaps asking if anyone else has had issues might be better than attacking the developers, considering they (most) likely do this in their spare time.


Or you could ask if anyone's found a way to make them compatible with each other. That works too.

 

[deathsia]

This has more to do with the way Mog builds his plugins/scripts. Mine tries to accommodate for any changes made previously by other plugins (mine or other creators alike). Mog's plugins/scripts just straight up overwrite the process and/or use his own which use completely different functions, which causes incompatibilities.


My advice to you: if it doesn't work, don't get hung up over it. Pick one or the other and move on. Waiting for a compatibility patch requires getting a third programmer into the mix because neither I nor Mog have the time to work out every intricate detail of our works and a third programmer is a chef too many.

Would it be possible to implement a hud similar or almost exactly like Mog's into your lineup of plugin's then? I absolutely love your plugin's flexibility and I love the pretty look of Mog's HUD system.


Also, its not as simple as choosing one or the other. Regardless of whether or not I get Mog's hud ancommands plugin to work with your plugins or not, I'll be using your plugin system because (and I'm not trying to butter you up to the idea at all.) You combat system, including your action sequence plugins are the kind of combat system I NEED in my project. The problem is (and I mean ABSOLUTELY NO OFFENSE by this) that while your system is superb in terms of flexabilty and feature rich, the look of your menus and such leave much to be desired.


Sure I could customize your plugins to my hearts content with additonal menu options, skill combinations, and a ton of custom features using your menu style plugins, It would still look and feel... Bah, how to put this, I guess plain is the best way to put it.

 

[Ahuramazda]

Gonna be that guy and say that if you want something you should learn to do it yourself instead of asking someone else who makes free-to-use content to change their style or make a compatibility patch for someone who's coding is in a completely different style they they are comfortable trying to mess with.


In this case I have to agree with @Yanfly though that it is more of Mogs coding style that is the problem than Yanflys coding. Yanfly in nearly every plugin attempts to alias methods as to not overwrite them in case someone elses work needs the original function. Mog's stuff just plain out overwrites many of the default codes and that can severely hinder any chances of making it compatible with other plugins that may have relied upon the default code.


Just my two cents on it.

 

[deathsia]

Gonna be that guy and say that if you want something you should learn to do it yourself instead of asking someone else who makes free-to-use content to change their style or make a compatibility patch for someone who's coding is in a completely different style they they are comfortable trying to mess with.


In this case I have to agree with @Yanfly though that it is more of Mogs coding style that is the problem than Yanflys coding. Yanfly in nearly every plugin attempts to alias methods as to not overwrite them in case someone elses work needs the original function. Mog's stuff just plain out overwrites many of the default codes and that can severely hinder any chances of making it compatible with other plugins that may have relied upon the default code.


Just my two cents on it.

I have attempted to learn a few programing languages in the past and have ended up banging my head against the wall trying to implement simple functions. It's not that I don't want to learn to code plugins myself, hell I would be ecstatic if I could do something even remotely close to creating a custom menu scene, but I as much as I have tried, I can't seem to wrap my head around it.

 

[Ahuramazda]

Trial and error was how I learnt to code, and I am by far no expert, but I have managed to figure out how to edit scenes and other peoples plugins/scripts to achieve whatever I was looking for. Start small and change 1 line of code at a time and see what the outcome is and always make sure you mark any edits thoroughly so you can revert any bad changes.


You never know, one day if you do get better at it then maybe YOU can be the person who can help others with the Mog/Yanfly solutions     Just never give up on trying to learn!

 

[SimProse]

Yep, for example, MOG's Battle Transitions plugin doesn't work with Yanfly's Change Battle Equip plugin...crashes when coming back to the combat screen from it. I emailed MOG about it, hopefully he can fix it.

 

[ashikai]

If you're looking to work with Battle Huds, might I recommend just using Yanfly's Battle Window Status and DreamX's extension for it? I was messing around with battle hud stuff just yesterday and was running into the same problem. Mog's hud/commands plugins specifically don't work with YEP_BattleCore... you can however, put Mog's plugins ABOVE Yanfly's and it'll work OK so long as your game is pretty vanilla otherwise. 


Anyhoo, http://yanfly.moe/2015/12/11/yep-42-battle-status-window/ 


DreamX's extension is also linked on that page. Obviously it's missing the pre-built graphics that Mog provides, but this will get you most of the way there (unless you want a ring menu for the commands).  


It's a bit more work to configure, but I think it's worth it.

 

[deathsia]

If you're looking to work with Battle Huds, might I recommend just using Yanfly's Battle Window Status and DreamX's extension for it? I was messing around with battle hud stuff just yesterday and was running into the same problem. Mog'shud/commands plugins specifically don't work with YEP_BattleCore... youcan however, put Mog's plugins ABOVE Yanfly's and it'll work OK so long as your game is pretty vanilla otherwise. 


Anyhoo, http://yanfly.moe/2015/12/11/yep-42-battle-status-window/ 


DreamX's extension is also linked on that page. Obviously it's missing the pre-built graphics that Mog provides, but this will get you most of the way there (unless you want a ring menu for the commands).  


It's a bit more work to configure, but I think it's worth it.

After some extensive testing I have found that its specifically Yanlfly's Selection Control that his hud an battle commands plugins do not like, if you can live without that plugin, I think you'll be golden but as for me, its a needed feature so I've asked Mog if he could patch it. whether he will or not is another question however.

 

[ashikai]

After some extensive testing I have found that its specifically Yanlfly's Selection Control that his hud an battle commands plugins do not like, if you can live without that plugin, I think you'll be golden but as for me, its a needed feature so I've asked Mog if he could patch it. whether he will or not is another question however.

Really, selection control? I wasn't using that plugin at all and I was still getting a gross amount of errors when Mog's plugins were below the battle core. Maybe there are specific settings Mog's plugins don't like...