AI assisted with source research and drafting. The small prototype below is a design proposal, not a completed playtest or a claim of personal experience with the game.
A themed collection needs more than additional entries. It needs a way for the player to recognize what makes an entry worth keeping. In an SF exploration game, a catalogue can make unfamiliar creatures and planets easier to remember without turning every discovery into equipment.
No Man's Sky offers a useful example through its Wonders catalogue.
Give each entry a reason to stand out
Hello Games' Fractal update description introduced a Wonders section containing notable discoveries from the player's journey. Its examples include an unusually large herbivore, an ancient tree, and a planet approaching paradise. The same update records valuable treasures and retrieved planetary glitches.
These are documented features of update 4.1, not an announcement of a new release. The useful design observation is that the collection presents several ways for something to be noteworthy. A creature, a tree, and a planet do not need to compete on one shared power statistic.
The later Interceptor update description documents Personal Records, where players can bookmark favourite discoveries, including planets, alien creatures, and flowers. That adds room for individual preference alongside the catalogue's record categories.
This is a design interpretation, not evidence that the catalogue caused the game's commercial success. The narrower question is practical: when a player opens a collection, can they explain why its entries differ?
Prototype the catalogue before expanding the universe
Consider a fictional survey game with six alien plants. Give each plant a distinct image, a short name, a location, and one observable feature. One folds its leaves during rain; another grows around warm rocks. These are invented examples, not No Man's Sky species.
Let a short exploration session add the plants to a catalogue. Start with a simple entry card:
- Show the plant clearly enough to recognize it again.
- State the feature that distinguishes it.
- Preserve where it was found.
- Make the collected state clear without obscuring the illustration.
The purpose is to connect the entry to something the player noticed. A glowing completion badge cannot carry that connection by itself.
Keep the initial test small. After the player collects several plants, ask them to find the entry for one they encountered and explain what they remember about it. Then show a new view of that plant in the world. Can they match it to the catalogue without reading the answer aloud?
If they remember only the rarity colour, the collection may be communicating a ranking more clearly than the plants themselves. That can be appropriate for some games. It does not yet support the goal of making the fictional ecology memorable.
Check what another entry actually adds
Adding thirty more plants would test content volume before resolving the smaller design problem. First inspect the six existing entries for repeated images, indistinguishable descriptions, or details the player never had a chance to observe.
A collection can also become administrative work. If players open it only to clear notification dots, the interface may be demanding attention without giving them a useful reason to return. Observe voluntary revisits, but ask what prompted them; a revisit might reflect interest or confusion.
The prototype's result could be that players enjoy the illustrations while ignoring the descriptions. That would be useful direction for the next iteration, rather than a reason to force more text into the cards.
The Wonders catalogue suggests a modest way to examine SF worldbuilding: give discoveries a persistent, recognizable place in the player's collection. Before adding more alien life, test whether the existing entries preserve something the player can actually remember.
Top comments (0)