EFHIII / balatro-calculator

A tool for calculating the score of a hand in Balatro
MIT License
65 stars 8 forks source link

Plasma Deck #52

Open anguigui opened 3 months ago

anguigui commented 3 months ago

name: Bug report about: Report any hands that are miscalculated or other bugs title: '' labels: bug assignees: ''


Description of the bug Plasma deck not working and breaking down properly at high values(?)

Steps To Reproduce Trying to calculate Meaty's legendary hand I noticed a discrepancy near the end of the calculation's breakdown leaking onto the actual result itself https://efhiii.github.io/balatro-calculator/?h=0AA2hgDAhBYwKd2O7EcIEQigACGHpAR227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtu23bbtt227bdtoAJyAQAcAAgAAAw

Expected behavior After observatory that goes 1,675 X 8.4521e133 It is expected for mult to half itself and be given to chips for a result of 4.2261e133 X 4.2261e133 --> this result should finally give 1.7859e265 (calculated by hand) Instead we get NaNeInf X 8.4521e133, NaNeInf could just be a visual bug which would be okay, but the mult is still not halved --> the final result then given is 7.1439e2665, which is clearly the calculation of 8.4521e133 squared Screenshots alt text

Additional context It is hard to be 100% certain there is a problem in the calculation, there might just be a problem in the breakdown itself, but it's a good bet to imagine something is up at that place too. The calculation itself is a nightmare though so things are hard to verify, I checked some of the code, which seemed right at surface level but I got lost at big adds and could not find sight of a NaNeInf in code itself, maybe I missed it or maybe that's part of the oversight for chips. Good luck and thank you for the help! I am not certain the screen worked so I will join a copy too externally. If there is a problem within this bug report feel free to contact me on discord, my @ is anguigui This is my first time submitting anything on a public git repo so sorry if I messed up something

image-1