Tutorial: how to actually capture the flagship?

[Gemberkoekje]

Hi there,

I'm in the tutorial (tutorial 4 i think) and I'm at step 8 of 11.

According to the tutorial I should do the following:
- Move my transport flagship from my original system to the new system
- Build a Logistical Command station
- The Command station should automatically capture the neutral Flagship in the system.

Well, I built it... but no capturing is happening. Did something break? Am I missing something? Did the game change since the tutorial was made?

Thanks in advance,

~ Gemberkoekje

[Strategic Sage]

The tutorial is fine, and you are fine.  Unfortunately there is a bug right now which there will be a hotfix out for hopefully very soon.  It messes up capturing/repairing flagships (and maybe other things, but that's the one thing that I know it for sure does).  So assuming you are on version 1.002 here, I'd recommend either waiting for the hotfix or going back to 1.001 which would allow you to finish the tutorial.   Game-Right-click-properties-Betas-opt into the last stable build to do that on Steam.

[RocketAssistedPuffin]

Yep, strange and highly annoying error when the update went out, meaning it took the old files instead of the most recent, working ones.

Here for info: https://steamcommunity.com/app/573410/discussions/0/1693843461185438537/

(Thanks Thotimx!)

[RocketAssistedPuffin]

Okay so apparently you can still play on 1.002, but you need to be looking at a different planet than the thing that needs repaired. Odd useful quirk of background processing I think.

Thanks to Smaug and Gem for both reporting this workaround!

[Strategic Sage]

You're welcome Puffin - FWIW I think you're doing a really good job minimizing the damage by being transparent and staying on top of communication on this.  There's a lot of people that can't be reached of course because they'll just get irritated (and hopefully come back to the game in the future and give it another try) and it is a big frustration for new players to not have it work.  I put out a short demonstration video of the workaround to try and also spread the word on that, pending the hotfix getting out there to resolve it for good.