Improvement suggestion for the CustomCosmetics about beacon HOT 2 OPEN

At the moment, the best I could do is allow setting DoCustomCosmeticValidation and CosmeticWhitelistOverride from within Beacon, but there's no way it could compute the values or host the url at this time. Not until we know exactly what PrintCosmeticCRC is doing so its behavior could be replicated. I'm assuming it's a CRC32 checksum, but I haven't yet figured out which file it's computing against. I've tried a handful of possibilities, but none seem to match.

from beacon.

" I've tried a handful of possibilities, but none seem to match."
Then I'm not the only one trying to figure it out ;).

I didn't realise until just now that CRC32 can also be represented as DEC instead of HEX. I found a calculator for it - I already took all values from the library.json - no match :(. The funny thing is: the JSON already contains hashes: sha1, md5 (both hex) and a filefingerprint (dec). Why this fourth hash?!

The funny thing is: since I don't have the PowerRanger skin (never!), I can't respond to player requests to activate the skin..... :(

I can't imagine that they did something complicated here - why? It's all about everyone having the same version - server support for version 1.0 - on the client is 0.9 -> update (if allowed)

from beacon.