Resources · medium severity · found in the console

A resource started, but a feature inside it is silently dead

The server console prints a line like this.

What the console says

<feature> are not set
<feature> are not set
<feature> will not load because … Not Found
<feature> is not set…will not work

What it means

A resource started cleanly, but <feature> is not configured — that feature is silently doing nothing while the rest of the resource works.

How to fix it

Open the resource's key/config file — usually configs/ApiKeys.lua, config.lua, or similar — and fill in the named value.
Restart just that resource and confirm the warning is gone from the console.
If the feature is not wanted, say so deliberately: disable it in the config rather than leaving a permanent error printing on every boot.

When it is not this

This is NOT a crash and NOT an outage — the resource is running and everything else in it works. Severity stays medium precisely because reporting it as urgent trains people to ignore the tool. It is also legitimate to leave a feature off on purpose: an owner who does not want video calls has no reason to buy WebRTC keys. Acknowledge those per server rather than repeating them. The value here is narrow and real: the server LOOKS healthy, the resource reports 'started', and a paid feature quietly does nothing until a player complains — which is exactly the gap a console reader is for.