It helps that really, only the maps, VSP's and CHR's have to be kept in the base folder. Everything else can be kept elsewhere. Sort the folder by file-types and it's reasonably easy to keep track of even a fairly expansive data-set.

As far as your windowing woes, I don't really know what to say. It's not something I've really needed to use. I mean, how essential is this to your game that the window is centered? Plus there currently isn't a way to get the desktop resolution from the engine.

Now as for the reflection effect, there's a few ways to do this, all of them fairly hacky, but the best way is to possibly use the sprites system or HookRetrace. Neither of them is too elegant, but it's doable with a bit of mangling. Regardless you'll need a bit of bookkeeping to get the effect, and you'll need to BlitEntityFrame to a temporary image and then flipblitting that onto another image. Then you need to keep track of entity positions. I'd probably recommend the hookretrace option, but that is because it requires less setup.

Reflection effects are useful and fancy! If it also rippled images with water waves, that'd be pretty fancy. I am tempted. If I get free time, maybe I can code something up that does that, but that wouldn't be until at least a week from now.

I have just pulled out my game to check on the reflections, and discovered that there are some ripples to it, but I think it might look better without them. I have been working on other projects, though, and haven't had a chance to work on making them. On another topic, I am debating whether to continue making a room for each area, with margins that overlap with other rooms as each room has its own settings but I want the player to be able to move "seamlessly" between them, or make one room which has regions that prompt the settings to change. I would go with multiple rooms, but I want the player to be able to travel to almost any open location on the map (rectangular, including areas between the areas that would normally be viewed), and some of those areas might not be shown on any of the smaller maps (for example, a small clearing in the middle of some woods). I remember reading about the MapEd 3 limits somewhere, but have not been able to find them again. So, taking into consideration both the system's limits and the ease of use, would it be better to make multiple small rooms or one large one? Please tell me if you are confused, and I will try to explain a bit better.

Kryptonite: Actually the workaround is "use the newest version of Verge". We've been trying to get a new version pushed out, and I was putting off responding to this thread until then, but things have gotten delayed.

Just grab http://www.gearleaf.com/files/basic_workspace_win.zip; it uses the newest .exe which supports tossing maps into other directories. You can just pull the .exe out of that if you want, but it is also set up as a barebones workspace, put together for the tutorials I am (finally) working on. It's got vx packed right in with it, and Maped is tucked away in the res/map directory, where the maps go.

The restrictions now are: The MAP file must be in the same directory as the verge.exe OR in a subdirectory (or one of its subdirectories, etc.), and the VSP file must be in the same directory as the MAP file that is trying to use it. You'll have to reference the maps by their path, not just their name, like map("res/map/town.map") or whatever.

Be warned that the zip also has completely rejiggered Lua support from the last official release so if you're using Lua you might have problems -- specifically, all of the Verge3 stuff has been moved into a special table called v3, so instead of called Blit() you have to call v3.Blit().

Sorry I didn't respond to this for so long. As I said, I was hoping this would be released a while ago (that zip that I linked to is up-to-date and probably stable) but we're waiting on other platforms to get updated as well ... my understanding is that there are some library linking issues and our mac dude is swamped with other work.

I hope that is helpful.

Just a quick note: I totally lied when I said that the exe in that zip was up to date. If you get it again, it is now up to date. The exe there has issues with some blitting functions.