Minecraft Version

1.20.1

KubeJS Version

2001.6.5-build.16

Rhino Version

2001.2.3-build.10

Architectury Version

9.2.14

Forge/Fabric Version

47.4.6

Describe your issue

This exception is created by using lots of "fluid" as fulid input in some recipies which has no problem in forge but may cause problems in Rhino's checking instead of using "name" (neoforge 1.20.1 may has the same issue)

Crash report/logs

No response

As the TiC people told you, please provide logs.

server.log
tic3 use "fliud" in recipies
e.x.:
{
"type": "tconstruct:alloy",
"inputs": [
{
"amount": 250,
"catalyst": true,
"fluid": "minecraft:water"
},
{
"amount": 100,
"fluid": "minecraft:lava"
}
],
"result": {
"amount": 100,
"fluid": "tconstruct:molten_obsidian"
},
"temperature": 1000
}
KubeJS doesn't support "fluid" (using "name" only)

As the TiC people told you, please provide logs.

sorry i've forgot logs

server.log tic3 use "fliud" in recipies e.x.: { "type": "tconstruct:alloy", "inputs": [ { "amount": 250, "catalyst": true, "fluid": "minecraft:water" }, { "amount": 100, "fluid": "minecraft:lava" } ], "result": { "amount": 100, "fluid": "tconstruct:molten_obsidian" }, "temperature": 1000 } KubeJS doesn't support "fluid" (using "name" only)

which means when you try to use
ServerEvents.recipes(event=>{
event.custom({
type: 'tconstruct:casting_table', \ or any recipies provided by tic3 which use "fluid" as fluid inputs
........
})
})
kubejs will always raise errors in checking other official recipies