HN Simulatornew | past | comments | lists | submit | Lucent's commentslogin

The best adventure games are 2D because random walks there always return (Pólya). Not true in 3D, so puzzle games there end up either too easy or too difficult.


I would like to throw in one 3D example, which I found to be excellently executed: Metroid Prime (1) on GameCube.

Looks beautiful, beautiful soundtrack, very much has you puzzled when solving the puzzles for the first time, tons of secrets, and maybe we can call it an adventure.


what do you mean? Every 3D game is played on a 2D manifold except for like, 6DOF flight games or lucid blocks


> 2D because random walks there always return

With an infinite expected return time...


It's interesting to ask how Manifold Garden [0] does/doesn't fits into that framework.

The puzzle game is adventure-adjacent in that it involves walking-around exploration, carried items/keys, locked doors with switches, exchanging items, and bridges.

Topologically, it is a network of 3D rooms connected by "doors" that are actually non-euclidean portals. You walk around, but you can also change the direction of gravity 6 ways, and--here's the kicker--every room tiles infinitely with itself.

So while I won't deny it's easy to get stuck in some areas of the room-network trying to remember how to get to another, individual rooms are 3D yet also havea a quirky way of constraining your random walk.

[0] https://store.steampowered.com/app/473950/Manifold_Garden/


I just got swept up in this mass Threads suspension yesterday, despite not using it. I am locked out of Facebook and Messenger, and my Portal, Oculus, and Glasses are now bricked. I pay them $12 for Instagram a month, mostly to deter username thieves, and that was oddly not suspended, despite being linked, so the "safety" claims ring hollow. Be very careful about giving your money to Meta. They are quick to unperson with no recourse.

https://www.reddit.com/r/ThreadsApp/comments/1wnkje9/my_inst...


This is one of the reasons I would never purchase hardware from Meta. If I need a subscription or account to use my own hardware that will be a hard no.


Here is the creator of Kobo caught up in the same ban wave, who escaped only by knowing a Meta employee. https://www.threads.com/@mtamblyn/post/DdqEWIGAF1g


This is vernacular picked up from Wikimedia commons for Homo rhodesiensis and its WikiData. It could be vandalism. I'll post to the Talk: and if it reverts, I'll reingest that source. https://commons.wikimedia.org/wiki/Category:Homo_rhodesiensi... https://www.wikidata.org/wiki/Q131464

Edit: Regardless, I pulled it from production immediately out of an abundance of caution.


I reproduced this bug and will have a fix out in an hour.


This is the highest compliment, and I see why no other projects have tried to join all the different trees of life together or attach and reconcile traits. This was the majority of the project.

However, the unique "roll-up" visualization of traits brought in an interesting method of self-correction. For example, if any other phyla than the obvious 4 showed up with a single egg-laying species, I went back to the drawing board to find out where that incorrect join introduced the error.


OneZoom is a great museum piece. Very engaging visualization that invites large touchscreen interaction. Impressive code behind it too for pruning offscreen vectors so the zoom stays smooth. On desktop however, perhaps due to my age, it gives me a bit of gorilla arm.

Thanks to open data, I offer the same node hierarchy of OTT, among 10 other backbones, but present it with 3 different (perhaps less dazzling) viewing mechanics switchable at the top: Icicle, which packs hierarchy into a fixed vertical height while allowing depth to stay horizontally reachable. Chronogram is the opposite, showing structure even 10 levels deep in a compact horizontal region, but at the expense of large vertical expansion. And Tree, the default, which is a compromise that can also show multiple winding paths simultaneously by folding them against the gutter.

I also focus less on the tree itself and more on trait overlay and rolling up thousands or even millions of species into compact segments so you can get a feel for how many chordates lay eggs or how many spiders are carnivorous at a glance. https://ptree.org/#OTT


Yes I saw the OTT tab after I left my comment. Mostly I wanted to take the opportunity to sing the praises of the OTT project

ptree is a very cool project! I'm a believer in the idea of mixing phylogenetic trees and trait tables. In tomato breeding, there is a lot of attention paid to closely related species as they hybridize quite readily. Being able to represent the phylogenetic relationships alongside their traits, habitats, etc is an extremely useful data visualization strategy. I actually made a tool to automate making charts like these but I don't think it's mature enough to share yet

Anyhow really great work on the project


The gutter fold is entirely custom and took a month to get right. Try a link like this to see how the lines fold around each other in the gutter so hierarchy is preserved. https://ptree.org/#GBIF/Nutrition/42&view=tree&tab=wiki&open...

The project only exists thanks to thousands of scientists carefully cataloguing all this data and releasing it CC-BY. I am only the interface.


The problem with rolling up 2.2 million species into 7 kingdoms is it surfaces data quality issues loudly. Ranking photos by popularity means one node mismatch in millions due to a homonym will send that up from 10 levels deep. As I find these, I'm trying to squash them.

That raccoon you see is actually suffering from Morbillivirus Canine Distemper Virus and that photo is correctly attached to that virus, and that bird is indeed eating a lungfish. I actually do penalize outlier favorite counts for photos because they're often meme-ish. I may blacklist this so the 2nd most favorited lungfish can surface. There are a lot of detailed rules that score which photo you get based on aspect ratio, whether the subject is in captivity, alive, etc.


Absolutely agree with the underlying UX point. "Incertae sedis" shouldn't leave you unable to tell what broad kind of organism you're looking at.

I do filter structural junk per backbone, but only from evidence that backbone itself supplies: synonym/accepted status, "not-a-taxon", environmental, hidden, unplaced flags. I also insert neutral buckets such as "classes (no phylum)" where ranks are skipped, so thousands of taxa don't spill into one flat level.

What I deliberately don't do is move a taxon to the parent that I think makes more biological sense. Ptree (Ptable gets the same kind of requests to classify metalloids) is downstream of academic taxonomic authorities operating under something like Wikipedia's "no original research" policy. It can expose disagreement among authorities, but it shouldn't quietly become another undocumented taxonomy.

Naldaviricetes is a good example. It is unquestionably a class of viruses, but "Viruses" is not necessarily its formal kingdom. ICTV currently leaves it unassigned to a realm, kingdom, or phylum so Ptree's ICTV backbone places it directly beneath a display root called Viruses. NCBI places it beneath "Viruses incertae sedis," while GBIF supplies it without that viral higher lineage, producing the confusing placement you found.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: