YEP Row Formation + Target Core + Selection Control question

[Alexandre_Belmonte]

Hello everyone!

I'm trying to solve this problem for days so any help would be greatly appreciated!

I want my game to have 2 rows. The back row should not be target by melee skills before the enemies of the front row are defeated.


In the Enemy A, I put in the notes:
-------------------------
<Default Row: 1>
-------------------------

In the Enemy B I put:
-------------------------
<Default Row: 2>
-------------------------

In the "Attack" skill:
-------------------------
<Row Only: 1>

<Select Conditions>

Front Row Only

</Select Conditions>
-------------------------

The Attack skill continues to target Enemy B. I created a new state for each row and in the Row 2 state note I added:

-------------------------
<Cannot Select: Skill Attack>
-------------------------

Nothing changed. Anyone has any tips about how can I make it work?

 

[Llareian]

It looks fine to me, so my question is: Are you using Battle Test to test this out, or are you actually creating a battle in-game to test? I've personally found that sometimes Battle Test doesn't work with all the Yanfly plugins, for whatever reason. If you've just been using Battle Test, make an event in-game with Battle Processing and load the game to test it out.

 

[Alexandre_Belmonte]

It looks fine to me, so my question is: Are you using Battle Test to test this out, or are you actually creating a battle in-game to test? I've personally found that sometimes Battle Test doesn't work with all the Yanfly plugins, for whatever reason. If you've just been using Battle Test, make an event in-game with Battle Processing and load the game to test it out.

Many thanks for the response Llareian, you saved me lots of headaches!

Yes, I was using Battle Test. The encounter worked as it should when loading the game! After trying this, the battle test started to work as well for some reason.

Didn't know about these bugs! Heh, I almost memorized the instructions of the YUP Plug-ins trying to find a solution.

 

[Llareian]

The other thing to be sure of with Battle Test is to make sure you go into the menu and save your project after making changes and before trying Battle Test. It's not enough to apply changes to the database, for whatever reason. But even so, sometimes I still run into this with YEP, so I've pretty much taken to doing most of my battle testing in Play Test.

Glad it's working for you!

 

[Alexandre_Belmonte]

The other thing to be sure of with Battle Test is to make sure you go into the menu and save your project after making changes and before trying Battle Test. It's not enough to apply changes to the database, for whatever reason. But even so, sometimes I still run into this with YEP, so I've pretty much taken to doing most of my battle testing in Play Test.

Glad it's working for you!

Thanks again! I will do that too just to be sure!