Trading, item catalog and economy

Trading combines three things: a catalog of known SCUM items, currently loaded trader settings, and an upcoming set of pricing rules. The administrator can change buying and selling, availability and limits en masse, compare the proposal with the original state and only then send it to the server.

The biggest advantage is a safe workflow. Editing in the administration initially creates a draft; does not change the player economy immediately. You can see the exact difference before application.

Where to find it

• Trading → Items – catalog, search and item detail.
• Trading → Missing - unknown or insufficiently assigned identities.
• Trading → Economy – imported status of traders and import.
• Trading → Settings – working price profile and trader rules.
• Trading → Presets – repeatable trade and category settings.
• Trading → Global – common rules and multipliers.
• Trading → Review - difference between draft and loaded state.
• Trading → History – prepared and applied revisions and their result.

What the main states mean

• Catalog: list of identities known to Nodera. "Verified on server" is a stronger signal than just an imported name.
• Loaded economy settings: a copy of the current trader configuration intended for review. Before editing, load fresh data.
• Draft: working proposal. It can contain hundreds of changes and it doesn't change anything in the game yet.
• Dirty rule: a line that differs from the loaded state.
• Review: final human review of what is added, changed or removed.
• Prepare/Apply: preparing the verified version and sending it via NODERAgent. Applying the profile does not restart the SCUM server.

Recommended Workflow

1. Choose a server and load the current status of traders in Economy.
2. Check the result of the import: the number of trader sections, items, unknown identities and invalid rows. Resolve missing identities before the price adjustment.
3. Create or open a draft. Name it according to its purpose, for example "Food rebalance - September".
4. Edit global rules or specific traders. For a mass change, keep a small test group.
5. Check dirty lines, disabled purchases, fixed prices and limits on Review.
6. Prepare the application and send it to the server. Follow the result in History.
7. If the new configuration requires a game restart, schedule it separately. Apply is not an immediate restart permission.
8. After activation, check several representative traders directly in the game.

Disable rule or remove override?

These are two different operations:

• Disable buy/sell: Nodera will create an explicit rule that the trader should not offer the given operation. This is useful when you want to disable an item on purpose.
• Remove override: Nodera will stop overriding this value and the game or parent rule will use its base. It does not automatically mean "forbidden".

When checking, look at the final effect, not just the empty price field. The value -1 can be a game sentinel for the default price and should not be automatically read as a price minus one.

Example from the Main server

Status of the database as of 1 September 2026.

Duplicate import lines often mean that the same item is being sold by multiple traders; they are not automatically a mistake. It is decided by the trader key and the final review.

Frequent problems

• The item is unknown: resolve its identity or alias. Do not apply a price based on a similar name blindly.
• Draft has hundreds of unexpected changes: could have arisen from an old load or with a different global rule. Create a new fresh draft and compare.
• Apply succeeded, but the trader did not change: check if the game configuration is waiting for a restart and if the correct server and trader were tested.
• Item disappeared instead of returning to default: check the difference between explicit disable and removing override.
• History shows an error: do not create another apply from the same old snapshot without solving the reason.