Giraffasaur_

This is impressively thorough and well-written, great work! Thank you for helping more pilots ease into opportunities they never knew they had.

Hey there, sorry to hear this. I will add this to the books, but please keep in mind it is unlikely we will be visiting this for a while since we are focused on EVERSPACE 2 currently. Regardless, having it cataloged will move us forward once we can. Thanks for your report.

Hey there, I posted on your Steam forum thread; thanks for the report. If you haven't checked the Steam post, the short of it is this: We had a similar report about 4 years ago in a Discord conversation. The specifics of the incident weren't entirely sorted, but the user was able to resolve the issue by turning off his overclocking. Might be worth a try?

The console versions are also being migrated to UE5 so we can continue supporting them, too.

You're asking for added features to change how the game is meant to be experienced, and it simply was not in the vision for the game.

For example, let's look at Pac Man. When beating Pac Man, should the devs provide the player the ability to despawn ghosts, or make 100 ghosts, or make Pac Man invincible, or make all the dots into power pellets, or have fruit appear every second, or be provided a map editor to make their own maze? Because the game doesn't have these things, does that somehow mean the devs are looking over the player's shoulders telling them they're playing wrong or tying their hands?

Cheat codes can inadvertently burnout players by experiencing all the content really fast in a matter that wasn't intended. Even as end-game unlockable content, this can remove any need to replay a game, and replayability is a foundational pillar of EVERSPACE. Sometimes having a sandbox mode or unlockable can be a good thing, but not always. Skyrim obviously doe...

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.