|
|
|
|
|
|
|
|
|
 Posted: Thu Apr 24, 2014 11:34 pm
This thread isn't a guide. It's just somewhat a disorganized tracking thread of my future research.
Yes opening caches and getting an approximate amount of percentages of variety caches has been done but more could be explored.
Working Hypothesis:
The caches you open follow a pattern. They are not random but have factors that also put into play with opening them. For example, if opening a philosopher's cache and getting a ruby cache, how much is your chance in getting an emerald cache next or vice versa?
Also, I have noticed an up, down and same pattern. If I open the most common cache to be dropped, there's a big chance that I will open a less common cache next ( down ), If I open a topaz cache, there's a good chance that the next cache I'll open will be a cache more common than topaz ( up ). If I open an emerald cache and have opened the same cache ( same ).
Another working hypothesis identifying odds and evens from base caches to caches you open. Example is, if my base cache has an odd number of 77, what caches are common to appear if you got a base cache that is an odd number. I noticed that some variety of caches appear more frequently when opening an even number of base.
I have to keep repeating the opening and tallying ten times to make sure luck is out of the way.
Because opening caches with a fixed base amount and counting how many of each variety isn't enough. There has to be a reason why some are lucky to open more gold caches and some less. It would be better if one had the ability to predict the next cache.
Ok, tackling them one at a time now.
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:03 am
Interesting theory.
However, I don't think the previous cache has anything to do with the result from the next cache.
To show you what I mean, open your inventory and click a base cache. Right-click and copy the link adress of the 'open' button. Paste it somewhere were you can read it and reload your inventory (without opening the cache).
Again, click the same cache and copy the link. Paste it below the previous one and it's easy to see the numbers have changed.
These numbers are generated randomly (or as randomly as a computer can do that) and used as an initializaton vector (or seed) for another random-number algorithm deciding the colored cache.
This means the colored cache depends on when you open it (or rather when you last reloaded your inventory) and not what you opened before.
However, figuring out the algorithm used by the server for selecting the colored cache could let you select the color of your choice simply by reloading your inventory until a desireable number appeared.
But as always, feel free to prove me wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:08 am
Sharacia Interesting theory. However, I don't think the previous cache has anything to do with the result from the next cache. To show you what I mean, open your inventory and click a base cache. Right-click and copy the link adress of the 'open' button. Paste it somewhere were you can read it and reload your inventory (without opening the cache). Again, click the same cache and copy the link. Paste it below the previous one and it's easy to see the numbers have changed. These numbers are generated randomly (or as randomly as a computer can do that) and used as an initializaton vector (or seed) for another random-number algorithm deciding the colored cache. This means the colored cache depends on when you open it (or rather when you last reloaded your inventory) and not what you opened before. However, figuring out the algorithm used by the server for selecting the colored cache could let you select the color of your choice simply by reloading your inventory until a desireable number appeared. But as always, feel free to prove me wrong. I do believe what you say. If I could figure out the numbers that the server usually leans on even randomly generated, I could increase some chances of getting what I want :> Thanks for the insight!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:15 am
236519227.1398417014.1179172246
A sample of a gold cache number link....
It's like looking at them on another language. I will try to decipher them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:21 am
Sphyxia I do believe what you say. If I could figure out the numbers that the server usually leans on even randomly generated, I could increase some chances of getting what I want :> Thanks for the insight! No problem. Just had another thought as well... If you were to be able to find out how the resulting cache is calculated, the same thing could probably be done for other rigs as well. Say, Alchemist's Case, Enchanted Golden Trunk, etc. Might be worth thinking about.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:25 am
Sharacia Sphyxia I do believe what you say. If I could figure out the numbers that the server usually leans on even randomly generated, I could increase some chances of getting what I want :> Thanks for the insight! No problem. Just had another thought as well... If you were to be able to find out how the resulting cache is calculated, the same thing could probably be done for other rigs as well. Say, Alchemist's Case, Enchanted Golden Trunk, etc. Might be worth thinking about. Definitely worth thinking but hard doing, cases? woooot much gold needed ._. For every hypothesis above I think I need 10k caches with 1k per trial. That's a lot of clicking.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:33 am
Sphyxia Sharacia Sphyxia I do believe what you say. If I could figure out the numbers that the server usually leans on even randomly generated, I could increase some chances of getting what I want :> Thanks for the insight! No problem. Just had another thought as well... If you were to be able to find out how the resulting cache is calculated, the same thing could probably be done for other rigs as well. Say, Alchemist's Case, Enchanted Golden Trunk, etc. Might be worth thinking about. Definitely worth thinking but hard doing, cases? woooot much gold needed ._. For every hypothesis above I think I need 10k caches with 1k per trial. That's a lot of clicking. Actually, what I meant was, cracking the algorithm for caches should make it possible to figure out the one for cases as it's probably the same algorithm. Just with different numbers for probabilities. It should be fairly few cases needed as all you need is the maximum value for deciding the prize (given that the most desireable prize is at the end of the scale).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 2:55 am
Sharacia Sphyxia Sharacia Sphyxia I do believe what you say. If I could figure out the numbers that the server usually leans on even randomly generated, I could increase some chances of getting what I want :> Thanks for the insight! No problem. Just had another thought as well... If you were to be able to find out how the resulting cache is calculated, the same thing could probably be done for other rigs as well. Say, Alchemist's Case, Enchanted Golden Trunk, etc. Might be worth thinking about. Definitely worth thinking but hard doing, cases? woooot much gold needed ._. For every hypothesis above I think I need 10k caches with 1k per trial. That's a lot of clicking. Actually, what I meant was, cracking the algorithm for caches should make it possible to figure out the one for cases as it's probably the same algorithm. Just with different numbers for probabilities. It should be fairly few cases needed as all you need is the maximum value for deciding the prize (given that the most desireable prize is at the end of the scale). made a dry counting and some numbers fit some profile like if I get a 13-17 beginning number its aqua or emerald, or ruby and topaz. then again I'm only looking at beginning numbers and not ends. anyhow, I'll be doing the listing on next 1k caches
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 3:01 am
1609423619.1398419872.1961443195
the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened.
that's plenty of progress so far XD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 6:43 am
Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 9:07 am
Sharacia Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches. The question now is, what are the numbers on the right and left farthest side mean?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 9:36 am
Sphyxia Sharacia Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches. The question now is, what are the numbers on the right and left farthest side mean? Those are most likely salts used by the random number function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 9:38 am
Sharacia Sphyxia Sharacia Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches. The question now is, what are the numbers on the right and left farthest side mean? Those are most likely salts used by the random number function. Salts? sorry, I studied nursing and shifting into medicine so you lost me there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 10:14 am
Sphyxia Sharacia Sphyxia Sharacia Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches. The question now is, what are the numbers on the right and left farthest side mean? Those are most likely salts used by the random number function. Salts? sorry, I studied nursing and shifting into medicine so you lost me there. A salt is a (usually) large random number (or string of text) meant to pad the input to a mathematic or cryptographic function. It is only there to make it more difficult for an outside user to, for example, discover an encrypted password or take advantage of a feature requiring a random number as input. In this case the salt(s) are used to pad each side of the sequential number then using the result to initialize the random number generator. Which then generates the colored cache. (In theory anyway, as it seems the most logical way of executing this task.) Hope I didn't make things more difficult there...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Apr 25, 2014 10:18 am
Sharacia Sphyxia Sharacia Sphyxia Sharacia Sphyxia 1609423619. 1398419872.1961443195 the underlined numbers are the number of caches so far attempted to be opened. It always increases as a constant which means its value is close to the number of all caches recorded by the server to have been opened and attempted to be opened. that's plenty of progress so far XD Yes, that seems very likely. It would have to use a sequential number to ensure randomness. And that's a lot of caches... Also, approximately 69.920.994 of those will have been Gold Caches. The question now is, what are the numbers on the right and left farthest side mean? Those are most likely salts used by the random number function. Salts? sorry, I studied nursing and shifting into medicine so you lost me there. A salt is a (usually) large random number (or string of text) meant to pad the input to a mathematic or cryptographic function. It is only there to make it more difficult for an outside user to, for example, discover an encrypted password or take advantage of a feature requiring a random number as input. In this case the salt(s) are used to pad each side of the sequential number then using the result to initialize the random number generator. Which then generates the colored cache. (In theory anyway, as it seems the most logical way of executing this task.) Hope I didn't make things more difficult there... I understood that there's more work to be done now ._. thanks for the explanation :>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reply
