Difference between revisions of "Map generator"
|Line 64:||Line 64:|
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console#Useful_commands_.28cheats.29|Console commands]].
===Map-width and -height===
===Map-width and -height===
Revision as of 21:42, 24 October 2016
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.
- 1 How it works
- 2 Generation
- 3 Generating new Chunks
- 4 See also
How it works
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.
Everything above a defined level defines the existing (or non-existing) features of some type of terrain.
The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.
The top row
This is not, how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.
This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.
What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources. Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.
High frequency: For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world. For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.
Low frequency: For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point. For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.
In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.
This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid enemy expansion due to the much higher number of nest clusters.
This defines the size of generated ore patches and water through defining "levels."
It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.
It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.
Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.
This defines the actual content of each generated ore patch, oil field, and Enemies' base drops, through changing the "height" of the wave.
Note that with bases this does not make them more difficult, but rather increases the Alien artifact yield.
The left column
- Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
- Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
- Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
- Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!
The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.
It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.
Map-width and -height
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.
Map seed / Map Exchange String
- Map Seed
- Random number generator seed
- Map Exchange String
- All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).
So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.
Map Exchange String
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA ADAFR8w0Q=<<<
There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807
Where can I use this string?
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.
Where can I get this string from?
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.
From the article which describes the generation:
Top: Normal settings, Middle: The same, but with higher frequency (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased size.
The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources. The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.
This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.
Generating new Chunks
A map is endless by default, though its size can be limited by height and width - see above.
Because it is technically endless, the whole map isn't generated from the start. A new Chunk of map is generated only when needed.
Generating Invisible Chunks (Fog of War)
Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).
Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.
Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".
Generating Visible Chunks
A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the Radar entity. When a visible chunk is generated there might be also invisible generated.
An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.
The player can limit the map size (limited width and height). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!
A map is not bigger than this, there are also no invisible chunks generated beyond that limits.
Everything around the map-limits is considered water. The player can place a Pump at the edge of such a map and it will suck water out of nothing.
If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference when these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.
Maximum Map Size and used Memory
The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 game-minutes (=4 hours) by train to reach that border from the center. So we can speak here from "endless".
Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.
The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.
Maps bigger than the active available RAM?
Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. (How to store 4 trillion square tiles of map in just 8 GB RAM)