|
Map Making Discuss everything related to creating new levels here. |
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Map file specification
Is there a document outlining the format of map files? I'd like to write a map editor but can't find anything regarding the file format.
|
#2
|
|||
|
|||
Any reason you don't want to use the included map editor?
There's no official documentation on the map format but you can figure most stuff out from a little trial and error with the builtin map editor. Open a map then check out the [ALTITUDE_INSTALL_DIR]/editor/maps/_imported_map directory. You'll want to look at the .alte file (XML, can view it in a text editor). |
#3
|
|||
|
|||
I can't speak for linux or windows, but on the mac the map editor isn't the most user friendly thing to use. For example, the keyboard shortcuts don't use CMD but rather CTRL. The menubar isn't utilized. If you click a menu entry and then try to move the window, the menu doesn't follow; it just floats in space. When I hit the (x) to close the window, it closes the entire program. It's a lot of minor stuff that adds up.
I believe that if Altitude had a easier map editor, it would help non-developer types create truly fun maps. |
#4
|
|||
|
|||
Quote:
In my maps directory I have altx files and inside maps/cache I have altx files that contain alte files. What's the difference? |
#5
|
|||
|
|||
The _imported_map directory is generated when you open/import an *.altx file using the editor. The maps/cache directories are pretty much the same thing.
|
#6
|
|||
|
|||
I meant what is the difference between .altx and their .altx directory counterparts?
|
#7
|
|||
|
|||
The *.altx file is just a zipped-up version of the edit/cache directory. It uses LZMA for the compression with a small custom header to describe the expanded file structure.
|
|
|