Jagex will add things to the client pre-release. Even though 289 does not have Slayer, you can find "slayer" in the skills array, similar to what you observed for 317 with Farming.
https://github.com/s1mple-dev/289-cl...stants.java#L8
This is a link to the 289 client found on my Github.
Graham also made a comment about this a couple days ago
As for the "update", the earliest I can find the cache was created is January 23, 2005 which puts it around here
I decided to do more digging.......
One of the last npcs found in the cache is the
Steel dragon. Which was released January 17, 2005 with the Karamja dungeon.
The last item found in the cache is the
Dragon platelegs. Which was released January 17, 2005 with the Karamja dungeon.
One of the last objects found in the cache is the
Dungeon entrance (Brimhaven Dungeon). Which was released January 17, 2005 with the Karamja dungeon.
We can 100% say this cache is atleast from the
Update:Karamja Dungeon RuneScape update from January 17, 2005.
Now it gets weird...
-According to
Old Clients and
Index of /resources/, the 289 client inside these archives are dated February 28, 2005.
-Both of these archives do not have a client dating to January 17-23, 2005
To confirm something with Slayer, I decided to decompile the 282 client from December 2004 and see what I find.
As you can see, even the December 2004 client has a reference to Slayer even though it won't be released for almost another two months.
I then decided to decompile the 294 client from one of the archives and check the same skills array
If you look closely at this specific array from both the 282 and 294 client, you will see that the 18th index from 282 is set
false and in 294 it is set to
true.
Code:
public static boolean c[] = {
true, true, true, true, true, true, true, true, true, true,
true, true, true, true, true, true, true, true, true, false,
true, false, false, false, false
};
The 18th index of the array is for the "slayer" index from the above array. 282 is false because it is from before the Slayer release. And obviously 294 is set true for Slayer because it was released. If you go back to the first link I provided in this post, you will see that 289 has this set to
false.
Conclusion
-This client is 100% 289. And this is already known just by the client build number which can be found during login etc.
-This cache 100% dates between January 17, 2005 to January 23, 2005.
-This cache is 100% 289-293. Critical thinking speaking, there is no true way right now to prove this is 289. Whether the cache is 289 or not really comes down to knowing if 290-293 client has "slayer" set to true/false in that skills array. We could also check a 290-293 cache for any Slayer npcs/items. Unfortunately, I can not find any of those clients/caches. However, if Jagex incremented the client build at each update they did, we could safely determine that this cache is 100% 289.
Thoughts
-The maps found inside this 289 cache is 100% from another revision. This is the only explanation I can come up with about the map objects that exceed the real amount of objects inside the cache config. (Ex. Object with ID: 7000 found inside part of a region of the map, when the 289 cache only supports up to ~5000.) There is no way Jagex introduced ~2000 new objects in such small time frame.
If you didn't know, I did a cache fix to the one on my Github. I removed/replaced all of the map objects not supported by the 289 cache. This was the best way I could think of to avoid any issues when it came to using the maps which I believe did come from another revision much higher than 289.
Thanks!