Binary Map Editor

[netninja]

This example shows you how to make a map editor (or the ability to save any type of data) with the use of the binary object. This means that you write your map using raw bytes and choose where to put them yourself.

Why would anyone want to make their own filetype with the binary object? The main reason is that the filesizes are tiny. For each tile\piece of information you save, it only takes up one byte. Therefore this program creates maps which are about 368 bytes in filesize. Here is a list of all the pros and cons:

Pros:

• Tiny File Size
• Total control over file structure
• Easy Map Protection

Cons:

• Requires planning of your file structure beforehand
• Modifications to file structure can be difficult

If you open up your maps with a hex editor then you can easily see how they are formed and even edit them on the fly with the hex editor. If you don't have a hex editor, try using notepad.
My filetype has a filestructure like this:
Bytes - Map Data
String - Title (32 Chars)
String - Author (32 Chars)
Short - X Length (2 bytes)
Short - Y Length (2 bytes)

This example assumes that you have a basic understanding of map editors and data manipulation. You use the mouse to place tiles, right click to change tile type. Save is located in the menu under File.

Requires:

• Substring Replace
• Binary

[Sphax]

When I click on "New" button, this application freeze...

[RaiFox]

Freezes for me too.

[netninja]

Aaah, sorry, I left a line in there from my debugging. It was trying to save to a location that wouldn't exist on your computers on the start of the 2nd frame.

[Nickydude]

This seems like an excellent example, if only I could get my head around it. :grin:

You wouldn't consider making some sort of video tutorial about it would you?

[netninja]

I don't really see how a video tutorial would help. Which part are you having difficulty with? Filestructure? Binary object in general?