[2019] PSA — Halloween ships and slots

Greetings, commanders and happy Halloween!

We hope you enjoy the new event and various rewards, such as signals, coal, Free XP and an opportunity to get camos for tier VIII, IX and X ships.

We know that some of you are upset with the necessity to have free slots in port for event ships.

Please take our sincere apology for the inconvenience - this is how ‘tech tree’ ships currently work. As of now, we have no ability to change it, but we will certainly consider this case for the next events with temporary ships.

As a token of appreciation, we’re happy to announce that the slots for the first three ships (Steel Lancet, Rust Nightfall, and Maverick) will stay with you after the event will end. And, of course, slots for other events ships won’t be removed from your accounts.

Good luck and fair seas!

I know that current situation is not ideal, but that is also part of technical limitations of the event ships.
On the other hand, you still can sell regular "Tech Tree" ships, if you want more ships to participate in the event - rewards are okay. And those who aren't interested can just do nothing and just get 3 free port slots at the end of it.

No, it wasn't. First of all - the slots will stay with you anyway, so, it's more of - get a slot now, and use it later as you want. And secondly - you aren't obligtated have to spend dobloons to get slots. Perhaps you may lose some credits freeing up the space, or use coal to get slots, but that's what those free slots are for - so at the end of the even't you'll have more stuff than at the begninning.

They don't — they came with their own slots — that's how event ships always work, and after even's end the ships will leave, but the slots from all "Raid for the Filth" ships will stay. The usual way would've been as with rentals - they come with their own slots, but don't leave them.
If those ships occupied your existing slots - then something must've been terribly wrong and you should write to support for clarification.

Hey. I see the problem there, but for this issue it's better to write to support with your logs (this problem is not universal).
Similar with sound issue.