WOLFCODER'S PROFILE

-When copying a selection, show a ghost overlay of the tiles being copied inside the rectangle.

That might cause some dizzying effects. Its nice to have a clear view of what is under your drawing rectangle, too.

-A button to open the Projects folder in Explorer.

Every editor of anything has one of those, I'll add it in for a future release.

-Middle mouse button down, or alt+right mouse button, to drag the view around.

Holding space and click dragging does this (ala Photoshop style). It's incredibly awkward to rely on the middle mouse button for anything as I keep scrolling at the same time trying to press it. Plus this laptop doesn't even have a middle mouse button.

-Allow arranging the maps in the list.

That's a tricky one, but its something the original 2003 could do so I'll have to implement it at some point.

-Clear layer button.

I'm not so sure about this one.


Thanks again.

2. Attempting to change the maximum of the "Tileset" tab in the database from 1 to certain numbers (2/3) just gives me a "That new maximum limit is too large or small, it will be adjusted". However, nothing is adjusted and the operation is just canceled.

I just checked, I had a typo in the range check. This will occur if you try for 2 or 3, but 4 or more is OK.

1. I created an event and assigned it a "Full Sprite" graphic. After going back in to "Update" it, the "Full Sprite" radio button was selected; however, the "Parts" and "Composite" list box weren't behaving as expected. I had to click on the "Full Sprite" radio button for it update the dialog box.

Found and fixed this one for the next release, it wasn't initializing all the way.

1. If I create a new tileset and leave it blank, then apply it to the map I get a "could not draw GDI" error. Which is fine, however, trying to change the tileset back to one that works, will crash the editor.

I checked and fixed this one too. This kind of error is what I was talking about, it'll nuke your project sometimes if it happens.

All these changes will be in the next release. Thanks for checking, I think you lead the list in finds now with 7.

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.

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.

If you set a map's dimensions below the minimum required (I set it to 1 in Rm2k and 2k3 so it resets automatically), the editor brings up a message saying it will adjust the dimensions to the correct size, then freezes

I found that it didn't crash when making a new map and making it too small, but when you resize an existing one too small. I changed it so that it shows this warning, and then forces the values in the dialog box to minimum and it remains open. It'll be fixed in the next release.

I assumed that was the case at first, and my first thought was something like that. That's too bad, there are a few instances where mixing up ocean and deep ocean tilesets near land tiles can make some cool looking architecture, like the illusion of a shoreline, or a steep dropoff.

RPG Maker 2003 freaked out when you drew deep ocean next to the land too, just in a different way.