#Errored while handling error... wtf.. -> What?
43 messages · Page 1 of 1 (latest)
Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!
Paste version of message.txt from @still hemlock
Paste version of message.txt from @still hemlock
looks like it starts or is in part in base/tags/blocks/mekanism/cardboard_blacklist.js

ServerEvents.tags('block', (event) => {
event
.get('mekanism:cardboard_blacklist')
.add(/.*/)
.remove([/chest$/, /drawer$/, /cooler$/, /crate$/, /cabinet$/, /barrel$/, /basket$/])
.add([/sophisticated.*:/, /mekanism:/, /functionalstorage:/]);
event
.get('mekanism:cardboard_whitelist')
.add([/chest$/, /drawer$/, /cooler$/, /crate$/, /cabinet$/, /barrel$/, /basket$/])
.remove([/sophisticated.*:/, /mekanism:/, /functionalstorage:/]);
});
It pretty much mentions 3 different scripts in that single error tho
did you change any code in either of the 3 or did it just start erroring?
It was erroring out for past 2 months
But today I've got "Errored while handling error" 😅
This is the other post about tag issues we have:
https://canary.discord.com/channels/303440391124942858/1049325853416366151
We have pretty much no idea why its blowing up, and we had reworked all of our tag scripts multiple times
Removing all loops
all variables
And yet, it still happens 
Funnily enough, the same scripts work fine on older versions of Rhino on 1.19.2*
This time I'm more curious about this Error while error handling, because that never happened before 
on a side note if you hate all those 'failed to parse recipes' warnings.... this snippet gets rid of all the smallship ones
ServerEvents.highPriorityData(event => {
// Small ships (has recipes for types not yet in 1.19, keep an eye out for new types)
let ships = ['dhow', 'galley', 'rowboat', 'war_galley', 'drakkar']
let woods = ['acacia', 'oak', 'dark_oak', 'jungle', 'spruce', 'birch']
ships.forEach(ship => {
woods.forEach(wood => {
event.addJson(`smallships:recipes/${wood}_${ship}`, {
type: "minecraft:crafting_shaped",
conditions: [
{ type: "forge:false" }
]
})
})
});
})
o.o, Thx 
I'm a bit sceptical about condition forge:false tho, I already saw a spam in the logs about it >.> Will probably try to re-do the script that we use to disable Arc Furnace recycling
[22:35:15] [Render thread/WARN] [ne.mi.co.lo.LootModifierManager/]: Unable to decode loot conditions
com.google.gson.JsonSyntaxException: Unknown type 'forge:false'
at net.minecraft.world.level.storage.loot.GsonAdapterFactory$JsonAdapter.deserialize:L99
at com.google.gson.internal.bind.TreeTypeAdapter.read:L69
at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read:L41
at com.google.gson.internal.bind.ArrayTypeAdapter.read:L72
at com.google.gson.Gson.fromJson:L963
at com.google.gson.Gson.fromJson:L1034
at com.google.gson.Gson.fromJson:L1006
Oh wait
No. 
I haven't seen any errors for all my recipe overwrites, but it wouldn't surprise me.... could be an allowed condition in recipes but not loot?
It could me that actually.
ServerEvents.highPriorityData((event) => {
event.addJson(`immersiveengineering/recipes/arc_recycling_list.json`, {
type: 'immersiveengineering:generated_list',
conditions: [{ type: 'forge:false' }]
});
});
This is what we use, it "works" but generates errors
I did learn though that virtual datapacking over advancements are a bad idea
still better to actually make those a file in /kubejs/data
was getting rid of the give you book advancements on first login... and if you /reload the original takes over for a min and gives you the books
haha
although maybe that's not intended behavior, but that would be a Max or Lat question
I would guess its not intended
But we will probably not get any bug fixes until Lat fixes Ichor
also, now I'm curious if replacing arc_recylinst_list.json with just empty json would work.
As this is the original:
{
"type": "immersiveengineering:generated_list"
}
@still hemlock Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!
@still hemlock Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!
@still hemlock Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!
@still hemlock Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!