Dated 1.3.0 notice: console crossplay release was awaiting approval
The May 20 notice labels the PC-to-console crossplay problem “resolved” but also says the correction is pending release approval. Those statements do not prove that the approved build had reached players. Keep this as a dated release-status note until a later publisher source confirms deployment; it is not a claim of a current outage. [1]
1.3.0: dynamic joining fails after a powered-off BRAIN target is destroyed
The same update fixes dynamic joining when a BRAIN target is destroyed while powered off. The note describes that specific state; it does not establish that a failed Join Code, blocked player or platform mismatch is also repaired by it. [1]
1.3.0: some parts of the UI cannot be clicked
The developer identifies faded damage markers as the cause of a particular unclickable-UI problem and lists it as fixed in 1.3.0. Use that context when comparing the report with a mouse or controller problem elsewhere in the interface. [1]
1.3.0: black screen or tally gets stuck as the ship is destroyed
The Maximum Calamity patch lists a correction for the payload system breaking during ship destruction. Its examples include becoming stuck at the tally screen or a black screen. This is the event described by the developer, rather than evidence that every black-screen report has the same cause. [1]
1.1.3: unusually long startup time
The earlier Crossplay update lists long startup times as fixed. This is an older, versioned correction rather than a report of a newly discovered launch problem. [2]
Sources & verification
Platform and version details belong to the individual issue or guide section. A documented workaround may not resolve every case.
- Maximum Calamity - AVAILABLE NOW! official-newsRetrieved
- Update "Crossplay" - AVAILABLE NOW! official-newsRetrieved