Update: World Scanner now runs automatically, plus a smarter Remy (agent pet)

Implementation Journal
1

a small update on remy and the world scanner

Remy is our ai agent pet: a small rat NPC that lives on our land, walks around it, and can be sent to explore parcels.

the world scanner is now running automatically every 12 hours, checking around 90,600 parcels across decentraland. each scan takes less than a minute.

so far, we’ve found that 52,934 parcels have a deployed scene, while 37,719 are empty. we’re also discovering that having a scene doesn’t necessarily mean there’s something interesting there. many are roads, templates, or default scenes, so we’re working on sorting those out.

you can explore the live map here:

click any parcel to see its scene and change history. you can zoom, pan around, and share a direct link to any location.

remy has also had a small upgrade. the in-world menu is now cleaner and easier to use, and remy can read the shape of the land directly from the scene’s own scene.json instead of relying on a hard-coded layout. we’ve tested this on our 8-parcel land, though other layouts still need testing in the actual world.

there’s still a lot we don’t know. the scanner can tell us what’s deployed, but not how many people visit. we’re also comparing the events we collect with catalyst timestamps before drawing any conclusions about world activity.

one thing i’m curious about is what land owners actually need.

if you run a scene in decentraland, what would you want a little agent like remy to help with?

would it be useful to know when something changes around your land, get alerts when your scene might have a problem, understand visitor activity, or have remy help visitors while you’re away?

i’m still figuring out what would be genuinely useful, so i’d love to hear what you’d want rather than just adding features for the sake of it. many thanks!

Visit: /goto 46,115

Live map: DCL World Scanner

2 Likes
2

As a DCL land owner from what i have heard and myself personally would like to know:

  1. Neighborhood activity: How many surrounding parcels are developed, active, abandoned, or empty? Is the neighborhood improving or declining over time?

2. Nearby attractions: What experiences, games, galleries, events, roads, plazas, and teleport destinations are within walking distance?

3. Actual visitor traffic: How many unique visitors pass through or visit the parcel, and how long do they stay? This may require player activity data, not merely a scanner observing scenes.

4. Parcel visibility and accessibility: Can people easily reach the parcel? Is it near a road or popular destination? Is the build visible from neighboring parcels?

5. Development history: When was the parcel last updated? How frequently has the scene changed? Has the parcel remained undeveloped for years?

6. Neighborhood development trends: How many parcels within a 5-, 10-, or 20-parcel radius have gained or lost active builds over the past 30, 90, or 180 days?

7. Build performance: Does the scene load properly? Are there broken assets, missing textures, excessive geometry, or other performance problems?

8. Land utilization: How much of the parcel’s available area and height is being used? Could the owner make better use of the space?

9. Comparable LAND listings and sales: What are nearby parcels listed for, and what have comparable parcels actually sold for? This would require marketplace and transaction data.

10. Opportunity alerts: Notify owners when a neighboring parcel is developed, a nearby attraction opens, surrounding LAND goes up for sale, or significant changes occur in their neighborhood.