WOLFCODER'S PROFILE

I recognize Tau and Inq from existing commercial SNES games- those are rips. I need to avoid even re-posting them as side content for legal reasons. This is the same reason I quit re-posting conversions of RPG Maker 2000/3's default resources. The license for those actually states you can only use them for RPG Maker 2000/3 games.

The open game art stuff gives me permission via the license the author mentions on the page, and the 16x16 REFMAP stuff sounds like abandoned assets. However, because no license information exists for REFMAP, the author has the option of sending me a CnD later if they want to.

I'm demonstrably one of RPG Maker 2003's biggest fans, but I can be critical of everything, even of myself and the things I love.

Frankly, it's a good fucking engine and personally I love it to bits.

I've defended it, but it's still one of the worst engines I've ever seen if you compare it to the world (and not to other versions of itself).

It isn't very robust at all- you can't do something like swap out all statistics and battle calculations yet keep the same battle engine. Unless you do something absolutely crazy with RPG Maker 2003 which usually results in a lot of tedium, the games made with it are all the same. Again however, this can be said about VX/Ace since most people smash the same scripts in. No RPG Maker series of toolkits in existence simply hands the author simple building blocks to make their systems with. I'm not counting RPG20XX yet because while it does this, I haven't written any tutorials for it yet (and I need to declare BETA before I can write any).

No tutorials means not user friendly and therefore might as well not be a feature.

but otherwise it's a great engine that still has many years left in it's life.

It had many years, but it's still too old and unstable to be reliable. The only long lasting projects are ones with maintained source code. It's only still here because nobody has finished a toolkit that is just as easy to use yet far superior. But many of use are close, I give it 4 more months before this changes.

Yes that's right, I'm afraid it's already dead.

Yes. The current license is GPL but I may release future versions under the LGPL which may be required when integrating a game with Steam. I don't know the specifics, though.

This software is being provided to you under the GPL license, so you accept the terms when you use it. Give it a read for more specific questions, but generally if you modify the source code to RPG20XX and publish a game, you must also provide the source code for your modifications.

The default artwork (whatever little is there) is CC-BY-SA-NC, although the future default project will contain CC-BY-SA assets but allow for commercial use. You'll want to make your own for a commercial endeavor though.

RPG20XX uses the FMOD Studio Programmer's API. You will need to grab a free indie license. It's free for one commercial indie game per year.

There's no royalty or anything for RPG20XX itself. FMOD is the only thing making this at all even slightly complex, and they'll just hand you a license for free anyways when you ask them.

There's a dormant PSG (Programmable Sound Generator) inside RPG20XX's engine. It may be used for LandTraveller. If it works well, I can provide it as an alternative to FMOD but it will limit you to .WAV and .OGG only for sampled sounds (will contain a synthesizer editor for classic PSG sound effects).

Ah, thanks for checking for bugs.

After a certain amount of steps are taken (30 to 40 steps usually does it), I get an error message and the game crashes. The numbers at the end are not always the same.

This happens because the encounter list is empty. You can put impossibly high values in for steps or disable encounters as a workaround, but it is now fixed for the next release.

There is no "none" option for composite parts except accessory. If you try to add one by creating a new part and not specifying an image file, the editor starts giving "Could not open character part (project path)\(null)" errors. At least the preview window does correctly show the character without ears/tail/hair/eyes/clothes/body, so it should work if there was no error message.

It was just the editor giving out errors, it does work in both the editor and engine. This annoying error has been fixed for for the next release.

If you change the slot used by a composite part, then edit a character sprite that uses that part, you get an "Arraylist out of bounds (2)" error similar to the other one.

I fixed this one for the next release too. When there's an undefined character set part, it will now either result in being blank or a different part instead of crashing.


If there's a bunch more bug reports, I can quickly release all the fixes.

I forgot, you'll want these

https://subversion.assembla.com/svn/rpg20xx/doc/layout/

They have the picture of an example layout of the asset and a text file explaining what goes where per letter.