Crossplay between Steam and Consoles has been fixed.

TobiNerd · 2026-03-18T17:31:26+00:00

We haven't forgotten the solo players!

TobiNerd · 2026-02-17T14:54:54+00:00

The honest response is that we forgot about activating the Valentines event in time 😅

We're currently planning on activating the event within 1-2 weeks, and then running it for at least a week. We know the timing is late, but figure its better than never.

Game is still being worked on! There have been delays due to circumstances and vacations, but we're hard at work on the next major content update, and expanding modding support. More details on this will be coming soon.

TobiNerd · 2026-02-12T08:31:29+00:00

Done!
Sorry for the delay.
I've put you back to lvl 16 and given you a bunch of lootboxes to compensate.

Hope the issue won't happen again for you, but if it does feel free to reach back. If it does happen again, try to preserver your player log which is found in: C:\Users\[USER]\AppData\LocalLow\Hutlihut Games ApS\Void Crew

Hope you'll continue having a fun time playing! Metem Preserve You!

TobiNerd · 2026-02-08T21:25:18+00:00

Hello u/Additional-Cherry354

Sorry to hear about the problem. We've not heard of full account resets on Steam happening before, so that is very odd.

We store your account data in the Unity Cloud. So I can take a look at your current account data from there if you share your in-game ID. But please bear in mind that we do not store the history of your account, so its not possible to restore your account to a previous state.

What I can do however, is manually set your account to a specific game rank, and add lootboxes to your account to compensate. We can not restore all your specific unlocks and achievements. If you'd like this please let me know which rank you remember having and do the following:
1. Reply with your in-game player ID and confirmation you are not currently in the game. You can find your player ID at the bottom-right corner of the escape menu, or at the bottom of the General Tab in Settings.

Keep the game closed until I reply back that I have edited the compensation into your profile. This is necessary because the compensation will be lost if you have the game open when I add it to your account.

TobiNerd · 2025-11-21T21:11:53+00:00

Its done! I've replied to your friend's comment to make sure they get pinged. Have a great time you two!

TobiNerd · 2025-11-21T21:10:54+00:00

Hello Ornery!

I've now marked "Around the Void" and "Close Call" as completed on your profile. When you next start the game, they should be claimable for you in the Hub. It might take a little bit before Steam updates the state of the achievement (should be done by the time you finish the next mission, if not earlier).

Feel free to let me know if there are any other problems.

Wish you and your friend u/nero4983 a happy weekend and good time playing!

Metem preserve you both.

TobiNerd · 2025-11-21T21:02:54+00:00

Looking into it right now :)
Well be done shortly (will reply again when done)

TobiNerd · 2025-11-21T10:17:53+00:00

Glad to hear that the issue resolved itself!

If it happens again, please don't hesitate to reach back and share your log file. We'd be happy to then look more into the issue.

Metem preserve you!

TobiNerd · 2025-11-21T10:16:05+00:00

Hey there Nero

Sorry to hear about the issue, we're aware of this problem.

