Suggestion: Funcom, for heavens sake, immediately stop all decay timers on all servers and give yourself time for emergency measures and hotfixes, e.g. cleaning caches and cloud slots for a new clean UE4 ->UE5 handshake. Why? Read …
The most most catastrophic bug leads to lost clan base, clan leader, clanmates and all thralls due to an incomplete or corrupted “digital handshake” between UE4 and UE5.
As only bots have been answering to our bug reports in the last 10 days, we are all getting messages like “Your issue has been resolved and closed, if you still have issues go to the support link listed”…which sends us to DUNE: AWAKENING support… (huh?).
The bots are bugged themselves because they cannot check if the hand-shake between your old (UE4) and new Sign-In (UE5) was successful as the new Sign-In for UE5 was not publicly visible until 2 days ago and thus could not be added to the Ticket, forcing the bots to use the old UE4 sign-ins. But, the old UE4 engine actually signed out with a message saying “This transfer has been successful”.
Therefore the bots should have been instructed to check both your old AND new Sign-In (the so-called “hand-shake” of both engines).
This happened to everybody who is missing his main char on his actual destination server - be it official or not. For everybody missing his char on the new UE5 platform.
However, it is important to know that our main chars are not missing, they are still locked in a transfer cloud or sitting on another server we may have visited while searching for a better location or reuniting with friends.
The data of our chars is still there and if FUNCOM lets the decay timer run through to Zero, all these still sitting “data ghosts” of our chars will either be destroyed imminently or by the next “clean-up script run” with the next new restart at early morning.
Algorithmic explanation simplified: During the transfer and migration, while modifying the sandbox lines, the local database pointer probably corrupted in many cases right before it could cleanly overwrite or clear the cloud slot.
The system now detects an orphaned character ID bound to our account in the cloud cache, which is triggering the hard lock “CHARACTER TRANSFER IS NOT ALLOWED ON THIS SERVER”. It thinks we are trying to illegally inject or duplicate a character token on a server that already holds our ghost data. The corrupted digital handshake has a long rat tail caused by a not fully transferred “ghost” clan leader. Lead may go to an EPIC clan mate or co-founder and is lost. The clan’s name remains on the base, but the base can’t be entered. This is a permanent loss of control in contrast to the internediate lag loss of control ANYGAMER mentioned.
We cannot manually ourselves fix the cloud-side lock without database access, we can only force the local client to clear its localized cache loop to see if the cloud overrides it. Most players will not have the data base knowledge or risk being banned when Funcom’s night-time scripts hunt down false manipulations of the local system. The fix has to be done by database managers…
End