Hi, I’m Zen. I maintain small browser tools and practical guides. One design decision I keep returning to is how to show a useful result without overstating what the data can tell us.

In AION 2 Pets, the library has 206 companion records, while the farming map covers only the 157 with recorded coordinates. I keep those counts separate and link the community sources, because a map pin is a recorded location—not a drop-rate measurement or a guaranteed drop. The collection checklist is also explicitly manual and local to the browser, with JSON backup instead of a game-account connection.

For anyone building a niche data tool: would you put a coverage warning beside every result, or show one clear notice above the map? I’m interested in how other makers communicate incomplete data without making the interface hard to use.

Example: https://aion2pets.app/map/?utm_source=uneed&utm_medium=community&utm_campaign=data_coverage

Independent fan project, not affiliated with NCSOFT; community records are attributed to Wikily. Written with AI assistance and checked against the site’s current features.

Zen Nin

Activity

Products

Posts