Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guaranteed Min 999. Potential Max 0. #74

Closed
broncoempire opened this issue Apr 13, 2020 · 10 comments · Fixed by #106
Closed

Guaranteed Min 999. Potential Max 0. #74

broncoempire opened this issue Apr 13, 2020 · 10 comments · Fixed by #106
Labels
prediction Prediction / Calculation Issues

Comments

@broncoempire
Copy link

Hi.

When entering the following values, I am getting my results as guaranteed Min 999 and potential Max as 0.

First time: No
Pattern: Decreasing
Buy Price: 101
Monday: 89AM - 77PM

When clearing the Buy Price it readjusts to Guaranteed min 89 and Potential max 139.

Any ideas why it’s not calculating correctly when I enter my buy price?

@ZZZZzzzzac
Copy link

a common rounding issue, i think it's the same problem like #47 #40, and i personally also had similiar experience, the boundary calculation may have 1 error

@broncoempire
Copy link
Author

a common rounding issue, i think it's the same problem like #47 #40, and i personally also had similiar experience, the boundary calculation may have 1 error

Thank you for pointing me to these other related issues :-D

@ZZZZzzzzac ZZZZzzzzac mentioned this issue Apr 14, 2020
@mikebryant mikebryant added the prediction Prediction / Calculation Issues label Apr 14, 2020
@mikebryant
Copy link
Owner

The numbers you've put in aren't possible with the code retrieved from the game.

@broncoempire Are you confident this isn't the first week you've bought from daisy on your own island, and that the buy price is for your own island?
What are your prices for Tuesday AM/PM?

@broncoempire
Copy link
Author

broncoempire commented Apr 14, 2020

The numbers you've put in aren't possible with the code retrieved from the game.

@broncoempire Are you confident this isn't the first week you've bought from daisy on your own island, and that the buy price is for your own island?

What are your prices for Tuesday AM/PM?

Thanks for the feedback @mikebryant.
I have been keeping track of these in a spreadsheet for over a week now.

Also, I’ve purchased turnips multiple times on my island. Maybe 2 or 3 Sunday’s since launch.

Tuesday’s prices are:
72 AM
68 PM

Thank you

@tsaiDavid
Copy link

@mikebryant - what if you purchased turnips on a friend's island but you've been keeping track of prices in your own? I'm getting this same behavior

@theRTC204
Copy link
Collaborator

theRTC204 commented Apr 14, 2020

Where you buy from makes no difference as long every value you enter into this tool is from your island only. Please share your values so that we can compare them against the extracted algorithm.

@peachiepie
Copy link

I am also having this issue. I purchased turnips on my own island for 101. this is my second time buying, but I'm not sure what my pattern was last week. Prices were 128 Monday AM, unknown Monday PM, 88 today AM, and 124 today PM.

@dotkupo
Copy link

dotkupo commented Apr 15, 2020

Hi, i'm also having this issue too. I am not a first time buyer, and the site was working fine for me until this morning at which point it refuses to accept my Monday PM price.
Prices are as follows.

Edit: I should edit in the following extra details.

First-Time Buyer: No

Previous Pattern: I don't know

Sunday - 95

Monday
AM - 85
PM- 79

Tuesday
AM - 76
PM - 71

Wednesday
AM - 68
PM - 64

As mentioned at the top of the post, the site accepted the Monday PM price until this morning.
I even have a picture of the Monday PM price being accepted if that helps.
stalnks

However now when I put 79 into the PM price, I get the all patterns 999 min potential max 0 issue.
image

This does work if I put 80 into the list instead of 79.
image

But well, 80 isn't what I got. I got 79.

@mikebryant
Copy link
Owner

@dotkupo Thanks for the details. I'll try and figure out why your numbers aren't matching the reverse-engineered code

@mikebryant
Copy link
Owner

mikebryant commented Apr 15, 2020

The problem here is, the change in rate between 85 and 79 is too large.
The minimum the internal rate value could be for 85 is 0.8842106316 - then 0.8842106316*95 == 84.000010002 - intceil gives 85

Maximum possible rate for 79 is 0.8315790526, *95 == 79.000009997 - which in theory through intceil is still 79. The difference between those two rates is 0.05263157895 - but all of the patterns in Treeki's code decrease by at most 0.05 in the rate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prediction Prediction / Calculation Issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants