robin's dumb questions (was: Max base map height is 2?)

[Falko]

yeah
above ground buildings will crush into the 255 limit
but xbase alone needs ~180 mcd entries and farm needs ~70 that was the only default terrain that worked within mcd limit
so  to make it possible/useful in the same approach above we need to "fix" this limit first

[Solarius Scorch]

yeah
above ground buildings will crush into the 255 limit
but xbase alone needs ~180 mcd entries and farm needs ~70 that was the only default terrain that worked within mcd limit
so  to make it possible/useful in the same approach above we need to "fix" this limit first

Then this needs to happen.

[Warboy1982]

Then this needs to happen.

no, it really doesn't.

[Solarius Scorch]

no, it really doesn't.

Nyoron~

[Hobbes]

Nyoron~

Give it time Solaris and davide.

What you guys want to do can be achievable with 280 MCD entries (using a couple of tricks to extend the 255 limit). Take out 180 entries for XBase and you still get enough entries for a custom MCD file for the ground level. It most likely won't be enough for all the tiles you wanted, but map design is all about managing scarcity, either of MCD entries or of sprites.

But if you just stay waiting for something to get implemented before designing maps... well that surely leads nowhere.

[Solarius Scorch]

Give it time Solaris and davide.

What you guys want to do can be achievable with 280 MCD entries (using a couple of tricks to extend the 255 limit). Take out 180 entries for XBase and you still get enough entries for a custom MCD file for the ground level. It most likely won't be enough for all the tiles you wanted, but map design is all about managing scarcity, either of MCD entries or of sprites.

But if you just stay waiting for something to get implemented before designing maps... well that surely leads nowhere.

Such bold words! Don't worry, the work is already underway. I've been thinking...

[volutar]

If we will make "mapDataSets" list overritable by similar values section INSIDE of particular mapBlock, it could make that happen without even changing map edit (I guess).

Code: [Select]

  - name: DESERT
    mapDataSets:
      - BLANKS
      - DESERT
    script: DESERT
    mapBlocks:
      - name: DESERT00
        mapDataSets:
          - BLANKS
          - DESERT
          - JUNGLE
        width: 10
        length: 10
        groups: [0, 1]
      - name: DESERT01
        width: 10
        length: 10
        groups: [0, 1]
In this case we will have 255 MCD limit per block, not per map. Which is way better, than it is now.


It's pretty feasible, comparing to 16bit map switch, or 8.8bit (mcdsetID.tileID) way. Just for notice - straight 16bit way is worse than 8.8, at least because removing/adding new MCDsets to map would be less destructive, and won't make that much mess.