Mark Poesch heeft zijn .plan over Unreal2Ed geupdate:Well... I've got good news, and I've got bad news... I worked most of yesterday and today on UT and WoT compatibility with U2Ed. I now understand the problems, and for UT, they look solvable... we'll have to hack a bit -- it's messy, but it'll work. But, the picture isn't so bright for WoT. Duane is working on the U2Ed patch for UT now. It'll have a big nasty disclaimer that says, "don't do anything with this, or you'll die"... but, from my testing last Friday, yesterday, and today, maps edited and rebuilt with U2Ed *seem* to be compatible with 405b. In any case, it'll be "use at your own risk." The primary problem I encountered with UT is due to our U2 build being based on Epic's 400 version of the engine. The latest UT 405b patch contains a variety of references to things that "don't exist yet" in our build. By including our 400 copy of BotPack.u we maintain compatibility... barely... as I said, it's a hack. For WoT, the situation is much worse. WoT contains C++ and script modifications that are not in Epic's engine code or in our U2 build. That means that WoT-specific components are expecting things in the Engine.u/dll that don't exist in our U2 400 build -- the build we're currently using to compile U2Ed. Resolving the Unreal2 build's incompatibility with The Wheel of Time isn't going to happen. Sorry. We should have the experimental U2Ed patch posted by the end of the week. Stand by....