Initial setup for the new chunk template concept

[Garanas]

The chunk templates will eventually replace the base templates. It is similar, if not equal, to the templates used by the LOUD community.

We use the navigational mesh to divide a map into squares. These 'chunks' templates represent what an AI could populate (in terms of structures) in one of those squares.

We can then create templates that are similar to build templates that fit in exactly one of those squares. As an example:

Each of those squares represents a chunk. A chunk of an AI base. We can create many variations of each size of a chunk to make sure one base is unlike the other.

The idea is that the AI will claim additional chunks as it tries to build structures. This way the AI can expand the base and gain more ground.

We need chunks to prevent the AI from exhaustively searching for a place to build. An example are the current base templates. These are gigantic files with gigantic tables that the AI can use to find a build location that is 'nearby' of the intended build location. On average there will be a lot of negative tests before a valid build location is found.

[Garanas]

As an example output of a chunk at this moment:

{	
  Faction = UEF, 	
  Size = 32, 	
  BuildAreas = { 	
    { { -6.50, -8.50 }, { -6.50, -10.50 }, { -6.50, -9.50 }, { -2.50, -10.50 }, { -4.50, -10.50 }, { -3.50, -10.50 }, { -5.50, -10.50 }, { -2.50, -8.50 }, { -2.50, -9.50 }, { 1.50, -8.50 }, { 1.50, -9.50 }, { 1.50, -10.50 }, { 3.50, -10.50 }, { 5.50, 13.50 }, { -3.50, 13.50 }, { -4.50, 14.50 }, { -4.50, 13.50 }, { -2.50, 14.50 }, { -3.50, 14.50 }, { -2.50, 13.50 }, { 4.50, 14.50 }, { 4.50, 13.50 }, { 5.50, 14.50 }, { 6.50, 13.50 }, { 6.50, 14.50 }, { 2.50, -10.50 }, { 5.50, -10.50 }, { 4.50, -10.50 }, { 5.50, -9.50 }, { 5.50, -8.50 }, { -0.50, 3.50 }, { 0.50, 3.50 }, { -2.50, -6.50 }, { -2.50, -7.50 }, { 1.50, -6.50 }, { 1.50, -7.50 },  }, 	
    { { 10.50, -2.50 }, { 12.50, -2.50 }, { 14.50, -2.50 }, { -5.50, 7.50 }, { -5.50, 11.50 }, { -4.50, -8.50 }, { 3.50, -8.50 }, { -0.50, -6.50 }, { 3.50, -6.50 }, { -4.50, -6.50 }, { 8.50, -2.50 }, { 5.50, -4.50 }, { 5.50, -0.50 }, { 5.50, -2.50 }, { -0.50, 1.50 }, { 0.50, 5.50 }, { -5.50, 9.50 }, { 10.50, -4.50 }, { 14.50, -4.50 }, { 8.50, -4.50 }, { -8.50, -2.50 }, { -12.50, -2.50 }, { -10.50, -2.50 }, { -14.50, -2.50 }, { -12.50, -4.50 }, { -10.50, -4.50 }, { -8.50, -4.50 }, { -14.50, -4.50 }, { 12.50, -4.50 },  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    { { -4.50, -2.50 }, { 4.50, 9.50 }, { -1.50, 9.50 }, { -4.50, 3.50 }, { 1.50, -2.50 }, { 4.50, 3.50 },  }, 	
    {  }, 	
    { { -11.50, 10.50 }, { -11.50, 2.50 }, { -11.50, -9.50 }, { 11.50, 2.50 }, { 11.50, -9.50 }, { 11.50, 10.50 },  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
    {  }, 	
  }, 	
} 	

Which is the chunk on the top right of the image of chunks

[BlackYps]

Very nice! How will the ai deal with the fact that a random location in the chunk can be occupied by mexes?

[Garanas]

Ideally there will be a way to 'break up' an area. As an example: a 8x8 factory can be 'divided' using a chunk of size 8. This can be useful when the build area is blocked (slope, resources, etc)

Of course that logic doesn't exist yet at this moment 😃