Developer oversight : Siege
I know that I will be told that this is the bugs forum, and that this is not a bug.
My feeling is that some vital code has been left out. If that is not a bug, it is an ommission.
Devs, I don't know if you're aware, but a considerable number of Siege's players have been playing on the New Legacy shard. You have stated that, when the season is over, transfers to Siege and Mugen will not be possible.
I would like to ask you to reconsider. Siege needs new players just as much as any shard does. By leaving us out of the transfer process, you are actively making Siege less appealing to New Legacy players, and you are driving players to other shards.
Many of the players I have spoken to have said that they would be willing to open an additional account, purely so that they could have an open character slot on Siege. There is no incentive to do that, if transfers are not possible. Granted, some of those accounts would have been Endless Journey accounts - but some would not, and that goes directly to your bottom line.
There is an additional problem. If a player, who predominantly plays Siege has not realised that transfers are not possible, reaches the end of the season and wants to keep their New Legacy items and pets, their only option will be to pick a different shard. At this point, their incentive to keep playing Siege is reduced. The scale of that reduction will differ from player to player, but that reduction will certainly be there. You are actively harming Siege's population with this decision.
Please reconsider the decision to leave Siege and Mugen out of the transfer process. I think everbody fully understands the need to keep those shards out of the standard character transfer process - but this is not that process. Even if it is the same code base, I cannot believe it is much more work than changing a statement along the lines of "If DestinationShard = Siege" to "if DestinationShard = Siege and OriginalShard = NL"
Thank you for listening, and I really do hope you'll reconsider.
