It's clear Reforged had a forced release date

[DrSuperGood-1327]

@Satan915-1871

So why not just build upon the classic client for Reforged and integrate that version into the Battle.net launcher? They put themselves in a bigger hole with more work to do by making a new client. Or at least, why not implement or copy over the features in the way they worked in the classic client (ladder, profiles, clans, custom campaigns) until the new replacements are ready?

They did build upon the legacy client. Which is to be expected since it was an update. No new client was made, only the existing one changed.

They could not use the old features as those relied on legacy BattleNet. Trying to mix and match legacy BattleNet with BattleNet “2.0” would not work well due to their different requirements and method of operation.

Honestly I am not sure why custom campaigns are still missing.

@Satan915-1871

Can you explain what you mean by this? Because what does licensing have to do with causing desyncs?

This was mentioned in the various patch notes. People running Reforged graphics playing with Classic graphics were prone to desync with each other soon after launch. Although the exact reasons can only be speculated, it was either because of the clients loading different assets, or because the graphic part of the engine produced different results. If the latter cause then the need for such strict separation of the graphic engine was for licencing, to make it impossible to play Reforged graphics, even with classic assets, without owning a Reforged licence.

If they would have kept a single graphic engine for both classic and reforged, and just tied the new assets to the reforged licence, then it is possible that some desync bugs would have not happened. It also would have even made classic look better, and the lack of working blob shadows would be less noticeable.

@arcsaber-21354

Except one version was mature and completely functional, for which you basically only needed to apply balance patches, which are basically textfiles, and the other version is incomplete to this day. The choice to abandon the classic client was not logical from the perspective of a player.

For inter-compatibility they would need to update both versions in parallel. Especially with regard to online services to enable the removal of the legacy BattleNet.