CONFIG Configuration File EN

SDM Shop 2 Configuration

The config controls how shops, limiters, and statistics are stored, and also defines the server-side behavior of the shop keybind.

Example:

openShopKeybindShopId: sdm:default
storageType: JSON
mongodb:
  uri: mongodb://127.0.0.1:27017/?replicaSet=rs0
  database: sdm_shop
  shopsCollection: shops
  limiterOffersCollection: limiter_offers
  limiterPlayersCollection: limiter_players
  dailyStatsCollection: daily_stats
  serverName: server_1

Main Fields

Field	Type	Description
openShopKeybindShopId	resource location/string	The shop opened by the client “Open Shop” keybind. An empty string disables keybind opening on the server side. If no namespace is specified, sdm is used.
storageType	enum	Storage type: JSON, MONGODB, or CUSTOM.

Storage Types

• JSON — shops and data are stored locally in the server config folder. Best for a single server.
• MONGODB — data is stored in MongoDB and can be synchronized across multiple servers.
• CUSTOM — storage is provided by an addon or another mod.

MongoDB

The mongodb block is used only when storageType: MONGODB.

Field	Type	Description
uri	string	Connection string. Local example: mongodb://127.0.0.1:27017/?replicaSet=rs0.
database	string	Database name.
shopsCollection	string	Shop collection.
limiterOffersCollection	string	World/offer limiter collection.
limiterPlayersCollection	string	Player limiter collection.
dailyStatsCollection	string	Daily statistics collection.
serverName	string	Unique server name, such as survival_1 or lobby. Used to prevent “echo” updates where a server reacts to its own database writes.

If serverName is left empty, the core may generate a random identifier. For stable multi-server synchronization, set a clear persistent name.