enemy rows?

[captainproton]

I'm using Yanfly Engine Ace and the Yanfly Visual Battlers scripts. I have it set up with the hero party on the right side of the screen, facing the monster troops on the left.

Thing is, when you are attacking the enemy, the first choice is always the monster the farthest to the left, which makes it seem like you are targeting the one in the back first.

How can I set it up so that Monster A is towards the right, ie, the "front row"?

https://yanflychannel.wordpress.com/rmvxa/battle-scripts/ace-battle-engine/

https://yanflychannel.wordpress.com/rmvxa/battle-scripts/visual-battlers/

 

[Shaz]

I've moved this thread to RGSSx Script Support. Please be sure to post your threads in the correct forum next time. Thank you.


Please add links to the scripts.

 

[Engr. Adiktuzmiko]

Enemy battlers in yanfly's engine is still done using the editor's troop tab. visual battler script is only for actor battlers. So arrange your enemies accordingly. Enemy A will be the first enemy you put in that troop and so on.

 

[captainproton]

Sorry! Can't believe I forgot the links. Derp!

@Engr: I tried that, and, okay, Monster A *is* on the right, nearest the party, but the leftmost enemy is still the first one targeted, making it look like the enemy in the back is being hit first.

 

[captainproton]

Bump?

 

[Engr. Adiktuzmiko]

Might be yanfly's... I tested it in default scripts where I put

Enemy A: Slime

Enemy B: Slime

Enemy C: Spider

Positioning was

Spider Slime Slime

Then when I choose a target, Slime A is still the first one to be selected so it's following the Enemy Order...

EDIT: Checked your link, Yanfly's Engine did change the selection order as per his screenshots.

Find this in Yanfly's Battle Engine

 #--------------------------------------------------------------------------  # overwrite method: make_item_list  #--------------------------------------------------------------------------  def make_item_list    @data = $game_troop.alive_members    @data.sort! { |a,b| a.screen_x <=> b.screen_x }  end

and comment it out or delete it if you want

 

[captainproton]

Commenting it out is putting those pound signs in front of the line, yes?

 

[Engr. Adiktuzmiko]

no... comment is # signs...

it will be

#def make_item_list   #@data = $game_troop.alive_members   #@data.sort! { |a,b| a.screen_x <=> b.screen_x }  #end

 

[captainproton]

Yeah, that's what I said. Putting the pound signs in front of the line.

I'm thinking in pre-Twitter terms, where # was known as the pound sign.

 

[captainproton]

no... comment is # signs...

it will be

#def make_item_list #@data = $game_troop.alive_members #@data.sort! { |a,b| a.screen_x <=> b.screen_x } #end

DUDE. A) Engr, you are awesome for always helping, and thank you so much.B ) I tried commenting it out, and just got an error.

C) so, after some tweaking with that passage you highlighted, I got this:

#def make_item_list   #@data = $game_troop.alive_members   #@data.sort! { |a,b| b.screen_x <=> a.screen_x }  #end

Swapping the a.screen and b.screen did the trick!

 

[Engr. Adiktuzmiko]

That's is totally weird, it's commented so the game wouldn't even be reading those lines anyways so deleting or swapping things shouldn't even matter...

 

[captainproton]

I don't pretend to understand it, but it worked.

Pressing the Right key moves the selection to the left and vice versa, but you at least target the nearest enemy first.

 

[Engr. Adiktuzmiko]

Which is weird, because if a line is commented it shouldn't be checked by the game anymore. Meaning it practically doesn't exist anymore.

Like I could do this and the game won't care

#def make_item_list   #@data = $game_troop.alive_members what alive? XD   #@data.sortasdasdas! { |a,b,x,y,z| b.screen_x <=> a.screen_x and I'm out of my mind}  #end

Maybe you have a script that parses comments?

 

[captainproton]

Uhhhh, maybe..? I really don't know.

I am using several scripts, but those are the only two which alter battle scenes. I think.