162 |
162 |
163 == `object` == |
163 == `object` == |
164 There may be multiple object keys in the file, each one representing one land object. |
164 There may be multiple object keys in the file, each one representing one land object. |
165 |
165 |
166 * `filename`: The object’s filename (without the “.png”). Case-sensitive. |
166 * `filename`: The object’s filename (without the “.png”). Case-sensitive. |
167 * `max`: The maximum number of this object that may be generated in a map (must by between 1 and 32) |
167 * `max`: The maximum number of this object that may be generated in a map (must by between 1 and 32 |
168 * `buriedrec`: A rectangle that must be buried in the terrain (`left, top, width, height`). In version 0.9.23, if all 4 values are 0, the object will be placed on top of the water |
168 * `buriedrects_num`: (optional): Number of rectangles that must be buried in the terrain. If this value is ommitted, a value of 1 is assumed. Only available in version 0.9.23 or later |
|
169 * `buriedrects`: A rectangle that must be buried in the terrain (`left, top, width, height`). In version 0.9.23, if all 4 values are 0, the object will be placed on top of the water |
169 * `minvisible`: The minimum amount of rectangles that must be visible |
170 * `minvisible`: The minimum amount of rectangles that must be visible |
170 * `visiblerec`: list of the rectangles for being visible (`left, top, width, height`) |
171 * `visiblerects`: List of the rectangles for being visible (`left, top, width, height`) |
|
172 |
|
173 Syntax for version 0.9.22, or when you only need 1 buried rectangle: |
171 |
174 |
172 <code>Values: filename, max, buriedrec, minvisible, visiblerec</code> |
175 <code>Values: filename, max, buriedrec, minvisible, visiblerec</code> |
173 |
176 |
174 Here's an example where `visiblerec` and the `buriedrec` are visualized on an ancient picture: |
177 Syntax when using multiple buried rectangles in 0.9.23: |
|
178 |
|
179 <code>Values: filename, max, buriedrects_num, buriedrects, minvisible, visiblerects</code> |
|
180 |
|
181 Here's an example where `visiblerects` and the `buriedrects` are visualized on an ancient picture: |
175 |
182 |
176 https://hedgewars.org/images/avematantheme/hw-avematan.rects.png |
183 https://hedgewars.org/images/avematantheme/hw-avematan.rects.png |
177 |
184 |
178 The large rectangle shows a `visiblerec` and the small one shows a `buriedrec`. |
185 The large rectangle shows a `visiblerects` and the small one shows a `buriedrects`. |
179 |
186 |
180 == `spray` == |
187 == `spray` == |
181 There may be several spray keys in the file, each one representing one spray object. |
188 There may be several spray keys in the file, each one representing one spray object. |
182 The `name` is the case-sensitive name of the PNG file (without the file name suffix) of the graphics file, and `number` is the rough number of instances of this spray that may be added to the map. The number is the average number of sprays that are normally placed on a random medium-sized island. For larger and smaller landscapes, this number will be automatically scaled up or down. Please note that this number only specifies a rough goal, the actual number of created sprays may vary and you may have to play a bit with this number in order to find a good value. |
189 The `name` is the case-sensitive name of the PNG file (without the file name suffix) of the graphics file, and `number` is the rough number of instances of this spray that may be added to the map. The number is the average number of sprays that are normally placed on a random medium-sized island. For larger and smaller landscapes, this number will be automatically scaled up or down. Please note that this number only specifies a rough goal, the actual number of created sprays may vary and you may have to play a bit with this number in order to find a good value. |
183 |
190 |