Fixed. Thanks for the heads up.

GBRO Games
Creator of
Recent community posts
Tutorial videos
I will be updating this page every now and then whenever I release a new tutorial. Creating videos isn't my forte, so bear with me w/ regards to the video quality. Join the discord if you would like to request for a specific tutorial.
1. Primer #1 is an introduction to visual action sequencing.

2. Primer #2 is a walkthrough of the interface.

Change 'Ra_Semi' to just 'RaSemi'. Don't put underscore in batterId as it will mess up the way the battle core reads the image files.
- If your 'Sheet Type' is configured to 'Compact', filename format should be: 'RaSemi_wait.png', 'RaSemi_guard.png', etc.
- If your 'Sheet Type' is configured to 'Separate', filename format should be: 'RaSemi_wait_1.png', RaSemi_wait_2.png', etc.
Thanks for the heads up. I haven't come across an editor lock during my tests, but I will be looking into it. There's not much I can work with based on your report at the moment, but do update me if you have more data leading to the lock. Things like: does it happen during simulation, on a particular action sequence line, or when you're in the middle of editing/adding a new action sequence line, etc.
I can add front view & absolute screen positioning support in the next update. Right now, it's only designed for side view battles where QTEs spawn near the subject, w/ definable offsets.
Yes, you can do more than just modifying damage. Add state/buffs, remove state/buffs, run js code/common event, etc. are supported.
This is a known issue for devices whose display's pixel ratio is not set to 1. This has been addressed in v.1.4.31 but the web demo is still at v.1.4.3. 
I have been occupied with a lot of things so I haven't been able to update my plugins as much, but I am still active on discord to answer questions. Next major update is set to release in the next 1-2 months.
Next time, please keep communications under a single thread so it doesn't get messy.
1. Plugin order should be GBRO_UtilsCore > GBRO_BattleCore > GBRO_LoLegaiaBattle.
2. The battle core uses es2020 syntax so you'll need to update your MV's nwjs version if you're still using the default one that came with it. Follow this guide here and update to at least 0.44.x
I just did, prior to my comment above. See attached video. That's the project demo of the first person battle plugin out of the box. I simply copy pasted the battle core and utils plugin into it.
If you're starting from a new project folder, then modify the x/y parameters of the actor sprites as well, as the default values are meant for a 1920x1080 resolution. The sample assets that comes with the project folder are 1920x1080 as well. Perhaps the reason you're not seeing them is because a new MZ project starts with 816x624 resolution, so the images are way off the screen.
The ML model does recognize colors, but it's not gonna return it. It only returns the probability of how close x drawing is to each data in the data set you've trained the model with. If you trained the model with black colored shapes, and the player draws with a red pen, then the probabilities are gonna be off.
My battle core plugin handles that. The vanilla engine only plays one of the 18 default motions of a sprite sheet. The battle core plugin allows you to play any number of motions, up to any number of frames per motion, during skill execution.
I did not see that there were new comments until now as I wasn't notified by itch's notification system, so I apologize for this late reply. I have subscribed to this post so I will be notified from now on, but consider joining the discord and tagging me there instead for faster responses.
You need to update your nwjs versions if you are using the MV version of the plugin. The plugin uses es6+ syntaxing that isn't usable with the default nwjs version that MV comes with. You can check this link on how to do that.























































