Is my game/mission impossible to complete (Swamp DLC)

[MrGowdy]

Including a short YouTube link since steam (as far as I can tell) doesn't let you directly insert screen snips?

In any case, mission says to kill a base which spawned off the map. I've unloaded countless missiles and ammo towards the base. I've built towers as close as I can to auto-attack (they don't).

I've waited around for multiple rounds of "your base is under attack" triggers.

As far as I can tell, mission isn't possible to complete.

https://www.youtube.com/watch?v=G_Q6KN4NfHc

[bosskrm]

hi, I have the same problem, the map of the area did not open further.

[Rider of Retarded Lion Prince]

Same, did try a new game and got the same problem so now i have 2 save files with the same bug.
Hoping for answer but until they update the game i will play something els

[Ezequiel]

The same thing happens to me, I got to that mission and I can't continue because it's off the map. WHO IS RESPONSIBLE?

[Ezequiel]

Originally posted by bosskrm:

hi, I have the same problem, the map of the area did not open further.

I HAVE THE SAME PROBLEM :(

[Morbius]

A lot of people had this issue, there is a thread about it here with replies from the dev

https://steamcommunity.com/app/780310/discussions/0/4355625041396556897/

Basically the fix is to use the ingame command console to destroy it, allowing the quest to progress.

Originally posted by voidreaver:

Feel free to send me your save files, but here's the manual on how to do it yourselves:

1) Save the game right before you plan to go and 'kill' the mound.
2) enter these commands into the console:
cheat_god_mode 1
cheat_no_clip 1
camera_enable_zoom 1
camera_disable_limits_clampign 1
3) Walk up to the mound, don't kill it.
4) Open the console and type in debug_entity_picker 1
5) select the mound with the picker and copy it's entity ID
6) You can now use the cheat_remove_entity XXXXXXX command where XXXXXX is the ID of that entity.

It's best to use the removal command after loading the save file you input in point 1 ofthis instruction.

If you don't feel confident enough messing with this, just send the files to me and I'll get them working. However, I am off for the weekend, so I will get back to you on Monday.

[andthebluefish]

You can mark an objective as completed with show_flow_graph_screen command, or restart the map with any suitable method.

[bosskrm]

Originally posted by Morbius:

A lot of people had this issue, there is a thread about it here with replies from the dev

https://steamcommunity.com/app/780310/discussions/0/4355625041396556897/

Basically the fix is to use the ingame command console to destroy it, allowing the quest to progress.

Originally posted by voidreaver:

Feel free to send me your save files, but here's the manual on how to do it yourselves:

1) Save the game right before you plan to go and 'kill' the mound.
2) enter these commands into the console:
cheat_god_mode 1
cheat_no_clip 1
camera_enable_zoom 1
camera_disable_limits_clampign 1
3) Walk up to the mound, don't kill it.
4) Open the console and type in debug_entity_picker 1
5) select the mound with the picker and copy it's entity ID
6) You can now use the cheat_remove_entity XXXXXXX command where XXXXXX is the ID of that entity.

It's best to use the removal command after loading the save file you input in point 1 ofthis instruction.

If you don't feel confident enough messing with this, just send the files to me and I'll get them working. However, I am off for the weekend, so I will get back to you on Monday.

I have 'syntasys error' for this command 'camera_disable_limits_clampign 1'.

[dj8472]

Originally posted by bosskrm:

I have 'syntasys error' for this command 'camera_disable_limits_clampign 1'.

The console has an auto suggest, if you just put in limit the first option is camera_disable_limits_clamping

syntax error means you spelt something wrong

[MrGowdy]

Just FYI, this is a known issue. There are some workarounds (sending saves to the developer for a custom command or entering other console commands to "fix" the issue or at least progress.

Restarting a new game, reloading the save, anything other than console commands will NOT fix the issue. The enemy 'entity' is being spawned outside the playable area. EVENTUALLY this area becomes available, which is why it can spawn there. They just had a bug that let it spawn where you can't get to it yet.

[Gorem]

I really don't understand why after 2 DLC's they made the third DLC feel like the game is back in early access again. Was there no quality control done on the 3rd DLC that added nothing to the game besides bugs crashes and power creep?

While still ignoring the fans and continuing to add nothing of value to the game - no coop, no after end game content.

[MrGowdy]

Originally posted by Gorem:

I really don't understand why after 2 DLC's they made the third DLC feel like the game is back in early access again. Was there no quality control done on the 3rd DLC that added nothing to the game besides bugs crashes and power creep?

While still ignoring the fans and continuing to add nothing of value to the game - no coop, no after end game content.

I think the issue is pretty limited? I can't imagine that many people are hard-locked on this mission otherwise they would have caught it (or we would see a lot more complaints).

As for what they've done with DLC. I do agree. The game is great, I enjoy it, but they haven't added anything meaningful in my eyes. Considering once you "solve" brutal, the game gets pretty easy and there isn't much reason to keep playing or building.

In my recent Brutal run, I was able to fire up the rift gate event and go AFK. Didn't lose a single wall. Also, I didn't build 90% of the weapons available because none of them felt very interesting or necessary. Best melee physical sword and melee laser sword.... and rocket launcher or similar and done. Maybe toss out a grenade here and there for funzies.