The new multiple choice questions are still a work-in-progress. Manifold is planning to add a button to easily sell soon.
Until then, you can buy a number of NO shares equal to your YES shares (or vice versa) and it will exchange them for that amount of mana.
Resolves YES if there is a feature to sell shares in a multiple choice question before the end of August (even if it is later removed).
The ability to buy opposite shares and redeem them does not count.
It must be supported in the Manifold interface (API support alone does not count).
This is one of the features that Manifold has said they plan for multiple choice:
Adding new answers (Done!)
Sell button
An option for independent answers (that don't sum to 100%) - https://manifold.markets/jack/will-manifold-add-multiple-choice-w
1,000
3.00@JamesGrugett "You can only sell up to -1.1368683772161603e-13 shares."
Very minor issue, seems to be a minor floating point problem, so it still shows I have a position. I was just trying to clean up those fractional shares 😂
@parhizj Thanks for the report! Having trouble reproducing... Maybe the client didn't update with the latest sell bet?
@JamesGrugett I was "cleaning" up some of my bets
https://manifold.markets/FlorisvanDoorn/what-day-of-august-will-manifold-ha
It has only happened once so far (trying to sell shares in 16 in that market)
@jskf I'm glad this didn't come up, but not sure why people think that just a non-functional button existing would count, unless they didn't read the description carefully. IMO it clearly doesn't.
Resolves YES if there is a feature to sell shares in a multiple choice question before the end of August (even if it is later removed).
If there's a non-functional button, that can hardly be called "a feature to sell shares"
@jskf Ah ok. Someone else said "resolution criteria says nothing about the feature actually working >_>" earlier
@parhizj Probably because I'm running the local server which uses the updated sell shares endpoint. I can deploy my change to the dev server so it could work for you.
@JamesGrugett I think I should have been doing it on the dev instead of prod, but yes it worked on dev! Great work. 🎊