So what is QRT? In short, QRT stands for "Quasi RPG Toolkit" and is a project I've been working at off-and-on for the past couple of years (already? gee...) which will (hopefully) eventually become an integrated set of tools for creating RPGs in the style of what one might have seen on the SNES, back in the day, like Final Fantasy VI, for example.
This makes it similar in its goals to the RPG Maker series of editors, for those who are familiar with them. So why, one might ask, make my own version of RPG Maker? Other than simply "because I feel like it", basically, I have several ideas for improvements over the RPG Maker series that I think would be, well, improvements, especially in the areas of flexibility and customization. I think it's also a good programming and design exercise.
The QRT project also serves as a sort of updated version of my FR project. Not only is QRT much, much, much better designed, it's also much more flexible and, more important, reusable which my much older and inferior FR code-base would not have been.
Without going into too many details, let's do a brief overview of what I've done so far and what I'll be working on in the near future. (Note that the graphics in the screen shots were downloaded for use with RPG Maker 2000 from various RPG Maker fan sites and are serving, for the moment, simply as placeholders. The plan is to eventually replace these with original graphics.)
Above is the main editor window. I had a map editor for FR, but it was *only* for map editing. The QRT editor will be an integrated editor for maps, scripting and the like - as one would expect from any sort of modern development toolset.
One of the ways that I am making QRT more flexible that the RPG Maker counterpart is including a tileset layout editor to allow users to create custom tileset layouts, unlike RPG Makers' pre-defined layout (to the best of my knowledge). It is also possible to use a different layout for each map in a project, if desired. One of the things that I am currently working on is improving the "auto-tiling" feature (used to automatically draw terrain feature like deserts, swamps, rivers or whatnot) to allow the use of animated tiles in all auto-tiling groups. (RPG Maker 2000 only allows animated tiles in auto-tile groups for its special water/shore groups - I don't like the rectilinear shorelines that it limits you to.)
Another customization feature is the inclusion of custom created fonts. Fonts can be created from scratch or can be based on any installed Windows font (though the import function still needs some work).
Scripting in QRT is initially going to be via a point-and-click script interface (as I feel this is easier for novices to pick up), but I plan to eventually include an actually scripting language as well (probably Python, but we'll see when I get to that). Another feature that I'm planning for scripting is a scripting API which I'm calling "Quartic" - QUAsi Rpg Tools Interface Component. The plan is to allow users to develop scripting plug-ins for custom functionality.
Above shows a (very simple) text box showing the font display and colouring at work. This is the (humble) beginnings of the in-game UI. My plans for the UI is to make it highly customizable, including a UI layout editor as part of the QRT editor. I hope to make it fairly easy to create custom game UI (which will help give each QRT game a unique look and feel). While custom UI can be make in RPG Maker, it's very inconvenient, not to mention tedious.So far, QRT is coming along slowly, but, I suppose, somewhat steadily. As far as important functionality goes, it's roughly equivalent to where I had FR all those years ago but, as mentioned, much better designed and ultimately more flexible, powerful and reusable. At the moment, my focus is on revisiting some of my existing features and improving and/or simplifying them before continuing on with the scripting and UI systems.
I may eventually post more as I continue to progress on the project.
Freak Out
-TFitC
No comments:
Post a Comment