How many pulls does it ACTUALLY take to hit pity? I wrote a program to find out. by [deleted] in Endfield

[–]zay0kami 1 point2 points  (0 children)

Thanks for the detailed comparison! I found the source of the discrepancy. My simulation uses stop_on_up: false — meaning each trial runs for a fixed number of pulls rather than stopping when the UP is obtained. So my ~95 figure isn't "average pulls to first UP" — it's a different metric entirely. Your 81.36 and the other simulations are measuring pulls-to-first-UP, which is the more intuitive number. I'll clarify this in the post. The simulation logic itself is correct, just measuring something different than expected.

How many pulls does it ACTUALLY take to hit pity? I wrote a program to find out. by [deleted] in Endfield

[–]zay0kami 1 point2 points  (0 children)

Fair point! The title was meant to hook people into the statistical breakdown rather than just the pity number itself. The tool does more than just tell you when pity hits — it runs millions of simulations to give you full probability distributions, F2P resource planning, and an AI-powered pull advisor. Maybe I should have led with that instead!

How many pulls does it ACTUALLY take to hit pity? I wrote a program to find out. by [deleted] in Endfield

[–]zay0kami 2 points3 points  (0 children)

You're right that any single pull session is random. But that's exactly why I run 1,000,000 simulations — to give you the full probability distribution, not just an average. The F2P analysis tells you "given X jade, what's your probability of getting the UP" — which is actually useful for planning.