Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It is not impossible and if you take the "group moves as fast as the slowest" into account with Abraham and his initial 2 hr movement, your chances are not too bad. It also helps to blindly advance the first 4-8 moves and restart quickly if you run into a base.
Yet I haven't "beat" Chapter 5 either. Why?
"Fatal Memory Error" crashed me to desktop exactly 4 times. The final time literally as I was entering the camp. This is why you can't release rougelikes when they're unfinished! I have to say I'm disappointed the game was released like this.
Furthermore, always send one scout one field ahead, if they don't return, it means they found an enemy base, wait one hour for them (they will return by then, as long as you only send them one area ahead), attack and take over the base. Always hand out water immediatly so you aren't slowed down. Might as well kill Abraham right at the start, he will probably kill himself next time you rest (and I'm pretty sure you have to do that) anyways.
The biggest problem I had was really before I did the scouting, because of bases. With that, it's really not that difficult.
It's not always SE, the direction of the base camp is changes with each playthrough. NE-SE-NW-SW.
Since the game is literally broken, that's rather a moot point. I would've been part of the people agruing that it is "good", but I can't get behind this game until the Devs release a hotfix.
Well, that's what happened to me (twice), anyways. It's one thing to have nearly an hour flushed down the toilet because you screwed up, but to lose this long, tedious, unenjoyable level due to the game messing up is another story entirely.
It seems to randomize things. As a workaround, I opened the game's folder and edited ../Chapter5/p5_control.ini
[settings0] appears to be the "original difficulty" section and the first entry map_size controls how many map tiles the level has.
Setting this to 10 allowed me to finish Chapter 5 before the memory leak could get the upper hand and finish the game.
This is obviously cheating you out of beating the chapter properly, but after watching that unskippable intro scene for over 15 times thanks to crashes just before the end, I can certainly live with that.
I just ran into the deadline in this chapter at the end of an as-close-to-pristine-as-it-will-get journey, despite the fact I rushed through the last 30 hours without scouting.
To be exact, I had a positive signal response on every single screen beyond the first 6. I got exactly not more nor less resources than I need. Proper movement speed (above "bad") was a constant.
I can only assume that RNG also applies to the actual distance you have to travel, because this attempt described above was practically impossible without killing someone.
(Mathematically it could work if the base was 2 screens from my final position, but not to forget the improbability of RNG luck I had along the whole way.)