New curve

[r2dev2]

Sets curve to min(max(428 * (0.995) ** solves + 75, 428 * (0.9978) ** solves, 100), 500)

This has values of (last argument to getScore is number of solves):

> getScore(100, 500, 800, 1)
500
> getScore(100, 500, 800, 5)
492
> getScore(100, 500, 800, 10)
482
> getScore(100, 500, 800, 20)
462
> getScore(100, 500, 800, 50)
408
> getScore(100, 500, 800, 100)
343
> getScore(100, 500, 800, 200)
276
> getScore(100, 500, 800, 300)
221
> getScore(100, 500, 800, 400)
177
> getScore(100, 500, 800, 500)
142
> getScore(100, 500, 800, 600)
114

This new curve will help differentiate between the most difficult challenges for the top few teams while still keeping the challenges most people (ucla students, other beginners, etc.) solve at a fun point level.

[Aplet123]

Dropoff seems too slow at the start (I think a 50 solve challenge should be 300 points or less), and I think it'd be nice to factor in the max solves for the dropoff at higher solve counts.

[r2dev2]

Putting this here: new curve I'm working on which is harsher at top that I'm working on: 50 solves is 360 points. This new curve is a bit inflated for the 100-700 solve area so needs work there.

I want to keep 50 solves firmly above 300 so we have enough room for distinguishing 100/200/300/400/... challenges while still incentivizing people to go for 50 solve challenges.