So why change something that is working perfectly ?
No smeltspeed. no campfire support, no oil refinery support, no charcoal rate,
No smeltspeed. no campfire support, no oil refinery support, no charcoal rate,
Many things not working after updateSolved
Hey!
About charcoal.
What about smelt speed. Lol, speed multiplier. No campfire support? Why do u think so? OMG WHAT IS WRONG WITH THIS WORLD!
Merged post
Works fine.
About charcoal.
What about smelt speed. Lol, speed multiplier. No campfire support? Why do u think so? OMG WHAT IS WRONG WITH THIS WORLD!
Merged post
Works fine.
It means before i can use the plugin i have to add 3 settings for small furnace, large furnace. campfire, oil refinery. water purifier, etc, And before you post an "example" please look at your own overview page which does not have the "charcoal" line in it anywhere.
Is there still a function to cook meat in a furnace ? is there still a function to prevent food burning ?. and as i asked why fix something that is working ?
"Permission": "quicksmelt.use",
"Use Permission": true,
"Speed Multipliers": {
"furnace.shortname": 1.0
},
"Fuel Usage Speed Multipliers": {
"furnace.shortname": 1.0
},
"Fuel Usage Multipliers": {
"furnace.shortname": 1.0
},
"Output Multipliers": {
"furnace.shortname": {
"item.shortname": 1.0
}
},
"Debug": false
}Is there still a function to cook meat in a furnace ? is there still a function to prevent food burning ?. and as i asked why fix something that is working ?
I will update the plugin soon and add meat cooking and preventing food burning. I don't fix the plugin, just updating it.
I would also like to know whether i have to do a "shortname" for each of the "cooked" meats that are available ? or do i not have to do an output one for the campfire when cooking food ?
You should add shortnames only for output items amount of which you would like to change.
I have checked this with .json validator and keep getting error "expecting closing at end" even though the existing original config ends the same way ?
{
"Permission": "quicksmelt.use",
"Use Permission": false,
"Speed Multipliers": {
"furnace.large": 100.0,
"furnace.small": 100.0,
"campfire": 100.0,
"small.oil.refinery": 100.0,
"water.purifier": 100.0
},
"Fuel Usage Speed Multipliers": {
"furnace.large": 10.0,
"furnace.small": 10.0,
"campfire": 10.0,
"small.oil.refinery": 10.0,
"water.purifier": 10.0
},
"Fuel Usage Multipliers": {
"furnace.large": 10.0,
"furnace.small": 10.0,
"campfire": 10.0,
"small.oil.refinery": 10.0,
"water.purifier": 10.0
},
"Output Multipliers": {
"furnace.large": {
"metal.fragments": 100.0,
"charcoal": 200.0,
"metal.refined": 100.0,
"sulfur": 100.0,
"furnace.small": {
"metal.fragments": 100.0,
"metal.refined": 100.0,
"charcoal": 200.0,
"sulfur": 100.0,
"small.oil.refinery": {
"lowgradefuel": 100.0,
"charcoal": 200.0,
"water.purifier": {
"water": 100.0,
"charcoal": 200.0
}
},
"Debug": false
}
Hey!
Just updated the plugin. Added whitelist, you can add raw food there to cook it in furnaces. Proof:
Merged post
About your configuration trouble.
You forgot something, like a '}' character before the "furnace.small"
Merged post
Also please change all
Unload the old version, change the config (fuel usage ..) and load the new plugin version
Just updated the plugin. Added whitelist, you can add raw food there to cook it in furnaces. Proof:
Merged post
About your configuration trouble.
You forgot something, like a '}' character before the "furnace.small"
Merged post
Also please change all
Fuel Usage MultipliersUnload the old version, change the config (fuel usage ..) and load the new plugin version
I will give it a miss and go back to the last version that worked fine.
I'm confused as well.
What was broken and why update? I'm hesitant to update this on my server. The changelog is extremely vague...
Yeah, what this version differs from 4.0.5?
Hey! You can just check out plugin's description to check out what is new. In 5.0.1 I fixed all known issues of 5.0.0
Hello
Here is "some" of my config file:
{
"Permission": "quicksmelt.use",
"Use Permission": true,
"Speed Multipliers": {
"furnace.large": 9.0,
"furnace.small": 9.0,
"campfire": 9.0,
"small.oil.refinery": 9.0,
"water.purifier": 9.0
},
"Fuel Usage Speed Multipliers": {
"furnace.large": 9.0,
"furnace.small": 9.0,
"campfire": 9.0,
"small.oil.refinery": 9.0,
"water.purifier": 9.0
},
"Fuel Usage Multipliers": {
"furnace.large": 5,
"furnace.small": 5,
"campfire": 5,
"small.oil.refinery": 5,
"water.purifier": 5
},
"Output Multipliers": {
"furnace.shortname": {
"item.shortname": 1.0
}
},
"Whitelist": {
"furnace.shortname": [
"item.shortname"
]
},
"Blacklist": {
"furnace.shortname": [
"item.shortname"
]
},
"Smelting Frequency (Smelt items every N smelting ticks)": 2,
"Debug": false
}
I'm getting errors each time I try to change some of the levels on :
},
"Output Multipliers": {
"furnace.shortname": {
"item.shortname": 1.0
}
},
So when I add "furnace.large" and "metal.fragments" 5.0 or other furnance.shortname or other item.shortname I keep on getting errors.
(09:42:38) | Unloaded plugin Quick Smelt v5.0.1 by Iv Misticos
(09:42:38) | [Quick Smelt] The configuration file contains an error and has been replaced with a default config.
The error configuration file was saved in the .jsonError extension
(09:42:38) | Calling 'OnServerInitialized' on 'QuickSmelt v5.0.1' took 218ms
(09:42:38) | Loaded plugin Quick Smelt v5.0.1 by Iv MisticosI guess I need some more guidens to set this up to and get it to work.
Thanks for taking on the job and update this awesome plugin!
Hey, @gormie
Please, create a new thread. Also provide a "modified" config with changed output multipliers so I can help you.
Please, create a new thread. Also provide a "modified" config with changed output multipliers so I can help you.
Why was my thread retitled ? I called the thread "why update" and i still have not received a logical answer to that, your overview is vague as it does not instruct users how to config multiple "furnaces" , a typical server will have large and small furnaces, campfire, water purifier and oil refinery, some might also have quarries ,
A complete "demo" config would explain that instead of painting arrows on submitted configs. I went back to a working version of the plugin and would not have posted here again until i saw that the thread had been "hijacked".
A complete "demo" config would explain that instead of painting arrows on submitted configs. I went back to a working version of the plugin and would not have posted here again until i saw that the thread had been "hijacked".
Locked automatically
- 1
- 2