It seems the mod isn't affecting the speed or output multiplier at all, up or down. Mine was set to 50 on both, and I was getting the Vanilla rates. I jumped to 250, 500 and 1,000 no change.

This was with reloading the mod each time, even leaving the server and logging back in. No change.

Current config for my builder server.

{
  "Use Permission": true,
  "Speed Multipliers": {
    "global": 1000.0,
    "furnace.shortname": 1.0
  },
  "Fuel Usage Speed Multipliers": {
    "global": 1.0,
    "furnace.shortname": 1.0
  },
  "Fuel Usage Multipliers": {
    "global": 1,
    "furnace.shortname": 1
  },
  "Output Multipliers": {
    "global": {
      "global": 250.0
    },
    "furnace.shortname": {
      "item.shortname": 1.0
    }
  },
  "Whitelist": {
    "global": [
      "item.shortname"
    ],
    "furnace.shortname": [
      "item.shortname"
    ]
  },
  "Blacklist": {
    "global": [
      "deermeat.cooked",
      "bearmeat.cooked",
      "fish.cooked",
      "horsemeat.cooked",
      "chicken.cooked",
      "meat.pork.cooked",
      "wolfmeat.cooked"
    ],
    "furnace.shortname": [
      "item.shortname"
    ]
  },
  "Smelting Frequencies (Smelt items every N smelting ticks)": {
    "global": 1,
    "furnace.shortname": 1
  },
  "Debug": false
}

Have you granted the permission to yourself? Also have you tried starting the server with no other plugins to see if it conflicts with any?

misticos

Have you granted the permission to yourself? Also have you tried starting the server with no other plugins to see if it conflicts with any?

The perm is to the default group so should work that way, as it has in the past. 

It will be later today before I can whip up my test server to try it alone, but suffice to say there are zero error messages that one would normally get with a conflict.

misticos

Have you granted the permission to yourself? Also have you tried starting the server with no other plugins to see if it conflicts with any?

i have to say after the update yesterday its not working for me on my server either and was working perfectly fine the day before was there an update put out and i just didnt realize it?

OK tried it on my test server with only one other mod (the whitelist to keep others off the server, but myself) and it worked.

So, I went back to my active servers and tried numerous different things until I stumbled upon an odd behavior I have never seen before in Rust (I have run across this in Conan all the time though).

Anyway, to solve this, the permission must be given alone, or if in a block, the last one before server. writecfg.

Alone:

oxide.grant group default quicksmelt.use
server.writecfg

In a block:

oxide.grant group default extendedrecycler.use
oxide.grant group default antiofflineraid.protect
oxide.grant group default bgrade.all
oxide.grant group default blueprintmanager.all
oxide.grant group default quicksmelt.use
server.writecfg