From time to time we receive requests to change exclusive database parameters.
The approach to that always varies from:
Convert your LDB to EDB, edit the needed parameter, then convert it back from EDB to LDB (Any change may break it).
Learn how to mess with the source code and make an entry inside the .ini file.
Wait for the editor.
I'm thinking about a better approach that may be easier to implement in the short term:
An extra modDB file that inject custom parameters while the .ldb/.edb files are read.
E.g.:
If someone wants to customize their easyrpg_disable_row_feature, they would create a ModDB file and add the following line:
After that, every time a game starts, somewhere near ReadLcf() or parseXml(),
the current entry for easyrpg_disable_row_feature will be located and replaced with the value pointed inside the ModDB file.
From time to time we receive requests to change exclusive database parameters. The approach to that always varies from:
I'm thinking about a better approach that may be easier to implement in the short term: An extra
modDBfile that inject custom parameters while the .ldb/.edb files are read.E.g.: If someone wants to customize their
easyrpg_disable_row_feature, they would create a ModDB file and add the following line:After that, every time a game starts, somewhere near
ReadLcf()orparseXml(), the current entry foreasyrpg_disable_row_featurewill be located and replaced with the value pointed inside the ModDB file.