WOLFCODER'S PROFILE

1. Were you planning on allowing the selector to loop back when it's reached the end of a command list? It would help navigation quite a bit.

Forgot, most likely. Its a quick change. Thanks for reminding me.

2. When I select the icon of a command from the database, the currently selected graphic isn't shown in the preview box. This is awkward when trying to remember which icon I have selected currently.

This isn't as quick a change, but it still makes sense.

3. It would be nice if your editor (unlike other RPG Makers) allowed multiple variables/switches to be met in order for an event to be trigger. Perhaps by opening another dialog box that would allow you to assign multiple requirements? However, I'm not sure if that would affect performance in any meaningful way.

If you need something more specific or detailed beyond the page triggers, add if statements at the beginning of the page that Return if conditions are not met. For really complex conditions, you can write a common event that modifies one variable or better yet, with the new quest system that will be added.

It will be most easy to have events page trigger themselves upon quest stages (with an added bonus of the event page reminding you what quest and quest stage its supposed to be for).

4. Implementing popup tooltip texts for the shortcut icons below the menu bar would be nice, sometimes I forget what the icons represent :).

I was going to do tooltips much later, but just for that menu bar button thing I should add them for the next release.

5. Did you plan on adding a "middle layer" for maps? That would be nice to see.

The lower layer is actually an automatic two layer (see the terrain setting in the tileset editor). It was a deliberate decision to make it still feel like only two layers yet to actually have three. This was done to make the editor much simpler to use and more RPG Maker 2003 like. One of the (many) reasons I never moved to XP was too many layers, but the autotile terrains going on top of stuff was something I thought was really needed in 2003.

Thanks for looking. Try to find things that crash the editor and could potentially ruin projects. The worst thing RPG20XX could do is get something like a map-tree-break.. I can remind people to back their stuff up all the time but it would be nice if the editor has a very high stability rate.

You wont find a bigger fan of RPG Maker 2003 than me, I've already looked far and wide. But I'm afraid you all need to come to terms with the simple fact that software without support "rots", especially something built on a poor foundation to begin with.

So yeah, people still use it. How ‘bout that?

but, you know what, there will always be a way to emulate old games and software programs - even in the future

The APIs it relies upon predate Windows XP, eventually more and more people will simply be unable to use it. The players. Telling your end users to make lots of little adjustments to their operating system that ultimately may not work is unacceptable.

Plugin’s!!! And tons of patches to boot

You mean the software equivalent of duct tape and bailing wire on an already quirky engine? The newer engines perform poorly too, but they do expose a programming language. I don't think either are good solutions for something that advertises itself as being easy for the non-programmers to use.


This is primarily the reason I came back. I really should finish RPG20XX before moving on despite my original thoughts on doing an entire standalone editor and engine would be too much. You all care about RPG Maker 2003, Enterbrain does not. There needs to be something written by someone who does. There needs to be something finished by someone who does.

The latter remains to be seen. A love for what RPG Maker 2003 could have been drives me.

Hmm in that case I am wondering what happens when you use a .ttf pixel font in there.

Why don't you find out?

It's crashing because you didn't put anything in for game author or game title. Fill those fields out under project settings and try again.

Thanks for finding that, I'll add some sort of safeguard for the next release.