
Which Rust plugin JSON file should you edit?
Start at the folder used by the running server and check its framework. Oxide usually reads settings in oxide/config. Carbon uses carbon/configs. A server moved from Oxide can still have both directories.
Follow the active server and plugin version
Read the game root in your host panel or launch setup. If you see a current folder and a backup, match the live console's plugin version and filename to the files in that game root. On a rented server, check with the host if their panel maps the default folder somewhere else.
Use the plugin's documentation to find the setting. For example, Stack Size Controller's current instructions put individual item stack sizes under IndividualItemStackSize in its config. An old data file or tutorial can describe a previous version that stored them elsewhere.
Watch where the plugin writes a default file
On a test copy, unload the plugin, move the suspected config out of its folder and load the plugin. For a configurable plugin, look for a fresh file with the expected name. Unload the plugin again before putting the saved config back, then load it with the restored settings.
If you still see the old value, check the active path and the version again before touching the matching file in another folder. If no config exists on a fresh install, find out whether the plugin provides one and whether the console says it loaded.