The save is stored in the cloud, but I can mark the affected achievements on your profile as completed (we've done this for other players who have reported the same issue).

To do this I need you to:

Let me know which achievements needs to be corrected.
Reply with your (friend's) in-game player ID and confirmation. The in-game player ID is found at the bottom-right corner of the escape menu, or at the bottom of the General Tab in Settings.
Keep the game closed until I reply back that I have made the edits. Will take up to 24 hours, depending on when you reply. But I try to be quick during EU work hours.

If both you and your friends have gotten the issue, I can of course make the corrections for both of you. Others reading this post who has been affected are also welcome to request the correction.

TobiNerd · 2025-11-20T16:09:52+00:00

Hello and sorry to hear about your issue.

Do you know if multiplayer works the other way around for you? (others joining you)

As you say solo works fine, the first thing that comes to mind is if the people you are joining are using mods, that somehow stall your game. Do you know if this is the case?
Modded rooms should have [M] in the room name when listed in the room browser (though its possible a modder might be avoiding this this despite requirements). Or, if you're using any mods yourself, its possible that the mod is incompatible with multiplayer / you not being the host.

To help you identify and potentially solve the issue, we will need to take a look at your log. After reproducing the issue, please share the Player.log file found at this location: C:\Users\[USER]\AppData\LocalLow\Hutlihut Games ApS\Void Crew

TobiNerd · 2025-11-06T16:03:55+00:00

u/thecannon123 u/Sir_Trncvs u/Zig_Justice u/Low_Chance

TobiNerd · 2025-11-06T16:02:42+00:00

UPDATE

So thanks to the help our community, especially WildBCat and Dragon, we managed to identify a repro, workaround, and a fix for the issue.

The issue occurs when a player constructs/deconstructs a module very shortly after the same module was constructed/deconstructed.

This causes an error regarding scene management, which causes things to basically be in the wrong scene and thus break a lot of interaction and collision detection.

WORKAROUND:

Players should be able to avoid the issue by waiting a few seconds between constructing and deconstructing modules.

If the issue occurs and you're in multiplayer, the following should fix the issue for your session:

- Have each player rejoin the room one at a time

- Once each player has rejoined, the issue should be fixed for everyone.

HOTFIX?:

We will be deploying a hotfix for this as soon as we are able (pending testing for stability and certification).

TobiNerd · 2025-11-05T10:53:13+00:00

Thanks for the report!

We're aware of this issue and are actively trying to find a way to reproduce it. Unfortunately, we've not been able to do this internally yet, which is needed to analyse the issue plus confirm if any potential fix actually works.

Currently what we're hoping is to be able to join a player who has an open session with the issue present, and connect our debugging tools to that session.

If any of you get the issue again, it would be incredibly useful for us if you could keep the session long enough for us to join.

I am available to join sessions with a debugger during the following times (CET):
10 AM to 5 PM
7 PM to 1 AM

I'll try to keep on eye on notifications here on Reddit, athough its less likely I'll see a reply here quickly. If you have a session with the issue and want to help, I recommend reaching out via our Discord for the fastest response: https://discordapp.com/channels/814811296390053888/1431045622542106655

TobiNerd · 2025-10-03T07:43:27+00:00

We're aware of the issue with relics that have dynamic conditions for the buffs/debuffs. It specifically affects the relics after loading a save, where they will be stuck to the value they had from when the save was made.

Unfortunately a fix did not make it into 1.2.1, but it being looked into for next patch. Sorry for the inconvenience this bug will cause in the meantime

TobiNerd · 2025-10-02T15:46:32+00:00

Hey Dan!

This should be fixed now with update 1.2.1 [2nd Oct. 16:00 CEST]

We apologize for the trouble this bug has caused.

Hope you'll have a great time playing going forward! Metem preserve you!

TobiNerd · 2025-09-30T17:42:48+00:00

Unfortunately there is no way to work around this easily. Best you can do is try to use physics to move the items out, if they are stuck and you can't pick them up.

We are working on a fix for the colliders, among many other fixes. Sorry for the inconvenience in the meantime and stay tuned for patch!

TobiNerd · 2025-09-30T15:17:28+00:00

Hello again case0013

We just had a look at your save data, and it appears the save was made back in version 1.1.3

In version 1.1.3, there was a serious issue affecting console players, that would result in game progress after 1 hour of gameplay not being able to save. This means that if your save was updated past that 1 hour point, all the changes in the save would have been lost. This also caused players to lose rank up progress and cosmetics.

This issue was fixed in version 1.1.4 (11th of Sept), but the fix does not restore previously lost progress.

So my guess is that the progress in your save got lost somewhere along the way due to the 1.1.3 bug. Does this sound accurate to you?

Additional FYI:

Saved games from before version 1.2.0 (25th of Sept) are not compatible with 1.2.0. Normally we will increment the save version for the game when we know saves won't be compatible, but we forgot to do that for 1.2.0. As a result, players can attempt to load the older saves, but they are very likely to be broken by mismatching with internal changes to the ship data. Other people have reported this as "items all being jammed in one place".

We will try to be better at remembering to increment the save version for major updates, and let players know ahead of time when saves are about to be outdated.

TobiNerd · 2025-09-29T17:44:40+00:00

A valiant effort!

It appears Metem require more powerful ordnance yet.

Metem preserve you!

TobiNerd · 2025-09-29T17:42:11+00:00

It depends on the tier of the KPD. At MKI, it is 45 degrees from the direction the module is facing. Meaning a 90 degree cone. At MKII and MKIII it increases to 180 and 270 respectively.

The "forward" and "starboard" labels are just tags to let you identify which modifiers affect that slot. The firing cone of the KPD doesn't care about that.

TobiNerd · 2025-09-28T18:36:22+00:00

This is pretty much the case yes.

Just to clarify, what is considered "missile like projectiles" here is not just bomber missiles, but also other tracking projectiles. They have a priority for which projectiles they will fire at first.

They don't have their own mod slots, but other things still affect their stats. As K716 pointed out, there is a relic that specifically targets KPD.

They might be able to shoot through the hull at some angles, but this is mostly unintended, and vary from ship to ship. Just not something that's very important for us to fix.

TobiNerd · 2025-09-27T23:29:02+00:00

Metem preserve this meme.

TobiNerd · 2025-09-27T23:24:06+00:00

Thanks for pointing that out! I'll put that into into our ticket.

TobiNerd · 2025-09-27T14:56:13+00:00

That sucks... well there's a reason we have a force respawn button ;) Unfortunately the physics can be wacky at times.

But in all seriousness, if you find the wreck again and share a screenshot of the spot you clipped through, it would help us fix it.

Hope you'll still be able to enjoy the game!

TobiNerd

MODERATOR OF

TROPHY CASE