#Mod version discrepancy when downloading the default mods from curseforge

49 messages · Page 1 of 1 (latest)

lapis creek
#

This is easily fixed by manually updating kubejs to build 15 but i thought i'd submit this because this will happen every time a new person downloads kubejs from the curseforge page and might cause confusion with people downloading kubejs for the first time and dont know how to check logs. I've uploaded one error with probejs and one without @amber ermine

vale lintelBOT
#

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

lapis creek
#

not sure if youre already aware of this lat

#

oh actually its still giving the same error even when i update to build 15 >.>

amber ermine
#

are you sure the mods are broken?

#

I saw something similar few days ago

#

where all the files were the same

#

bugged out by launcher

#

cc @umbral pendant

lapis creek
#

idk if they're broken but all i know is i downloaded them straight from the curseforge launcher

#

ahhh

amber ermine
#

show your mods folder

lapis creek
#

kk

amber ermine
#

with filesizes

lapis creek
amber ermine
#

uh oh

#

arch and rhino are the same jar

#

upload them

amber ermine
#

Im pretty sure this is cf bug

lapis creek
#

yikes

#

fair enough

amber ermine
#

in fact neither of them are what they claim to be

#

both are kubejs

lapis creek
finite maple
lapis creek
#

wait

#

i coulda sworn i downloaded rhino but it downloaded architectury instead

#

ill have to double check

#

nah im going crazy

#

nvm

umbral pendant
#

you're doing the thing i did which i hate heh

#

oh what the fuck

#

what is curseforge doing

umbral pendant
#

nah it's my bad

#

i was the one who normalised this behaviour heh

#

anyways now that i'm not ingame that is fucked up

#

i'm assuming this doesn't happen normally on cf?

amber ermine
#

ive seen it before few days ago

#

if I've seen it twice, it must be super common

umbral pendant
#

well shoit

#

hope it's on their radar then

lapis creek
lapis creek
#

closing this cause its not a kubejs sided issue