I am in the process of writing the toolset to build the data for my game. Here is the a link. http://cpplibs.spaces.live.com/blog/cns!F7D26664CE20E649!1755.entry That entry will tell you about my Map Editor so far.

This is the class I am using to store the data if a tile is passable or not. I extracted it from my code as a stand alone class because I thought it would be useful for others.

BitVector

Seriously though, what do people out there think of this? It has compression/decompression (yes, I know it's not the best out there - atleast I wrote it myself though) and it supports two layers, and it will have trigger edit mode soon. I just need to write my own CheckBox class (either that or owner draw, it makes more sense to just write my own class) to handle toggling the modes of the control.

TXR

There seems to be hostility/jealousy in the air just daring to be called out so they can deny it. Oh well, I know that, but I am not going to start anything. Case closed.

Anyways, what I am looking for on feedback is what would end uers like to see added? I got ONE reply about something like that, and that was a mini-map suggestion elsewhere. I have that on my TODO list.

Now here? I have just gotten hostility. This probably means you are being pushed around by the nazi government, and are not willing to admit it. I will stop there. (Don't like it, too bad. I didn't post it here)

Quote:Original post by GuildBuilder
There seems to be hostility/jealousy in the air just daring to be called out so they can deny it.

As an unbias outside observer, I have to say you're way off base. If anything, Sandman was being generous with the "if it works for you, it's perfect" compliment. Your tool looks like it took all of five minutes to develop. It looks fine so far, but it's certainly nothing to show off yet.

Here's a piece of advice from someone who's had a tremendous amount of experience with game editor development: avoid them as much as possible. Keep your editor as simple as possible, and put the heavy details into other areas, such as text parsing and object start-up scripting. Every time you make a change to your game, you'll end up going back to add and remove dialogs and interfaces to and from your editor. Eventually, you may even avoid changing aspects of your game to avoid having to change the editor.

Tile modules are an example of a map editor setup in that line of thought. Most of the details about how a tile functions and looks can be put into a text file somewhere, and your editor simply allows you to paint them onto the map easily. In this way, removing/adding variables to your tile structure/class/object should not require you to update your map editor or saved map files. Rather, you should, at most, only have to update a few text files. Often, you won't have to update anything, since text parsing allows for easy default variable values.