Comments

Log in with itch.io to leave a comment.

(2 edits)

Is there Gamepad support? Any chance anyone tested with visustella core? Not the battle core, just the main core. Thank you.

Can I use mouse? Also, for android?

Hi, I found this strange bug about the left side status icon. it kept going towards the middle even though the x,y coordinate is nowhere near there.


Here's the x,y coordinate


Can you help me fix this?

Fixed. Please redownload the demo project. The parameter should be hooked up correctly now.

Thank you for a quick response! It worked perfectly now.

Hello, I was wondering if its possible to make the plug in work for a one man party instead of 3?

It works for a one man party as well. As long as it doesn't go beyond three, you're good.

Does this plugin work for MV as well? I was looking into using your Psudeo 3D plugin, and wanted to partner it with this one. Is that possible? Thanks.

(1 edit)

The Pseudo 3D plugin is designed to work with this one, or as a standalone plugin. However, this plugin isn't expected to behave properly of the box with MV.

An MV port of this plugin is already a planned release. Currently busy at the moment with client works, but I will be getting into it as soon as I have free time. 

Released the MV version of this plugin just now. You can get it here

Thanks for the response! I appreciate your time. I'll check it out now! 

(1 edit)

Am I able to change the FPS sprtie to show a different weapon that's equipped?

Like if the play has a sword equipped I can make it show that. And if they equip a dagger I can have it changed to a dagger sprite?

(3 edits)

I have added this feature in v.1.1. Call the following script call to change the actor's fpv identifier:

 $gameActors.actor(actorId).setFpvBattlerName(battlerName)

EDIT:

I have added this feature in v.1.2. You can still use the above script call if you wish to have another version of your actor sprite. 

1.) First, set the Equip 1 Based Sprite parameter to true.

2.) Then prepare your actor's battler images following the naming convention:  fpvId_motionX_equipId

eg. Reid_wait1_dagger, Reid_wait2_dagger, etc.