#KubeJS isn't anymore Serverside in 1.19.2?

62 messages · Page 1 of 1 (latest)

grand meadow
#

In 1.19, it was possible that vanilla client join fabric servers with kubejs.
But in 1.19.2, client get kicked with message Internal Exception: io.netty.handler.codec.DecoderException: net.minecraft.class_148: Loading NBT Data immediately.
Is there a way to fix it or should I stay in 1.19?

calm coralBOT
#

Once your question has been answered, please close this post with </resolve:1050379261372006400> command!

timber shadow
#

if i had to guess this is an ongoing issue with how ingredients are currently done in kubejs for 1.19.2+ (since it requires the custom ingredient api), making serverside only essentially impossible

#

iirc @hot edge said he wanted to take a look this weekend?

#

oh wait no that was the rhino issue which is… equally problematic

hot edge
#

I want a longer weekend

timber shadow
#

i‘d already guessed you didn’t have enough free time (or spent it playing rust and league to relax from work lmao)

#

so no biggie

hot edge
#

best rust wipe ever yesterday

#

lan party too

timber shadow
#

but yeah shit sucks unfortunately still, and 1.19.3 is currently unusable because of forge bugs and vanilla changes 😍

timber shadow
hot edge
#

played until 6 am

#

anyway where am I

#

oh the ingredient thing

#

thats honestly just mb

#

easy single if block to fix it

#

wait it already has if (!CommonProperties.get().serverOnly) {

timber shadow
#

hmm didn’t you want to rewrite the system anyways?

hot edge
#

eventually

#

not this decade

timber shadow
#

to not use kubejs ingredients unless necessary

timber shadow
hot edge
#

yeah yeah

#

god damn it

#

right hold on

#

question 1

#

do we want to bring back tag ingredient

timber shadow
#

probably not

hot edge
#

but vanilla sends list of all items

timber shadow
#

yeah but it should be fine honestly

#

remember 1.18 was fine despite vanilla doing that

hot edge
#

1.18 has tag ingredient

timber shadow
#

yes but it’s always resolved as items because we just use Ingredient.of(tag) for the vanilla ingredient

hot edge
#

no kjs overrides every recipe to use my own tag ingredient im pretty sure

timber shadow
#

whuh

#

no

hot edge
#

when it deserializes recipes

#

it doesnt? hmmm

timber shadow
#

1.18 had IngredientJS

hot edge
#

right

timber shadow
#

oh you mean the way it parses them

hot edge
#

but I parse "tag" as my own from json

#

yes

timber shadow
#

i‘m not sure

hot edge
#

and then it puts those recipes back in to the map

timber shadow
#

but either way you serialise it back to vanilla in the end

hot edge
#

inb4 reason 1.18 runs at all is because KJS injects more efficient tag ingredient

#

im not sure what point it stops doing that

#

idea:

#

add Temp: Tag Name tags

#

"Temp: Ingredient Issue", "Temp: Method Issue" etc

#

so tag all posts that have them

timber shadow
#

yeah that’d be good honestly

#

i‘ll do that when i‘m on my pc so give me a bit

hot edge
#

already did

timber shadow
#

oh lmao

shadow spindle
#

I have the exact same issue, is it still not possible to have kubejs only server side?

hot edge
#

Currently no, but thats not really intended and will be fixed at some point