Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español - España (Spanska - Spanien)
Español - Latinoamérica (Spanska - Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (Portugisiska – Portugal)
Português - Brasil (Portugisiska - Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (Ukrainska)
Rapportera problem med översättningen
You pick valley, hill, or mountain as per normal.
But then the generated landscape is much, much larger. The player then chooses a boundary within that larger generated landscape, and the rest is cropped out.
Would be a bit of a pain to implement: The save file would need to keep an "offset", and the generator would need to understand that offset for regeneration during save game loading. I think you could limit it to that though, if you then shifted the coordinates by the offset before applying the changes in the save file (such as minning/construction), other parts of code wouldn't need changing. This assumes that the terrain generation algorithm chosen can generate a single square without considering nearby squares. Probably true now, but things like water dynamics can break that assumption.
The other portion would be the terrain selection GUI, I'm not as good with GUI, and couldn't guestimate how hard that'd be. *Should* be moddable via code injection, but it'd certainly be easier if it was done in source.
If a developer comes out and says they won't do that, I might take a stab at it.