OldUnreal (Engine)

I don't know for sure if this has been stated before but:
After I did some research into the incompatibility issues, it seams like it only comes from UnrealI/UnrealShare packages.
So what this comes down to, if you put in 225f UnrealI/UnrealShare packages on 227f/227g system folder the server is compatible with 226f clients (and 227 client is compatible with 226f servers).
BUT there's one drawback; by doing so, you lose some 227 features that's in UnrealShare/UnrealI packages (including projectile Decals and some maps or mods made for 227)... and you can't use UnrealGold style menu no more (UMenu.UnrealConsole).

But this is fine for those who still host 225f server simply because they want compatibility with all versions. To do that follow these steps:

- First off; make backup of 227 UnrealShare.u / UnrealI.u / UBrowser.u / UWindow.u (in case something goes wrong).
- Copy over 225f version of those respective files to 227 System folder.
- Edit Unreal.ini and remove following lines:

ServerActors=UWebAdmin.WebAdminManager
ServerPackages=UnrealIntegrity227

And you should be ready to go with hosting 227 server for all client versions.

PS: Do this at your own risk + we do NOT support this in any way!

I want to add here what I already said in another topic about compatibility:

Now, the only thing still bothering me is, that people (and I don't mean now someone specifically, because its a somewhat common problem) still believe 227 would break backwards compatibility.
Indeed exactly the opposite is the cause- it suffers from it, as you can see, badly.

To understand why this problem exists a small explanation:
Any new version has to be made compatible with the previous version to make it compatible. Thats what Epic did from any version to the next. The procedure to do so is called conforming. It is necessary to align the nametable, so that any entry is on the "same place" as it was in the previous version.
If you have a new version now, which adds new things (like 226 did too), they are placed at the end, after the entries which match with the previous version. Forgive me that this is now maybe not 100% technical correct, but you get the point.

What happened is easy. Legend and Epic forked that with 226b(UGold) and 226f. My med fried brain refuses to tell now exactly which version was first, I think it was 226f. But that doesn't even matter, its just about who to blame if you still wish to blame someone.
They both conformed their version of 226 against 225, thus the new 226 specific entries are out of sync and causing the known problems, like 226b servers crashing 226f clients etc.
It would have been easy to avoid, if they just would have conformed it against the previously existing 226 version.
However, they followed the same "We don't care policy" with Anthology, which needs to be patched again to make it netcompatible at all. The only comment from people about that is: "where is the patch" instead of complains why it is that way.
Why people behave so different with 227 is a miracle to me. For Anthology they broke it just to add some crappy advertising Logo.

Anyways, back to topic. Due to the given situation we can conform 227 only to one version- to 226b or 226f.
The decision to take 226b for conforming was a pure logical one. 226b has compared to 226f a lot of less bugs AND it is nowadays more often in use than classical Unreal.
As first hour Unreal player I'd have chosen 226f, but this would have been a pure emotional decision then and my logic refused me to do so.
So 227 servers are compatible with: 224,225,226b.

Why people are so afraid to leave buggy 226f and don't go to 227- I don't know. But even if they don't want to, they still can go back to 224/225, an option which an UGold player doesn't have. Another reason why 226b and not 226f. While I have to add that I always disliked 226f. 224 was the best client in my eyes before 227, compared to 226f it was still better as server and 225 was the best server.

The method above can cause problems and if problems appear we are not able to fix them in any case. It reverts some fixes and additions.
If it affects the server in any way (stability, compatibility) there is nothing we can do.
Take it as some kind of hack with no guarantee whatsoever.