#Minehut being weird with resource packs
39 messages · Page 1 of 1 (latest)
I can't check the logs rn but, where is the resource pack hosted? Is it for itemsadder?
it is itemsadder yes, hosted by lobfile
lobfile is one of Minehut's allowed pack hosts so it should work fine
the pack works and everything, its just that this error appears
are you using a proxy or direct to paper
is your proxy up to date cause googling it shows an issue with an older velocity version
yeah if you only have 1 server and it is 1.19.2+, you can just connect that directly
im on 3.3.0, the latest
do you have any other plugins sending the pack. cause it says that can happen if you try sending the pack twice or something
i use itemsadder to manage the pack
though i would think that someone would've reported this issue to them if it was their fault
since its a pretty popular plugin
I've seen other people use lobfile with itemsadder on Minehut fine so not really sure
i mean, its not like the pack doesnt work, its just an annoying error that i hoped wouldnt exist in the first place
if it cant be helped i guess i can live with it
what is your specific velocity version?
but like, this is another person who has connected their server to minehut and gets the same error as me, this is from the paper discord server
idk, i installed it like 6 months ago, but it seems to still be the latest version
says 3.3.0
like what build version. cause a github issue on velocity, someone says they first experienced that issue on 3.3.0-350
350 was 7 months ago, i think we're on 371(?)
try updating to the latest velocity version
this happens in the server console
ive been getting this error since i linked with minehut it always loaded the pack anyway so i just ignored it. However if you find a solution would love to know how to get rid of seeing the error
i have my packs hosted with mc-packs and am using itemsadder to create the packs as well
i cant tell if this is a coincidence
we are both using itemsadder
it could actually be an itemsadder issue
to debug, try loading a different pack not generated from itemsadder and see if that still shows the error