What collections are

A collection is a typed, game-specific library that the platform can load for the active team. Collections are separate from projects: a project stores your map data, while collections provide reusable rules, textures, templates, and asset catalogs that many projects can use.

Each collection has a type, target game, optional target engine, visibility, owner information, usage counts, ratings, favorites, storage size, and item count. The API returns the relevant item arrays for the collection type, such as mapping rules for vector mapping, textures for ground textures and roads, or object catalogs for placeable assets.

Browse collections

Open Dashboard -> Collections. The page loads collections for the selected game and active team, then groups them by type. Farming Simulator 25 and Minecraft appear in the game selector, but custom collection creation is currently available only for Farming Simulator 25 vector mapping.

The catalog view shows the default platform collection for a type first, followed by compatible public, private, owned, or favorite collections. Search filters by collection name, description, type label, game label, and owner details. Type filters let you focus on one collection kind instead of scanning the full library.

• Ground textures: texture assets used for terrain surface categories.
• Roads: road-oriented texture or material libraries.
• Vector mapping: rules that classify vector features into editor layers, categories, colors, textures, and saved attributes.
• Water: water surface mapping entries used by the editor water tool.
• Trees, buildings, electricity, and foliage: indexed object catalogs used by the Editor collections panel.
• Export templates: downloadable template archives used by export generation.

Ownership and access

Collections can be built in by MapToPlay, owned by a user, owned by a team, public, or private. Built-in and default collections are maintained by the platform. Public custom collections can be browsed by other users. Private collections are intended for the owning team only.

Private collection access is tier-gated. When a private collection belongs to your team but the team tier cannot use private collections, the API marks it as blocked and the Editor excludes it from selectable collections. Upgrade access or switch the collection to public before relying on it in active work.

How the Editor and exports use collections

When the Editor opens a project, it fetches collections for the project target game and active team. The collection type determines where the data appears: vector mapping collections affect vector import and presentation, while object catalogs fill the Collections panel on the right side of the Editor.

When a vector layer is created from a source asset, the selected mapping collection ID can be stored on the layer metadata. Exports later use that metadata, the current layer state, and the relevant collections to resolve game-ready outputs. For export packaging details, continue with Exports and Export Templates.

Custom collections today

The current custom collection workflow creates Farming Simulator 25 vector mapping collections. On the Collections page, choose Farming Simulator 25 and click New collection. The dialog creates a vector mapping collection with a name, optional description, visibility, and one or more mapping rules.

Other collection types are still real platform libraries, but user-facing custom creation is not exposed for them yet. They are populated through the platform/admin import flows and then consumed by the Editor and export system.