Rm2k3 with no autobattle

[Pneumatic]

Hi,

Been working on a game for a long time in rm2k3, possibly would like to switch to using easyrpg.

My biggest hang up is my game has a patched Rpg Rt that removes the autobattle option from the DBS because if the player used it, it would totally wreck the pseudo-CBS I had made and cause it to skip tons of battle events.

Is there a way to have no autobattle when using easyrpg with rm2k3?

Thanks!

[Kasekumpel]

Hi!

There’s currently two ways to achieve this in EasyRPG:

Custom database option (Since 0.7)

First, EasyRPG has a few experimental data fields that may modify some parts of the battle system. This isn’t very well documented & a bit hard-to-use at the moment, but is supported since version 0.7 of the Player.
In this post, Ghabry explains how to set such a field with the tool lcf2xml:

Any way to use 2k battle system in 2k3?

EasyRPG Player has an experimental feature that will opt-in for the RPG Maker 2000 Battle System while running RPG Maker 2003. So you get all the 2k3 features except for the battle system. The setting is lost everytime you edit the database and you must manually set it, e.g. with lcf2xml. https://ci.easyrpg.org/view/liblcf/job/liblcf-win32/lastSuccessfulBuild/artifact/build/bin/lcf2xml.exe Important: Make a backup of at least RPG_RT.ldb before doing anything of this!!! How to use it: Put it …

For this particular patch, you’d want to override the value for “easyrpg_battle_options”.

Changing the following line:
<easyrpg_battle_options>0 1 2</easyrpg_battle_options>
to:
<easyrpg_battle_options>0 2</easyrpg_battle_options>

But note: These line changes are lost everytime the database is saved through the Editor because RPG Maker 2003 doesn’t know & preserve these custom fields.
So if you want to take this approach, you may want to also create a small script file that automates this process of converting the .ldb via lcf2xml back & forth.

Maniac command “BattleCommandsEx” (Since 0.8.1)

Version 0.8.1 hasn’t officially released yet, but the current Nightly Build already supports a similar feature by implementing a new custom command of the “Maniac Patch”.
The latest Windows build can be found here → EasyRPG Player for Windows 64 bit [Jenkins]

This approach also isn’t perfect, because the command can only be used while inside battle.
At the moment, you’d need to call this command for every single instance of your battles in the database (Set to execute on ‘Turn 0’).
Maniac’s custom CE type “Begin Battle” isn’t supported at the moment.

Here’s an example project that uses this approach:
ManiacDisableAutoBattle.zip (935.1 KB)

I defined a few variants of this command as Common Events. You can copy them over to your project & use them there. In the unpatched Editor these commands will show up as “Unknown command”, but they won’t be auto-removed like the custom easyrpg_ database fields. Just call the desired option right when a battle is started & it should work in the latest Player build.
(See Troop 0001: Grassland 1)

Note: For this patch to work in EasyRPG, the support flag for Maniac Patch must be enabled in EasyRPG.ini. Otherwise, the command would be ignored.

EasyRPG.ini:

[Patches]
ManiacPatch=1

[Pneumatic]

Hi! Thanks for the detailed response, will try this out!