• Add Review
  • Subscribe
  • Nominate
  • Submit Media
  • RSS

Integration

I've begun negotiating with the person writing EasyRPG. Sure they might have seemed a little funny but they're re-doing the editor. There's lots of features you want to see in the editor as well as the engine. I've got all my focus on making the best DirectX next generation engine I could possibly make and as fast as I could make for RPGM2003 so I'm going to see them about the datasheets for any extensions.

This would be a good opportunity to bring anything I say to them if I told you it's best done in the editor. If their editor is from the ground-up, it should eventually be great. It would be to your (all) benefit if you could use this engine with their editor and have all the features that would best work well.

Posts

Pages: 1
But... But... What about Cherry?
KingArthur
( ̄▽ ̄)ノ De-facto operator of the unofficial RMN IRC channel.
1217
Given that this is nothing but a runtime engine, any editor that creates RM2K(3) information can in theory be used with 20XX.

Minus any unique additions from the editors that 20XX would need to read, that is. For that the various editors would need to work together or there'll be compatibility hell.
"But... But... What about Cherry?"

Cherry is doing things on their own and weren't quite as cooperative in this manner.

"For that the various editors would need to work together or there'll be compatibility hell."

Yes. As fun as I love competition, it'll be really stupid to not at least try seeing what I can do.

Update:

"Concerning editor we want to save in a new own format, XML based."

This means EasyRPG will be an entirely different platform if used in this manner instead of it just using the existing code-len-data RPG-int format. This would mean I would have to write another data reader that reads all the XML files.
author=WolfCoder
Anyone else who's an engineer would start to worry too, the project going faster and better means there's some really horrible project-breaking flaw that's going to pop up.
forgot to invest in diplomatic technologies nooooo
I think unofficial hacks to the official RPG Maker is hard to emulate and do better things supporting original LDB, LMU and LMT formats. This formats are closed source and hard to read (RPG Maker 2003 has serious errors reading its own format in several versions, prior to 1.04). XML format and a public and extensible specification is always better because is open and transparent. You can find errors easily. Easier to share files between users and fast editing and debugging editing with plain text editor that files. RGSS is nice because you have the code available and ready to run. Why not to do the same with the file format?

For example, a proposal for the new file format:

Data/Actors/0001.xml
Data/Actors/0002.xml
...
Data/Skills/0001.xml
Data/System.xml
Data/Texts.xml

If you want to share with other game project developers any data file is a lot easier with this design. With a monolithic LDB and hacked on top of LDB is not nice to share data with your project mates and had to synchronize the cooperative work.

A possible example XML design of Actors/0001.xml:
<?xml version="1.0" encoding="utf-8"?>
<actor>
<name>Alex</actor>
<title>Soldier</title>
<charset character="1" transparent="no">chara1</charset>
...
</actor>
I'm having no problems reading the existing data format and it's actually a lot like the RPG-Binary format I use for WeaponBirth. XML as you describe is going to add lots of problems to my existing problem and divide my development speed by ten.

Believe it or not, but Enterbrain's LXX format makes more sense to use in this case to me.
KingArthur
( ̄▽ ̄)ノ De-facto operator of the unofficial RMN IRC channel.
1217
EasyRPG is deviating completely away from its RM2K(3) roots and consequently away from 20XX if EasyRPG uses XML to store its data as opposed to LDB/LMT/LMU.

This is scope creep at its finest for 20XX since it's supposed to be a one-to-one RPG_RT.exe runtime engine replacement, the very nature of which makes working together with the original RM2K(3) editors the top-most priority (both for the design and the consumers).

Also:
XML format and a public and extensible specification is always better because is open and transparent.

I, as a consumer, could not care less about the open- or closed-source nature of a format. The significance only applies to the developers of the program.

You can find errors easily. Easier to share files between users and fast editing and debugging editing with plain text editor that files.

None of these are or have been a problem with the closed-source LDB/LMT/LMU formats. I also question why I'd be using a text editor to directly manipulate the files, isn't that what the editor is for?
This is scope creep at its finest for 20XX

You sure got that right! I've got an insane speed going tonight and I'd like it if the whole project went this fast. I want my engine to be playing games versus a 10% finished version that can run on my microwave.

As if I wasn't already creeping scope anyways, hahaha!

From the rundown of all possible RPG editors out there, it looks like the most common problem is either slow speeds or abandonment. I'm going to try not being in that list.
Pages: 1