Closed Fabrizio-Caruso closed 3 years ago
Actually the MAPeD exports MAPs that consist of screen data of certain topology that you can customize using layouts. The minimal data to export is a layout with one assigned screen. NOT single tile (!)
Read the 'Quick Guide': 'The Steps to Quick Start' and 'A Few Steps to Create a Game Level'.
+Also you can get development build ( link in the Readme.md ) with an example project for the ZX version.
I will look at the docs but could you please tell me if I can draw a set of 8x8 tiles and see their "shapes" as Assembly directives otherwise I cannot use it for my purpose, which is just to know if it can export the tile "shape" data into a file with Assembly, e.g. db ... ... db ... or any other Assembly directive.
P.S.: My purpose is to support the import of tiles from Assembly and BASIC listings into my universal 8-bit development framework: https://github.com/Fabrizio-Caruso/CROSS-LIB
The MAPeD exports tiles as binary files for all supported platforms and then incbin's them in assembly listings. As for the ZX specific, the most useful tiles for use in games are tiles 2x2 or in terms of the editor - blocks. That's why the editor exports tiles 2x2. The only way to see 8x8 tiles as a set of 'db' in assembly listings is to write your own exporter using Python. The simple Python editor and API are available in the editor.
[I think you answered this] What I am trying to do is something trivial but I don't understand if and how your tool can do it. I just want to draw a bunch of monochromatic 8x8 tiles and see them as an Assembly file. I don't mind if more data (e.g. color data) is also part of the output.
I know 2x2 or 1x2 is more common but I have written a few games using also 8pixel x 8pixel tiles for all 8-bit computers and dozens of consoles (including the ZX Spectrum): https://github.com/Fabrizio-Caruso/CROSS-LIB/blob/master/docs/GAMES.md
That's why I made an API for custom data export.
Just in case, take a look at the '.\samples\zx\tilemap_render\multidir_scroll\data\tilemap.zxa'. This is an example of exported assembly listing. The source project file is '.\data\scroll_multidir_TEST.mapedzx'. Compiled binary here: '.\samples\zx\bin\multidir_scroll.sna'
Your tool is very powerful and it is meant for people who need to create binary asset files for a single or multiple specific target among many possible targets with tons of options. On the other hand, in my case, I need much less. I need to help people draw simple tiles with immediate and less smart tools for my abstract framework, which will automatically create Assembly and binary target-specific assets on the fly when mass-compiling/building for 200 different targets. Your tool is probably "too much" in a good sense.
I am trying to do something very simple. I want to draw a single tile (8 pixels x 8 pixels) and export it as an Assembly file (with Assembly directives such as .byte or db or defb, etc). It looks like the editor forces me to choose 2x2 tile blocks as the smallest editable object.
If I export I get something about the project and nothing about the edited tile: