Hide geocaches at the baked landmarks #177
Labels
No labels
accessibility
animation
audio
bake
blocked
bug report
controversial
cosmetics
documentation
easy
economy
events
feature request
gadgets
hard
impossible
medium
multiplayer
physics
rendering
social
ui
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
elsie/liuverse#177
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A geocache is a small tin with a logbook, and the campus is full of places that deserve one: the sculpture trail, the tower, the orchard, the old railway. Each cache has a clue drawn from the landmark, not a coordinate, and finding it logs the visit. A journal shows what is left, and the first finder on a server gets the credit.
How it fits. The bake already names landmarks, sculptures and signs; the interaction system already resolves a prop under the crosshair. A cache is a tiny new prop placed at a landmark, plus a journal panel. The clue is authored data keyed by landmark, so it can live with the world rather than in a separate service. No wire change is needed for the cache itself; the log is a small server message.
Scope.
Related. #201 (passport), #200 (records), #202 (newspaper), #208 (orienteering).