Everspace 2 Dev Tracker

Because the overarching intent is to futureproof to continue supporting, this means for continued support. The difference in engine shouldn't change much (if anything) since we aren't changing assets at all. After all has been migrated, it should be the exact same game, just with a sexier engine under the hood of it with mechanics standing by.

We use Blueprints quite a lot, so the process has currently been mild pertaining to the codebase. Hopefully that doesn't change, because there's a lot of work to do!

Edit: Next stream is this Friday, January 5th.

For EVERSPACE 1, you can reset the game through the menus.

Options > Game > Reset Game

This will completely wipe your save, thus starting you from the very beginning with the tutorial.

Ah, I see the confusion now. For all intents and purposes, Okkar are treated as hostile targets, made a bit more skittish due to their lore. As such, uncontrolled explosions will trigger them into fighting the player.

Otherwise, the Vigilante set EMP explosion bonus is one we are evaluating. It seems likely we'll adjust this.

Generally speaking this is our mindset as well, but we wanted to give favor to the player for the more controlled parts of the experience versus the randomized ones. Crit Happens and Symphony of Destruction have a randomized chance to cause an explosion, so these will only damage enemies in the area. A flak cannon, however, is very much intended to hit everything in the area, and will do so when used. Randomized chance at splash = only damage enemies, guaranteed splash = will damage everything.

Swapping loadouts more easily is something we've seen requested a number of times and have explored internally; there are some significant technical limitations that have made this far more difficult to implement than we'd like so it's not something we can guarantee will happen, but know that it's a nice-to-have we'd like to get to, if time allows.

We did some testing and the perks Crit Happens and Symphony of Destruction do not hit neutral targets, which is working as intended.

Bird's Nest is an explosive, AoE weapon. If you're launching this into a battle, it very much would damage allies in the area. This is working as intended, much like using any other secondary mine that explodes.

An Outlaw Viper exploding leaving a corrosive area is the natural outcome of the vessel, friend or foe, based on the ship's trait. This is working as intended.

We're still evaluating a couple other instances to make sure we're giving the advantage to the player, but please keep in mind that weapons putting emphasis on splash damage are very much intended to damage everything in the area, friend or foe.

On it!

To let you in on our mentality, we went back and fourth on the idea of splash damage affecting everything in the area, or only enemies in that area. This raised some controversy internally because we both wanted players to not accidentally aggro neutrals/allies while at the same time feeling like players would recognize a splash damage weapon would hit neutrals/allies; we had to make some decisive actions to what made sense and where.

Certain, intentional splash damage effects only affect enemies (like the EMP device) while others would splash everything (like flak cannons). That said, perks that make everything have splash damage change situations to what you've described would occur; even if the player doesn't want to hit allies, now they almost don't have a choice. Hmmmm. Based on your feedback here, it seems we need to revisit some of this and ensure it is working as intended and feels good. Thanks for sharing your thoughts; here's hoping we can make this feel better....

Hey there, I sent you a chat. If you can send me your saves I'll see what we can do. Let me know if you need any assistance on packaging up the saves to send our way.

Navigating around the issue with a prior save is the only work-around that comes to mind. There's a chance we might be able to "fix" your save file if you want to try that first thing tomorrow.

That definitely appears to be bugged, yikes! I'll write this down for inspecting and see if we can remove it. For the time being, do you have a prior autosave to skirt around the issue?

Hey pilots, some context and action is needed here.

This user was banned from Discord and Livestreams because of excessive manipulation, gaslighting and misdirection of the Rockfish team and community, blatant victimhood to garner attention and rally support, chronic interrupting, cherry-picking, inflammatory remarks against certain users including our community team, and threatening the team itself.

The behaviors listed above do not appear to have ceased. Since these antics will not be tolerated, the user is being removed. That said, discussions surrounding what EVERSPACE 2 has failed at is great to continue in any degree or capacity; criticism has been a huge part of helping strengthen the game through early access and beyond. This ban is not about this topic but rather about protecting the community here - both from the user and for the user himself.

Thanks for your time and understanding.

Thanks for the report; this is a location prone to choppy performance, and we have this on your list to see if we can optimize it further.

We cover all channels regardless, but responses are a tad faster on Discord due to the nature of having a live chat. No worries either way!

We'll definitely look into this one, thanks for bringing it up.

Quick note:
This is live for Steam, Mac, Game Pass and Playstation 5.
This is NOT live yet for XSX. We need to get through some small adjustments for certification; we will follow-up once it is available.