I brought this up in #super-mario-64, and the minor consensus is that 100 Coins is "possible", the same way Red Coins is possible.
According to a FAQ online, DDD has 106 coins. That means you are still required to get at least 5 of the red coins in order to get the 100 coin star. If we already have a rule stating the Red Coins require the sub to be removed (by reaching Bowser in the Fire Sea), it should apply to the 100 coins as well.
The consensus on it being "possible" was that it requires a very specific triple jump. There is no "Strict" category for this since it isn't caps/cannons-based, but it is extremely unreasonable to casual play. If you want to sequence break it, go for it, but I don't think it should be expected.
* Changes:
* When client loses connection to the server through no fault of your own, it no longer forgets your username.
* It is now possible to do /connect archipelago://username:password@server:port or to paste archipelago://username:password@server:port into the connect bar and hit connect, and have both the username/password filled in that way.
* Switch checksfinder client to getting username from url if suppplied by url.
* Correct the print statement
* Add stone theme
* Fix h2 color, change rogue-legacy to stone theme (approved by Phar)
* Add stone theme preview to world api.md
* Different stone theme preview to match other images
* MC: open file selector if client is run without apmc
* MC: linux fixes
* we don't use shell anymore
* use user_path for forge_dir. Unless read-only, this is the same as what cwd is set to.
This updates notify_hints() as follows:
- Sort hints by their 'found' attribute in reverse during the first
iteration, so items not found will show at the bottom.
- Store a tuple of (hint, hint.as_network_message()) in concerns rather
than just the hint so the raw hint data remains available for later
sorting.
- Do the logging.info call as part of this iteration instead of doing
a second iteration pass that does nothing but logging.
- Iterate over concerns (and look up connected clients) rather than
iterating over all clients (and checking for concerns)
