First off: Currently you do NOT need the update if you have installed AOS. Previous UO_RICE version 2.2b runs fine with AOS. The patch engine didn't need an update, so it's just cosmetical. (not complaining anymore about unknown installation)

First off: Currently you do NOT need the update if you have installed LBR.
Previous UO_RICE version 2.2 runs fine with LBR.
From a users' point of view the update is just cosmetically, showing which UO version (LBR or NON LBR) is installed. The patch engine didn't need an update.

So why did I bother making it at all ?

UO:LBR beared two surprises for me:

I. LBR and NON LBR clients are IDENTICAL
II.There can be only one: LBR or NON LBR installation.

Ad I.: That's the reason why there's currently no real need to update.
But one never knows what OSI does, if clients start to differ, UO_RICE is prepared.
This update is mostly internal restructuring to deal with LBR differences more easily if they arrive in future.

Ad II.:
I don't understand why OSI doesn't allow it.
I don't like it, added instructions (in zip file) how to workaround this limitation and how to use UO_RICE in this scenario.
Anyway, I admit usually it doesn't make sense to have LBR and NON LBR simultaneously.
Unless you create OSI client tools ;)

Conclusion: If you already have UO_RICE 2.2 you don't need 2.2b

Firstoff: UO_RICE 2.2 has already survived 11 pachtes / 0.25 years without breaking :)

Secondly: Will UO_RICE support UO:LBR ?

Definitly, but before I can do this I need the damned CD. OSI announced that LBR "streethitday" will be delayed a few weeks for Europe.

Furthermore it will be probably lots of work.

In short: yes, but PATIENCE !!!

Might be - in worst case - a month or more or so till I can add LBR support.