SRD Summon Core - Compatibility with Yanfly and SRD Plugins

[Vis_Mage]

Hey there!

Would someone be willing to take a look at, and possibly help me out with a compatibility patch between a few of SRD's plugins?

The plugins in question are SRD's Summon Core, Battle Status Customizer, and Battle Popup Customizer, and Yanfly's Core Engine.

1:
For the Battle Popup plugin, this one seems to instead be incompatible with Yanfly's Core Engine. The game will crash whenever the summoned actor does any actions, such as attacking or guarding, giving the error:
TypeError: this._damagePopup.push is not a function

2:
For the Battle Status plugin, whenever an actor is summoner (and as far as I can tell, also if an actor is added to the party via an event command), the battle HUD with the party's faces/HP/MP starts to display at a higher priority (Shows on top of the skill menu).

EDIT: Found out that the issue with Battle Popup Customizer is actually to do with Yanfly's Core Engine. I've edited my post to reflect this.

 

[J-G]

Try rearranging the srd plugins order. Could help

 

[Vis_Mage]

Try rearranging the srd plugins order. Could help

Thank you for the advice Although in this case, I've tried out changing up the order of the plugins, to no avail.

 

[ShadowDragon]

they all work together from the same author, the reason that might be inflict is that another
plugin change its fuction (overwriting and not aliased). do you have other plugins that
change the status or popup? if it does, turn that one off and see if it works,
if it does, you might need to alias or create a compability patch if you want the other included.

 

[Vis_Mage]

they all work together from the same author, the reason that might be inflict is that another
plugin change its fuction (overwriting and not aliased). do you have other plugins that
change the status or popup? if it does, turn that one off and see if it works,
if it does, you might need to alias or create a compability patch if you want the other included.

Fair enough. I've done a little more testing, in a project with only the SRD plugins, and actually did manage to figure something out.

The Battle Popup plugin actually does work with the other SRD plugins, and instead has a compatibility error with Yanfly's Core Engine.

As for the Battle Status plugin, this one is indeed incompatible with SRD Summon Core, even if they are the only two plugins in the project, and regardless of their order.

 

[ShadowDragon]

some of srd dont play nice with yanfly plugins, but it does for the most part.
you need either ask for a compability patch or change a function to play nice.

that depends how you want them to work to gether, I have seen some games that
use srd and yanfly and work nicely and smoothly.

I dont know if they edit yanfly plugin or SRD plugin for it.

 

[nanqi0000]

Hey there!

Would someone be willing to take a look at, and possibly help me out with a compatibility patch between a few of SRD's plugins?

The plugins in question are SRD's Summon Core, Battle Status Customizer, and Battle Popup Customizer, and Yanfly's Core Engine.

1:
For the Battle Popup plugin, this one seems to instead be incompatible with Yanfly's Core Engine. The game will crash whenever the summoned actor does any actions, such as attacking or guarding, giving the error:
TypeError: this._damagePopup.push is not a function

2:
For the Battle Status plugin, whenever an actor is summoner (and as far as I can tell, also if an actor is added to the party via an event command), the battle HUD with the party's faces/HP/MP starts to display at a higher priority (Shows on top of the skill menu).

EDIT: Found out that the issue with Battle Popup Customizer is actually to do with Yanfly's Core Engine. I've edited my post to reflect this.

any result?

 

[Ms Littlefish]

@nanqi0000 , please refrain from necro-posting in a thread. Necro-posting is posting in a thread that has not had posting activity in over 30 days. You can review our forum rules here. Thank you.

Hi there! Welcome to the forums! I’ve noticed this is the second thread you’ve bumped from three years ago. You will want to consider starting your own thread if you’re not finding solutions in elder threads. Members come and go, and sometimes time makes a thread less relevant to your particular issue. Thank you for understanding!