Before I get into that, if you want to try 4.1.1, here are the steps involved, regardless of whether you're the client or the server:
1. Download the file UrbanTerror411_update.zip.
2. The ZIP archive you just downloaded contains 2 files inside it:
- ut4_commune.pk3, which is just a plain old 3rd party map just like any other (you can use it in either 4.1 or in 4.1.1)
- zpak001_assets.pk3
3. Place zpak001_assets.pk3 into the same directory where your zpak000_assets.pk3 resides.
Now here are the problems.
First, note that there are many permutations of possiblilities. I see that there are 4 variables in determining the outcome:
1. Which client version you have (plain vanilla, mitsubishi client, or ioquake3 vanilla [rare])
2. Which server version you have. The choices here are plain vanilla unpatched server binary, Rambetter's ioUrT-server-4.1 branch (behavior will be identical to plain vanilla unpatched binary), Rambetter's ioquake3-UrT-server-4.1 branch, and variations thereof (using different patches).
3. Whether or not client has the 4.1.1 zpak.
4. Whether or not server has the 4.1.1 zpak.
Now from my experiments using different permutations, it seems that in almost all cases (in all of the common cases), a client that is running the 4.1.1 zpak _will_ be able to connect to a server running just 4.1 with no problems.
So upgrading your client to 4.1.1 will not hurt your ability to connect to old 4.1 servers.
Now, one of the mistakes that Frozen Sand made is that they named a heavily modified map with the same name. For example, they've included ut4_tombs in 4.1.1, which is drastically different from the original 4.1 ut4_tombs (and they have the same BSP name).
With Tombs map, if you're a 4.1.1 client connecting to a 4.1 server, you will have no problem. The client will load the old version of the map and all will be well.
However, if you're a 4.1 client connecting to a 4.1.1 server, really bad things will happen (I say "bad" because the behavior is very unexpected with no clear error message). you will actually be able to connect, but when you enter in-game, you won't be able to walk normally. There will appear to be invisible walls blocking you and you won't be able to walk down a simple hallway. This is because the server has the new Tombs loaded, but your client shows you the old Tombs. Frozen Sand should have named the revised maps to different names so that errors when connecting would be more predictable.
I think a better move altogether would have been to release these new maps as independent PK3 files.
Anyhow, the News on the UrT website states:
"WARNING: This update will break compatibility with most 4.1 servers. Request the admins to update their servers."
This is misleading. Like I said, it seems that updating your client to 4.1.1 will not put you in any danger of not being able to connect to an old 4.1 server.
Now I actually went ahead and created a 4.1.1 server. I have all the revised maps on this server's mapcycle:
ut4_casa
ut4_company
ut4_docks
ut4_harbortown
ut4_herring
ut4_horror
ut4_ramelle
ut4_ricochet
ut4_subway
ut4_swim
ut4_thingley
ut4_tombs
ut4_uptown
(If you want to test, it's /connect porky.clanwtf.net:27966 .)
What's happening on this server is as follows. The map is Tombs. Clients are connecting, and they are trying to walk into walls. They don't know what is going on, and assume that the server is totally busted. They leave. I don't expect this server to retain its popularity for very long (it was top 40 for past month).
I've just described some of the problems with 4.1.1, there are actaully a few others too.
This post has been edited by Rambetter: 20 January 2011 - 10:07 PM