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
I don't play on PS4, but how cool is that!
go get your free slots while you can!!!!
cant you still manually edit your save files anyway?
In general Terminus deletes all “non-Galaxy-X” space station and other players’ bases destinations whenever you TP out of Galaxy X. And the bug prevents you from adding any non-Galaxy-X space station or other players’ bases destinations.
This is a big problem since many of us were not in our primary galaxy when we updated to 2.11, so now we cannot go back without losing tons of TP destinations.
In general I think Terminus should let you add space station and other players’ bases as destinations no matter what galaxy they’re in, but as of now, it does not do that.
We have been waiting since the launch of Beyond for a fix to this major bug. Since 2.11 some of us are now stranded outside of Euclid, since if we go back it deletes all our data.
I submitted a long bug report on this issue on Thursday of last week to Zendesk yet I do not see any fix for it in these patch notes.
I can’t really play Beyond until this is fixed since I don’t want a bunch of data to get deleted out of my saves. And I’m not the only one in this situation.
Is there any possible way you can please fix this bug so the game stops deleting terminus destinations? 2.11 was supposed to have fixed it, but all it did was change which galaxies are affected by the bug.
Seems like this should not require much code to fix... maybe even just a one-liner!
Please...