I'm not involved with payments, so it's just a guess, but you're using English language in-game. What if you switch it to German for the payment?

Those are “intended” (needed to make new system work for now, but may be changed in future, if abused).

There was a bug in a service that sends fleets back from holding. It was fixed today.



Quests are not affected. This one will finish the mission as soon as Gigalord reaches destination planet.

The game is still in development state. It's unfortunate that changes disrupt your game plans, but I don't think there was a way for an indie Chelyabinsk studio to develop a finished project of this scale before releasing it to public.



That's simply not true. We publish balance changes and announcements in all languages we support, roughly at the same time.
Russian part of playerbase may get the most debate, since it's the largest part and more players ask questions. But we try our best to provide critical info for all players equally.

We apologize for missing our estimate by one day, but even with that there was no guarantee we would apply a patch exactly at 00:00:00 of April 26th. It seems you're taking it too personally and not arguing in good faith.

Local coordinates.



We don't move fleets attached to the satellite with it, so we have to stop the satellite from jumping with prolonged capture process.
(I'm also not sure this is a good mechanic anyway to keep the Entity flying after owner change.)

No, I mean objects that currently can be colonized (free planets, asteroids, PPS/temples, OPS). No new types are added to this category.

Testing is finished, estimated deployment date is Monday, 26.04.2021.

They are doing good work.

I wonder how many people got disqualified from Starcraft tournaments because they dropped an army at defenseless enemy base and killed all their SCVs? Not that many, I'd wager.

Some changes to this feature were required by Bloodthirsty Administration™, please check the first post for updated information.

Most people IRL who call themselves “hunters” are the ones who kill defenseless lumps of meat from afar using advanced weaponry. So he had a point.



These rules do more harm than good, IMO. But that's the choice of the playerbase.

One level of Hangar can cover 80 points of fleet. A Fighter is valued at 1.3 points, meaning each level of Hangar can cover ~60 Fighters. For 1000 Fighters one would need level 16+ Hangar, without accounting for other ships like cargo and recyclers. You can see details at FAS page, accessible from Overview.



Relying strictly on Hangars may work for 1k, but with larger fleet it would be not feasible. On that level, it is better to start investing in defense to protect fleet and resources, or develop a habit of “saving” them manually when you leave the game for several hours or more.

I don't see any value in messing with free planets either, but can't help with that.



I see no changes in base values for terran production in last month. Please check Ally network and other possible dynamic modifiers.

Any Colonization order will require at least 24 hours of hold to take control of the object. Fleet with Colonization order would be placed on hold at the target object after winning a fight against object's defenders. Other holding features will also apply.
While in holding mode, the fleet could be seen in espionage reports (with the same requirements as there are for Defense and Occupation fleets).

While a satellite is being captured, some of its special abilities would be disabled. Starting a teleportation process or Entity jump, as well as changing speed of flight in LC, would become impossible as soon as battle for capture starts. In addition, if the capturing fleet wins the fight, currently started preparations for teleportation or Entity Jump would be canceled, and flight in LC would be stopped.
Functioning of Tribunal, Sensor Phalanx or other special buildings would not be affected by the capture.

For free planets or stations, a fleet would need at least 24 hours of hold as well. Non-friendly fleets trying to colonize same object would engage in a combat.
With longer hold time, the “quality of planetary base” (i.e. building field count) will increase slightly. Unknown planet would be “opened” when a colonizing fleet is put on hold at it (after that, that planet would be able to be spied).

Allied players would be able to hold at the same object with Colonization order. After the first Colonization that finishes successfully, all other fleet will turn back.

Quests that require colonization won't be affected.

SusiS, messages you just sent are displayed using your device time, while other messages are dated with server time. Most likely, it's your device that is out of sync.
If you refresh the dialog, you shouldn't see any time travel.

HardStone, gravity damage isn't tied to stat points. Can you please give more info about those objects? (In PM)

Since the vote options in that topic aren't autotranslated, here's what they say (just in case someone may need it):
«ЗА изменение полномочий НТ» => in favor of changing People's Tribune powers
«ЗА изменение полномочий глав альянсов» => in favor of changing alliance leaders' powers
«ЗА возможность выхода из политики» => in favor of having an option to exclude oneself from politics
«ПРОТИВ всех представленных изменений» => against all presented changes
«Навальный» => Navalny [joke option]

Not a bug.

Moving this to Complaints.

Good news:

Gate interface will be moved to dedicated page, with better navigation and messaging.
- Unified interface for viewing, performing jumps and changing settings (for Gate owners).
- Links to Gates in list for quicker navigation.
- Ability to hide closed Gates from list and other small improvements.

A new mechanism for setting personal access rights will be added instead of current crutch.
- Right now, the only way to personally alter access to Gates involves using ignore list in PM. Since this mechanics is not really related to Gates, we will remove it, adding proper “allow/deny” lists.
- Personal access rights will work separately for each gate and each direction.
- Temporary access changes are also considered.


Bad news:

Jumping through any Gates will require Vespene, which would be taken from jumping fleet's cargo. Jump to any distance will use a standard fuel consumption value (listed in unit's description for each unit).

Jumping to Gates of inactive players will be forbidden.

We don't argue with that. I see a lot of your fleets that were sent to expedition with 999-hour hold. But also several of them with 24-hour hold, including the one you mentioned.



If that's the problem, we would like to know how can we reproduce it, so we can fix that.



Some players still use expeditions for their original purpose (finding random things), and longer expedition hold time also means more fuel consumption, so I don't see the highest value as a good default for everyone.
Maybe as a user setting it will be fine.



I'm afraid it's not possible, since they are for internal use only. I can cite some non-public info about your fleets (like time of arrival, carried resources etc) to you in private, if you wish to verify that we keep information about them.