Avatar
-1
anonymous
  • Not a Bug

Unfortunately, this isn't a bug, just confusing design.

The Banshee is trying to go to the Red Core Shard at the top of the map and the shortest available route is through your dungeon, but it's just a bit too narrow. You could either claim more of the middle of the map or make wider corridors to stop them blowing up near your core.

Thanks for letting us know, please let us know if you have any further issues

Avatar
anonymous
  • Under Review

Thanks, I'll take a look in the morning 

Avatar
Leïna

1 group stage volcansnow_20190429112014

1 group stage volcansnow_20190429112014.meta

Don't worry about fixing it in my save though, I already successfully completed the level, so... I'm just sending so you can check where the bug might lie
Avatar
anonymous
  • Pending Customer

Hey Leïna,

Please send the save file over and I'll see if I can work out what's going on.

Save files can be located at the following locations:


Windows

C:\Program Files (x86)\Steam\userdata\Your User ID\230190\remote

OS X

~/Library/application support/steam/userdata/Your User ID/230190/remote

Linux

~/.local/share/Steam/userdata/userdata/Your User ID/230190/remote


You will need to add both the save file & the metafile.

These save files will not have the display name that you gave them whilst saving, they will reference the level and a timestamp:

[level_number][map_name][level_name][timestamp]

4 bonus round cornucopia_20180418165553

4 bonus round cornucopia_20180418165553.meta

If you have multiple saves with very similar names, then simply sort you save files by date and you should be able to find your most recent that way.

    Avatar
    Leïna

    hi, I am playing as of 29/04/2019 and I have the same exact problem. I claimed a Nether shrine and the banshees are going toward my dungeon core (not shard, CORE) Saved the game if you want to see it in action.

    Avatar
    Lee "Noontide" Moon
    • Completed - Resolved
    Avatar
    Lee "Noontide" Moon
    • Completed - Next Patch

    I'm told this should be resolved in the latest internal versions.