EXAMPLE: base_size 9
number_of_tiles[0-1] = 19x19 square (361)
number_of_tiles 2 = 19x19 square + 2 tiles starting on the rightmost corner (bottom side)
number_of_tiles 3, 19x19 square + 4 tiles starting on the right corner and migrating clockwise
number_of_tiles 11 makes a 19x20 square (380 tiles), 19 along top/bottom and 20 along left/right side
number_of_tiles 12 makes a 19x20 square, +3 tiles (383) on the right side, ignoring the rightmost corner tile
I'm not sure what function would map this, since it looks more like a programming function taking from a whatever c programmers call their arrays.
current chart, using base_size 9
f(0) = 361
f(1) = 361
f(2) = 364
f(3) = 366
f(4) = 368
f(5) = 370
f(6) = 372
f(7) = 374
f(8-10) = Untested
f(11) = 380
f(12) = 383
Then I started messing with base_size 0, thinking there's some lower level function working off of number_of_tiles - these functions might not even be connected
But trying with
base_size 0
number_of_tiles 5
lets call this g(X)
g(5) = 4
g(6) = 4
g(7) = 6
g(8) = 6
g(9) = 9
So does anyone know how these work??
edit
So I found some things about base_size and set_avoid_player_start_areas and number_of_tiles
set_avoid_player_start_areas seems to makes terrain avoid a 19x19 square of player lands, which is equal to base_size 9 number_of_tiles 0. It also seems that you can't place objects with set_place_for_every_player AND terrain_to_place_on on those terrains created with set_avoid_player_start_areas, but I'm not sure why in that case (i could be wrong)
When used with player lands and base_size, number_of_tiles is confusing in really low numbers (10 or less) because I noticed it starts creating from the right corner of player lands, adding to base_size instead of, umm, well before today i always assumed that number_of_tiles went first, then base_size overrides it, but on player lands it seems that it creates the base size first, then it adds the number of tiles starting from the right corner and going towards the bottom corner. Then at some point, it starts from the right corner and goes towards the top corner. And the function governing number of tiles is confusing, it's not equal to the number you use, but some weird function that sometimes takes 2 or 3 tiles for what I put.
USA
katsup or mustard
number_of_tiles
number_of_tiles 2 = 19x19 square + 2 tiles starting on the rightmost corner (bottom side)
number_of_tiles 3, 19x19 square + 4 tiles starting on the right corner and migrating clockwise
number_of_tiles 11 makes a 19x20 square (380 tiles), 19 along top/bottom and 20 along left/right side
number_of_tiles 12 makes a 19x20 square, +3 tiles (383) on the right side, ignoring the rightmost corner tile
I'm not sure what function would map this, since it looks more like a programming function taking from a whatever c programmers call their arrays.
current chart, using base_size 9
f(0) = 361
f(1) = 361
f(2) = 364
f(3) = 366
f(4) = 368
f(5) = 370
f(6) = 372
f(7) = 374
f(8-10) = Untested
f(11) = 380
f(12) = 383
Then I started messing with base_size 0, thinking there's some lower level function working off of number_of_tiles - these functions might not even be connected
But trying with
base_size 0 number_of_tiles N
I don't get anything until N = 5 (returns 4 tiles)base_size 0
number_of_tiles 5
lets call this g(X)
g(5) = 4
g(6) = 4
g(7) = 6
g(8) = 6
g(9) = 9
So does anyone know how these work??
edit
So I found some things about base_size and set_avoid_player_start_areas and number_of_tiles
set_avoid_player_start_areas seems to makes terrain avoid a 19x19 square of player lands, which is equal to base_size 9 number_of_tiles 0. It also seems that you can't place objects with set_place_for_every_player AND terrain_to_place_on on those terrains created with set_avoid_player_start_areas, but I'm not sure why in that case (i could be wrong)
When used with player lands and base_size, number_of_tiles is confusing in really low numbers (10 or less) because I noticed it starts creating from the right corner of player lands, adding to base_size instead of, umm, well before today i always assumed that number_of_tiles went first, then base_size overrides it, but on player lands it seems that it creates the base size first, then it adds the number of tiles starting from the right corner and going towards the bottom corner. Then at some point, it starts from the right corner and goes towards the top corner. And the function governing number of tiles is confusing, it's not equal to the number you use, but some weird function that sometimes takes 2 or 3 tiles for what I put.
USA
katsup or mustard
[This message has been edited by local boi (edited 06-02-2018 @ 08:18 PM).]