WALKTRU: Tileset image design and jsoning autotileingExt (Elevation)

[Stratego (dev)]

Extended version of autotileing, we made "elevations" using that.

sorry this is not really a walktru - however it should be but i have no time now
so i only paste here what is set in jsons and a few words.

1. all_terrain.json: we defined 2 types of elevations steep and mild versions, one is walkable other is non walkable by land units (in AOS)

Code: Select all

      {
        "id":7500,
        "imgName":"terrain/terrain_elevation.png",
        "imgTilesetColumnCount":10,
        "imgTilesetPosition":0,
        "imgTilesetPositionRange":"+20",
        "imgTilesetTileSize":32,
        "imgColumns":1,
        "layer":"TERRAIN_DECOR",
        "terrainClassName":"cliff"
     },
      {
        "id":7600,
        "imgName":"terrain/terrain_elevation_mild.png",
        "imgTilesetColumnCount":10,
        "imgTilesetPosition":0,
        "imgTilesetPositionRange":"+20",
        "imgTilesetTileSize":32,
        "imgColumns":1,
        "layer":"TERRAIN_DECOR",
        "terrainClassName":"cliffgroundsteep"
     }

2. Tile groups: There is a new array in tilejoin.json (on same level as tileAlternatives) where you can set a groupname for certain exact tiles.
the goal is that you can use these names instead of using 1 in tilejoin byteTileRel definitions.
Important: The name must not contain these characters: 1 and x and 0 ! (as they are also still can be used in byteTileRel-s)

Code: Select all

  "tileGroups": [
      "LHD-7505,7504,7500,7512,7506,7518,7509,7520",
      "LHU-7514,7515,7510,7502,7516,7508,7507,7520",
      "RHD-7506,7505,7501,7513,7504,7508,7507,7520",
      "RHU-7516,7515,7511,7503,7514,7509,7518,7520",
      "UHL-7507,7517,7501,7502,7518,7506,7514,7520",
      "UHR-7509,7519,7500,7503,7508,7516,7504,7520",
      "DHL-7518,7517,7511,7512,7507,7516,7507,7504,7520",
      "DHR-7508,7519,7510,7513,7517,7506,7509,7514,7520",
      
	  "MLHD-7605,7604,7600,7612,7606,7618,7609,7620",
      "MLHU-7614,7615,7610,7602,7616,7608,7607,7620",
      "MRHD-7606,7605,7601,7613,7604,7608,7607,7620",
      "MRHU-7616,7615,7611,7603,7614,7609,7618,7620",
      "MUHL-7607,7617,7601,7602,7618,7606,7614,7620",
      "MUHR-7609,7619,7600,7603,7608,7616,7604,7620",
      "MDHL-7618,7617,7611,7612,7607,7616,7607,7604,7620",
      "MDHR-7608,7619,7610,7613,7617,7606,7609,7614,7620"
  ],

3. bytTile rel definition: and finally here is the bytTile rel definition with the new tags
Important!: The new logic will ONLY run if the FIRST byteTileRel definition line uses a group name otherwise the old logic will run that will run into errors.
Good news that (in theory) you can mix Group names and 1-s and x-s and 0-s in the same deifnition, so the old (only 1,x,0 setting will also work in theory)

Code: Select all

   {
      "id": 7520,
      "comment": "decoration - elevation",
      "insteadofTiles": {
        "void": {
          "byteTileRel": [
              "LHDx0x0x0x-7506",

              "LHUx0x0x0x-7516",
            "LHUx0x0xUHLx-7511",

              "0x0x0xUHLx-7518",

              "0x0x0xUHRx-7508",
            "LHDx0x0xUHRx-7513",

              "0x0xRHDx0x-7504",
            "LHDx0xRHDx0x-7505",
            "0x0xRHDxUHLx-7512",

              "0x0xRHUx0x-7514",
            "LHUx0xRHUx0x-7515",
            "0x0xRHUxUHRx-7510",

              "0xDHLx0x0x-7507",
            "LHDxDHLx0x0x-7501",
            "0xDHLxRHUx0x-7502",
            "0xDHLx0xUHLx-7517",

              "0xDHRx0x0x-7509",
            "LHUxDHRx0x0x-7503",
            "0xDHRxRHDx0x-7500",
            "0xDHRx0xUHRx-7519",
            
            
            "LHDxxxRHDxxx-7505",
            "LHUxxxRHUxxx-7515",
            "xxDHRxxxUHRx-7519",
            "xxDHLxxxUHLx-7517",
            "xxDHRxRHDxxx-7500",
            "LHDxDHLxxxxx-7501",
            "xxxxRHUxUHRx-7510",
            "LHUxxxxxUHLx-7511",
            "xxDHLxRHUxxx-7502",
            "LHUxDHRxxxxx-7503",
            "xxxxRHDxUHLx-7512",
            "LHDxxxxxUHRx-7513",
            
              "LHDxxxxxxx-7506",
              "LHUxxxxxxx-7516",
              "xxxxRHDxxx-7504",
              "xxxxRHUxxx-7514",
              "xxxxxxUHLx-7518",
              "xxxxxxUHRx-7508",
              "xxDHLxxxxx-7507",
              "xxDHRxxxxx-7509"
          ]
        }
      }
    }, 

4. tileIsBasically setting: also we dont forget the tileIsBasically setting

Code: Select all

    "elevation-7500..7520",
    "elevationmild-7600..7620"

[makazuwr32]

Can we set separate from hills walkability for these elevations?

And another question:
How are these elevations placed on the map — on terrain layer or on decoration layer?

[Stratego (dev)]

in AOS
- the mild one is walkable but little slowing ("cliffgroundsteep" type),
- the steep one is not walkable like cliffs do now (type "cliff" type)
so neither of them is "hill" type

in AOF these settings will be same as in AOS
however walkability is set on units themselves so that can differ.

-----------
they are on decoration layer.

but please post here ONLY about how to json things, the things we talked here are to be in one of AOF topic - or better in email.

[makazuwr32]

Good that we can set walkability for them separate from normal hills and from each other.
It is related to json i believe.

[Stratego (dev)]

please post here ONLY about how to json things, the things we talked here are to be in one of AOF topic - or better in email.