Frozen w/ client 6.0.1.10 and 6.0.2.0 inserting to backpack

JarelBlythe · Post by **JarelBlythe** » Mon Sep 03, 2007 9:47 am

Hi all,

Hopefully someone can help me with this. I just pulled down the latest POL 97 and was trying to use it with client 6.0.1.10 and 6.0.2.0. Anytime that I try to put something into the backpack it locks up the client.

I have tried this with the Full Distro for 97 and with the core (moving over some of my old files from 95).

Any ideas on this one?

Thanks,
Jarel

JarelBlythe · Post by **JarelBlythe** » Mon Sep 03, 2007 10:03 am

Also note that this occurs whether the item is put into the backpack on the client side or programmatically on the server side.

Jarel

Pierce · Post by **Pierce** » Mon Sep 03, 2007 12:21 pm

Since 6.0.1.7 there are some packet changes which are not supported by the pol core. You have to use a version lower than 6.0.1.7. atm.

JarelBlythe · Post by **JarelBlythe** » Tue Sep 04, 2007 6:54 pm

Hi Pierce,

Yep, that was it...I went back to the base Mondains Legacy install and it works perfect. Thanks for the quick response.

Do you (or anyone else) know of a location to get later versions pre-6.0.1.7, but later than 4.0.11c (Mondains Legacy)?

Regards,
Jarel

OldnGrey · Post by **OldnGrey** » Tue Sep 04, 2007 7:09 pm

Just patch with OSI. Watch it closely and cancel when it starts to download 6.0.1.7. At that point you will have a partial download in the patch directory but a fully working client at 6.0.1.6. Just don't run uo.exe again

phao · Post by **phao** » Thu Sep 06, 2007 9:13 am

well, once a guy told to me that you can patch to OSI but in the middle of the patch (when you are downloading 6.0.1.7) stop it and backup the 6.0.1.6 client, so restart the patch, it'll resume and patch to OSI, then make a backup (just for precaution of the most actualized client) and them copy the 6.0.1.6 client to the UO folder, replace it and game.

well if what i told is confused to understand, the 'base' is: patch to osi, but make a backup of the client supported by your emulator (6.0.1.6 in this case).

He says that since the packets that aren't supported by the emmulators are sent by the client, dont' matter if other filles are patched (unless some big thing is ADDED or REMOVED in UO by the patch), but the client.

i've (i think) experienced one od this changes in path, i've patched to some client i don't remember what, and occlo (haven i think) was totally different from it was, and probabilly other areas were changed too, this isn't a problem is EVERY player in the server uses the same client, but if dont, it can be a problem.

it's by you, i think if you patch to 5.0.6 (i use 5.0.9.1, oldngray recomended to me) it's enough because you can see the VERY BEAULTIFUL NEW ARMORS

which include anims, gumps, tiles, THEY ARE GREAT hahaha.

OldnGrey · Post by **OldnGrey** » Thu Sep 06, 2007 5:22 pm

Dealing with OSI patching is a bit of a headache. We decided we need to deal with players who have base ML but could have patched to anything up to the latest. So that means everything from 4.0.11 to 6.0.1.10 and later.

Retaining and playing 5.0.9.1 client.exe isn't enough I'm afraid. In our experience we've noticed that we have to distribute several other files as well. But with our logon patcher at least we can replace files if we have to.

From what I have seen though, CUO doesn't allow you to distribute the client.exe (at least that's what appears to happen) so it's quite a nasty minefield.

I am still wondering about the best way to ensure our players have the right files but remain compatible with ConnectUO. Sorry, off topic.