You create 2 objects, a maker and a solver. The maker has the following tasks: Generate a number 1..50000, Check the number given by the solver and give feedback accordingly
type Makes=class function CheckNumber(N:integer):FeedbackType; End;
Then the solver could just make a call to that function
oops, makes should be maker
Anyhow, if the solver calls that function he gets feedback, using that feedback you can determine if you should try a higher or lower number. I seriously dont see how this is so hard to understand
Fair enough, point taken. The way I saw it is that you know what the percentages were but the solver could not use those values.
Lets say if you get in a 15% range you will get the message "Really warm" and a range of 5% "really hot" the solver cant move on based on the knowledge that he is only 5% or 15% off
Then the author needs to say that. As it stands, nobody else seems to understand. I thought you had to write only a solver. You thought you didn't. Two others are also unsure.
None of us want to suggest an edit because the challenge has other problems that aren't necessarily close reasons. You are welcome to suggest them.
Teun Pronk, the reason I went to Meta about your question was because the concept was worth saving (And because I had a decent answer.) The concept of the other question I mentioned in my meta post was also good (though the OP was looking for something that was just too trivial.) Both those questions were better than this latest one.
This question has no API defined, the game can be optimised by a very trivial algorithm, the bonuses are all over the place, and (worst of all) the OP just doesn't want to listen.
So thank you for your question, which I went to some effort to save, but the same arguments don't apply to this one.