<Ivor>
Auto-translated
I'm not a fan of TE/WT, but if someone really wants to play these versions, their revival is quite possible – at a new technological level, through the Baratorch patcher, and not through ERM.
For example, someone could put together a set of plugins (like Armageddon), and here we have WT, essentially with full simultaneous turn-based gameplay and 100% support for the HD mod (because in this case, the HD mod isn't installed on top of WT, but rather the other way around – WT in the form of plugins is installed on top of the HD mod).
The talk about a new technological level is amusing. VOG is a platform for modding, while the HD mod only offers the ability to connect libraries and some mechanization for creating hooks. Even if we assume that a ready-made WT doesn't exist yet, and there's only a technical specification, it's obvious that it would be easier to implement it on ERM, resorting to low-level programming only in rare cases. Simply put, there are no tools in ERM to implement the functions of the HD mod, so it's natural that Baratorch wasn't interested in VOG. And once a TE/WT mod is already available, saying that it would be easier to rewrite it from scratch than to eliminate incompatibilities with the HD mod is not serious. Moreover, there's no guarantee that the new mod won't conflict with the HD mod, especially regarding simultaneous turns. In both cases, everything will depend on Baratorch's willingness to help resolve incompatibilities, since the HD mod's code is closed. Of course, such an option is quite possible. I myself wrote about this when Mafia started working on mod compatibility. But there's no point in talking about some new level of technological advancement here. Moreover, ERM offers the ability to create interesting maps and templates.
I gave the WT source code to Mafia; he posted it somewhere in public access, like on GitHub. WT is written in ERM, and where ERM was insufficient, Delphi was used. There are no problems with porting to C++; Delphi libraries are no different from C libraries; the main thing is to maintain the format.
As I understand it, when hypothetically making WT and HD compatible, the WT shell as such is not needed. Template selection is available in HD, chat is not needed, and replaying quick saves is also available in HD. And in general, it's necessary to abandon duplicate functions, such as quick operations with stacks.