[2022] Bugs not mentioned in Trello' known issues

Hey there @Uncle-Sam14

Thanks for reaching out.

We appreciate your opening this thread and raising these issues, however in future, if you could please open a thread for each so we're not having to discuss multiple issues in one place, it'd be appreciated and makes for easier reporting!

As for what's been noted in your initial post;

1. You forgot to resize the different skins of the old airship "Boreas" to 90%

• This is known and has already been forwarded to the team for investigation.

2. You forgot to put the airship ornaments in the cultural tab of the buildings menu (it's only available if tiers category is chosen)

• There we some issues with the new ornaments which were addressed in GU15.1 - if the above still persists, could you please capture some screenshot examples and we'll get this raised up?

3. Maybe that's a design issue, but in the scenario Clash of Couriers which is supposed to challenge the player into building a network of mail delivering ships. It's easily possible to get gold and all the 3 badges by only settling one island and having a single mail route delivering mail back and forth between the main island and the second!

• Would it be possible to please capture a video / screenshot of this setup working in this manner? As you say, this appears to be by design, but an example would be appreciated for us to raise as feedback if the scenario can be easily completed in this way.

4. The airships would rather wait for a busy air platform to unload trade cargo rather than use a free pier nearby, putting lots of strain on the slow (2t/secs) air platform. (An option to make the air platform exclusive for mail would be useful, or for the airships to chose a free pier to unload/load cargo).

• Feedback on the loading times of airship platforms has already been noted to the team for consideration - I've passed your comments on as part of this.

@ryner30 - thanks for updating your post!

@AuddieD - We're aware of these issues and have a thread tracking them here.

@johnny19w - This issue has already already been reported to the team.

Thanks guys!