My tests were too accurate, I did 100 * 100 throws, for a display of inaccurate testing, please see the end of the post where I did 10 * 100 throws
I really don't know what's happening here, not once did I find such flawed testings and people eating it up without understanding what's happening. It's like people have zero experience with a "game of chance".
Let me try to explain to you why the testings happening in this sub are completely meaningless, you guys can try it for yourself if you don't believe me.
Get a 6-sided dice
Sit down and throw it 6 times
Look at your results
Statistically the chance for a dice to roll a specific number is equal to every other side, meaning a 1 has the same chance of rolling as a 6 has. But this is mere statistics, it can help you create an estimate but it won't predict the outcome. You will easily realize this if you did what I wrote before as rolling a dice 6 times won't give you a 1, 2, 3, 4, 5 and 6, you will most likely end up with one of the numbers appearing twice, maybe thrice, you could even end up with rolling only 6 as this is not impossible, it's just that the chance for this to happen is very low.
Additionally, doing one run with your test sample also isn't enough, yet again due to RNG. What you should do is create your test scenario, set your test sample and then run this whole scenario multiple times, always resetting the statistics before each run and in the end evaluating the averages of all of your runs.
But because RNG is still involved, you will never get a 100% accurate result, it's just not possible but you can get closer to being accurate the more runs you do.
To explain this even more detailed, I did a simple dice test using a loop and a MySQL select that gives me a random number between 1 and 6 and waited 0.1~ seconds between each select (computer functions for random numbers aren't actually random, they can be predicted if you have insight on the function at it's lowest level, this applies to palworld too), one loop is made of 100 dice throws and I did 100 loops in total, totaling in 10.000 dice throws. The complete test log can be found on pastebin, here is the end outcome of the whole test:
More accurate testing see at the end of post
~~End of Tests, the total amount for each side rolled is: ~~> 1: 997 times
2: 1943 times
3: 2017 times
4: 2034 times
5: 1992 times
6: 1017 times
As you can see even tho each test has a test sample of 100 and I did 100 tests, I still end up with the 4 rolling twice as much as the 1, which can be credited towards RNG. What this means is that even tho you do 100 * 100 tests, RNG can still make you end up with an abnormality of >100%. I also did the same test runs before this test but forgot to note the total rolls, the individual test results are completely different but that doesn't matter because comparing one test to another is meaningless, what needs to be done is compare the average and totals.
That being said, if you want to test capture rates, 100 times throwing a ball isn't enough, if you want to test game mechanics, monitoring 1-4 pals over a timespan "once" isn't enough. There're actual studies about what your test sample needs to look like to even get a glimpse of an accurate result, but how those "tests" are currently done in this sub is completely wrong and not even in the slightest a reason to criticize any of the games mechanics. The most accurate way of telling if a game mechanic is working as presented is looking at the code but AFAIK the code is not available to us, maybe catch rates are flawed or maybe not, without proper testing or looking at the code you won't be able to tell.
I don't mind if someone wants to play around and do some number games but unless you know how to do proper tests, I'd stay away from making statements that something is broken.
For reference, I am a software developer myself and I constantly have to deal with customers claiming shit that just isn't the case, someone claiming they know better how our software works even tho I am the one writing it. And that's exactly what is happening right now in this sub, none of us can no for sure if something is flawed or not unless we get insight into the source code and since we can't we do Blackbox-Testing but this is only accurate if you do it over and over again, not just a few times and stop just because your initial thought is being supported by that test, that's not digging for the truth, that's digging to make yourself feel better.
I also was criticized for pointing out those flawed tests, people just want to help and contribute towards the community, completely understandable I do that myself among many games but giving false statements just doesn't help, if anything it damages the community. Good intentions don't fix faulty results, so please be careful with your statements unless you know for sure what you're doing.
Edit: I worked on the number generation (thanks /u/Blazenclaw) and instead of rounding after retrieving the result, I am now using a proper set of 6 numbers and select a random one among them.
The problem is 100 times running a test with testsample n=100 is quite accurate, but I've seen people use 1*100 times and think it's accurate.
The MySQL-Code for that is:
SELECT t1.die FROM (SELECT 1 AS die UNION ALL SELECT 2 AS die UNION ALL SELECT 3 AS die UNION ALL SELECT 4 AS die UNION ALL SELECT 5 AS die UNION ALL SELECT 6 AS die) AS t1 ORDER BY RAND() LIMIT 1
With the adjusted retrieval of the numbers, I did three tests and the results were (1, 2, 3):
Test 1:
End of Tests, the total amount for each side rolled is:
1: 1712 times
2: 1674 times
3: 1655 times
4: 1687 times
5: 1632 times
6: 1640 times
Test 2:
End of Tests, the total amount for each side rolled is:
1: 1680 times
2: 1713 times
3: 1689 times
4: 1699 times
5: 1639 times
6: 1580 times
Test 3:
End of Tests, the total amount for each side rolled is:
1: 1685 times
2: 1686 times
3: 1719 times
4: 1584 times
5: 1703 times
6: 1623 times
3 More tests without a wait between each throw (1, 2, 3):
Test 1:
End of Tests, the total amount for each side rolled is:
1: 1631 times
2: 1697 times
3: 1606 times
4: 1710 times
5: 1687 times
6: 1669 times
Test 2
End of Tests, the total amount for each side rolled is:
1: 1685 times
2: 1686 times
3: 1719 times
4: 1584 times
5: 1703 times
6: 1623 times
Test 3
End of Tests, the total amount for each side rolled is:
1: 1695 times
2: 1675 times
3: 1636 times
4: 1665 times
5: 1663 times
6: 1666 times
Since these test samples seem to be sufficient, here are 3 tests with only a 10*100 run: 1, 2, 3
And while 10*100 is still somewhat accurate, you can still see that numbers may vary quite much, e.g. on the first test we got 1 a total of 140 times, on the third try we got it 174 times. It's actual chance to appear is 16,6~% which would equal in a total of 166-167 times.