Updates to user account handling and e-mails
- Tuned the game world's initial airport slot growth mechanism to make sure the standard slot amount is reached after two full game years (steady growth at random dates during this period).
- The e-mail template at the main website is updated to be more mobile-compatible, and better formatted across different devices and e-mail clients.
- The main website e-mail templates are now dark-mode compatible (depending a bit on your e-mail client).
- Updated the layout of the in-game billing notification/warning emails to show the relevant information more clearly.
- AirwaySim newsletter is updated with a new more mobile-compatible layout with dark-mode support (similar to other site e-mails).
- Account activation and password reminder processes at the main website improved with additional security layers and technical improvements.
- User account inactivity checks re-activated. The system will send a reminder mail to keep the user account alive if it has been inactive (no logins) for more than 180 days. A second reminder is sent at 270 days, and the account closure happens automatically after 360 days of inactivity. The email includes a direct one-click link to retain the account activity status. (n.b. unactivated or otherwise "pending" accounts are removed faster without separate reminder e-mail)
- Some other technical improvements and changes to the login handling at the main website. The login session timeouts after 60 minutes of inactivity (no clicks) if the
"Always stay logged in"
checkbox was not checked.
- Improved the handling of our anti-spam ban list (provided by 3rd party) to avoid false-positives.
- Fleet Commonality page grouped data incorrectly for fleet groups with multiple different manufacturer names (e.g. data for McDonnell Douglas MD-81 and Boeing 717 were shown twice); did not affect cost calculation, UI display issue only.
- Newsletter subscription button did not work at My Account page.
- Automatic login timeout handler did not always work properly, and could have booted the user out even he was active at the site.
