Benefits of 227 - official vs unofficial

[[]KAOS[]Casey]

It's not that simple..

[[§Ŕ] ŤhěxĐâŕkśîđěŕ]

A simple 226 fix might work really.

227 = 226 fix + 225 fix + 224 fix, etc., you do the math...

[Bane]

Hmm. If 226f came after 226b, doesn't that mean it would be impossible to conform 226f to 226b? Wouldn't that require 226f, which does not contain RTNP, to have the entire nametable and whatever else of 226b, including all of the RTNP stuff?

As casey already said, if it would have been conformed in the correct order, one version after another there would be no compatibility issue.
But both 226f and 226b were conformed against 225 and not against the previous 226 version (and I honestly don't care which version came first).

Of course updating one of the 226 versions and then conforming 227 against that would fix all compatibility issues, but then again, why would people update 226 and not if they are already updating anyway, to 227?

If the reason not to use is they don't trust Oldunreal, they wouldn't trust such an update too. If the reason is they don't like the 227 features, they don't need to use them. If the reason is the gameplay- the gameplay wasn't changed.

Even if it is possible, it's not worth the work because the true problem is, that a 226f and 226b client can't be distinguished before real login and the login won't happen because it's crashed before. To catch that is maybe even completely impossible without changing at least one of the 226 versions.

Let me rephrase.

Correct me if I'm wrong, but it is impossible to conform 226f to 226b because of the additional content in 226b. Thus when 226f was made they had no choice but to conform it against 225, creating the incompatibility.

[[§Ŕ] ŤhěxĐâŕkśîđěŕ]

UHHH why didn't you totally break the compatibility against 226f because it *cough*sucks*cough* anyway...

[[]KAOS[]Casey]

it already is totally broken for netplay, and it's going to stay that way, there's no way to fix it, period.

[Smirftsch]

Let me rephrase.

Correct me if I'm wrong, but it is impossible to conform 226f to 226b because of the additional content in 226b. Thus when 226f was made they had no choice but to conform it against 225, creating the incompatibility.

Almost
It would be possible to re-conform 226f to 226b (although it would make more sense to conform the package containing the additional information against the package with less information of course, so you are right in some way), but this would require a new update for 226 containing all .u files, so at least huge download, but an update nevertheless.
They COULD have done it and they SHOULD have done it to conform 226f to 226b, but they didn't. Why? Don't ask me, maybe legal issues because 226b was created by legend. But that's only a guess. Maybe they didn't care or maybe just nobody thought about it.

[Buster]

Yes, it was because of Legend being involved. If Gold 226b wasn't compatible than the thinking was it will get people to buy Gold even though they may have regular Unreal etc.

It's all about sales $$. Otherwise Epic would have lost their distributer !!