If i ever download a Umod i always just use Umod Browser to get all the files since half the time someone f**ks up with the Umod and the files aren't setup right, or the Umod thingy doesn't work at all, plus with Umods unlike zip files, you can't overwrite prevoious files (unless you uninstall but who wants to do that).

I do like the UMod's way of adding the mods to setup.exe, so you can manage a list of mods and mutators. I know one can create those entries manually by editing files like Manifest.ini, but it's still a comfy way of managing mods.

If its the same files then why VERSION mismatches unless the Bcore from JW is totally diffrent then the one in BW 1.72.

I think it's a bad idea to get rid of the UMods, they are convenient for people that are unsure about manual installation.

I think DC should seperate JW totally from BW, create a JCore for example.

AAAaaarrrghhh!!! (Resisting temptation to run away screaming) Ok, first, UMODs seem to have some serious beef for some people. Thats why we have ZIP and UMOD. UMODS are easy to install (when they work) and we have had no experience of our umods damaging any UT install. I don't know what a poorly built umod might do to someone's UT. If you are unlucky, the zip is here. It is more reliable, but doesn;t add those server packages or do the other mod registering stuff. (which ain't too serious IMO)

BCore vs JCore, no I don't think thats nessecarry, they would be identical! There will always be JW version available that works with the latest BW. If you ever have a problem with JW-BW compatability install the latest BALLISTIC WEAPONS version.
We may actually try rethinking things a bit and/or changing our install methods to prevent BCore being replaced with older versions when installing an old JW or BW.
These friggin mismatches sound like hell! If the server has the latest release, the clients should have it too and all would (theoretically) work! perhaps its the old stuff in the cache or maybe people don't have the latest ver. Maybe some thing installed an older one or they did to join older servers. Perhaps you have a better idea of what it is.
At any rate, we're gonna try hammer this one as soon as we can. We want it fixed (or at least improved) for the next release. Right now we're thinking that giving each version unique package names will help, but we'll have to investigate it thoroughly...

Hang on, you say anyone who installs UMOD get mismatch? And the ZIP works???

That is exactly the problem, the server may have updated files, but because the clients have the same files as the server, it won't attempt to upload the updated version to the clients because it thinks the clients are up to date.
Adding version numbers would get rid of this issue altogether.

A simple change like BCore_172.u, or BCore_20 for the next release, would do the trick nicely.

And if JCore and BCore would be the exact same, then let's drop that idea.

How can you possibly screw up the system with the ZIPs? They don't replace any important files, only BW ones...