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






You can take a look at the new campaign first. :)
Hope you will fix it, cause I really look forward to play it :D
No, this only happened once. The first attempt where I did not use the explosion disabling option.
Passed the mission. Feelings are controversial.
Initial defense. If you get too close to the “front line”, 2 tankers climb into each passage. The defense is swept away in an instant.
Disabling explosions works strangely. After loading a save, they begin to act like an anti-personnel mine.
The final boss is "thin". There is a map called "Maxima Basin". There's a final bug with insane health recovery.
Landing reinforcements one fighter at a time looks ridiculous. A large transport designed for 2 full compartments brings 1 crazy person. I would understand if there were 4 of them.
I think it would not be amiss to add, as an “additional task,” an order to help in holding other sectors of the defense.
У меня нет идеи, почему это происходит. Это всегда происходит в одних и тех же местах? У меня такого не происходит.
As for the explosions: they in and of themselves can still be an interesting addition when implemented as "beware any unexploded munitions" as one-time nasty surprise to anyone who gets too close. But overall the changes you mentioned definitely make the mission far more player-friendly.
You are correct about my path. My issue is that there was no warning that the game expects me to take the middle path straight to the bug boss. Hence my suggestion to use markers for example.
On a positive note, I absolutely love how you integrated the Starship Troopers FPS game's voice-lines. They really touched a nostalgic note there.
b) Unless I have missed something somewhere I dont really recall the commander telling me to use a specific path, so I am really not sure what the official route is supposed to be. And flanking an enemy or coming up at them from a less guarded direction is considered cheating in a game that leans heavily into advantageous positioning? That is bit of a questionable design too I dare say. It could help to mark a specific path with flares and maybe an added mechanic where the commander tells us they will increase the pressure on bug flanks to lure them away from the center so we can rush their main hive entrance and kill the commander. I really did not see any dialogue about having to use one very specific path nor have I seen any markers like those used to point to where the defensive lines need to be reinforced in the first part of the mission.
a) I might be paranoid but I believe I saw at least one relatively wide area undergoing carpet bombing, then those miniature craters disappearing before it being bombarded again, somewhere past the right-most forward control point. The bug plasma gives the battle some atmosphere for sure, but friendly fire from bombing runs during an ordered advance? Im afraid that is not really a thing.
b) He ate the whole map. I didnt really time it but running from him all the way to the base and then across it took more than 10 seconds for sure.
B) Since you're taking a non-official route or "cheating," the trigger to deactivate invincibility isn't activated. You also miss a cutscene by not taking the official path.
Regardless, I'll update the map today to prevent attacking the bug commander from the side, and I'll add an option to disable the artillery.
understood!
and I think killed human commend, noting happen, is a bug, after I played new version, all things become no problem.
thank you!
@Boriss
b)he's invulnerable have time limit , I think about 10 seconds(count after you attack it.), after times up, you can harm it.
so just send a troopers and say: come to catch me, you bad girl~
loved your maps outside of this one. keep it up!
a) Horrible mission design choice here - losing units without any chance of replenishing them to random plasma and air strikes with little in the way of telling where stuff is going to land results in autolose
- not sure who considers that fun but slot machines usually come with a disclaimer.
b) Attacked the bug commander, came up at him from the side, turned out he's invulnerable and he ate the whole map, literally. If the objective is to kill it, why make it invulnerable? If it is not, why is it stated as being the objective?
https://youtu.be/7mWKY6z3vF8?si=FAVT1huK9u1RL_it
Why do you have to kill the human Commander? If you trust the Bugs, it's because the human Commander naturally isn't thrilled about it and will try everything to stop you, so it's necessary to kill him.
I like it!
hope you make more new maps!
but it seems have a bug: if I trust bugs, after I killed human commend, noting happen.
(and I don't know why I have to kill them, maybe can more description?)