');
document.write('');
var yuipath = 'clientscript/yui';
var yuicombopath = '';
var remoteyui = false;
}
else // Load Rest of YUI remotely (where possible)
{
var yuipath = 'https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build';
var yuicombopath = '';
var remoteyui = true;
if (!yuicombopath)
{
document.write('');
}
}
var SESSIONURL = "";
var SECURITYTOKEN = "guest";
var IMGDIR_MISC = "warmane/misc";
var IMGDIR_BUTTON = "warmane/buttons";
var vb_disable_ajax = parseInt("0", 10);
var SIMPLEVERSION = "422";
var BBURL = "https://forum.warmane.com";
var LOGGEDIN = 0 > 0 ? true : false;
var THIS_SCRIPT = "showthread";
var RELPATH = "showthread.php?t=470545";
var PATHS = {
forum : "",
cms : "",
blog : ""
};
var AJAXBASEURL = "https://forum.warmane.com/";
var CoTTooltips = {
rename: true,
icons: false,
iconsize: 15,
qualitycolor: true,
overridecolor: {
spells: '#839309',
items: '',
npcs: '#fff',
objects: '#fff',
quests: '#ffb100',
achievements: '#fff'
}
};
// -->
WotLK Warmane 3.3.5 12340 client checksums are not original
Member
Warmane 3.3.5 12340 client checksums are not original
I noticed that when I hashed/made a checksum for the Warmane wotlk client that its checksums are different from the original client.
CRC32: 60CE0C11
MD5: 5758d89ed392e2190c44c5183a6d23a3
SHA1: f397a538e6d7ecd362768303feb2d43d90227c31
Here are original: https://github.com/anzz1/wow-client-checksums
CRC32: b8d98b75
MD5: 45892bdedd0ad70aed4ccd22d9fb5984
SHA1:178f78380affd260cb775d44397ba6b33ac05fdb
I checked another popular wotlk client server and they had the original checksums.
Does anyone know why Warmane's are different from the original? It is not something like Large Address Aware since if you apply LAA to the original you end up with these checksums:
CRC32: 467CEBA8
MD5: 7c29dcc0f7909d840c41e1f7145ce50b
SHA1: 8141706c6935fc10c03e25c2e1562957ea9d8998
Posting Permissions
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
Forum Rules