Quote:
Originally Posted by Huppy
I had the same problem and now the zone points are fixed, but I found a few
different entries of client_version_mask using a number 3 or 28.
I did notice that all of the other client_version_mask entries had a number
of 4294967295 (ending in 5, not 2), so I used that for the ones that needed
it. Not sure if this makes a diffrerence or should I change them all to end with
number 2 (as with your update entry above) ??
|
If you understand binary, the mask has a bit for each client, with the 6.2 Client being the least significant bit. In decimal, these correspond to:
1 Client 6.2
2 Titanium
4 SoF
8 SoD
16 Underfoot
32 HoT
64 and upwards are reserved for any future client versions.
So if a door/zone_point entry has a client_version_mask of 3 (1 + 2), it only applies to Client 6.2 or Titanium.
A mask of 28 is made up of 16 + 8 + 4 (i.e. Underfoot, SoD and SoF), so an entry with that mask applies to those clients.
4294967292 means any client from SoF onwards.
4294967295 means all clients, which is why most of the entries have this value, since most doors and zone_points are the same for all client versions.
So, to sum up, if a door or zone point is to apply to Titanium/6.2, use a mask of 3, for SoF and later, use a mask of 4294967292, for SoD and later, use a mask of 4294967288. For all clients, use 4294967295.
Where there are two zones for two sets of clients, there will be two entries for each door and zone_point, usually one with a mask of 3 for the old clients, and one with a mask of 4294967292 to apply to SoF onwards. Of course if any zones were revamped in SoD, then one set of entries would have a mask of 7 (6.2, Ttanium, SoF) and the other 4294967288.
Threaded Mode
