-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open
Labels
Description
We're discussing whether to consistently use "metatiles" or "blocks" in pokecrystal: pret/pokecrystal#1171 So far there's a strong opinion in favor of "blocks".
| Purpose | pokered | pokecrystal | Notes |
|---|---|---|---|
| Graphics | gfx/tilesets/foo.png | gfx/tilesets/foo.png | |
| Palettes | gfx/tilesets/foo_palette_map.asm | ||
| Blocks | gfx/blocksets/foo.bst | data/tilesets/foo_metatiles.bin | pokered's data/tilesets/ has other files |
| Collision | data/tilesets/foo_collision.asm | ||
| Attributes | data/tilesets/foo_attributes.bin | WIki tutorial |
Given that the blocks are really just tilemaps (you can view them in Tilemap Studio), I like how pokered stores them in gfx. I'm less sure about having separate directories for tilesets and blocksets, since they correspond so closely.
How does this sound:
- pokecrystal moves the data/tilesets/* files into gfx/tilesets. Likewise pokered moves the gfx/blocksets/* files into gfx/tilesets.
- pokecrystal renames foo_metatiles.bin to foo_blocks.bin. Likewise pokered renames foo.bst to foo_blocks.bin.
@dannye Since this is now about syncing pokecrystal with pokered, I'd appreciate your input.