Open smhcnshn opened 4 months ago
Are the packs loaded using the velocity api or on the backend?
And which version of Minecraft are you using?
1.19.4 and 1.20.2 and they both are loaded on the backend
So the backends have different versions? (and have ViaVersion) If so have you tried with only one version? (aka without ViaVersion)
Sure, i've put them into the same versions and disabled viaversion on both, issue persists, this time console printed this stacktrace out
java.io.IOException: Kurulan bir bağlantı, ana makinenizdeki yazılım tarafından iptal edildi
at java.base/sun.nio.ch.SocketDispatcher.read0(Native Method) ~[?:?]
at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:46) ~[?:?]
at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:330) ~[?:?]
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:284) ~[?:?]
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:259) ~[?:?]
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:417) ~[?:?]
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[velocity.jar:3.3.0-SNAPSHOT (git-82189a6a-b366)]
at java.base/java.lang.Thread.run(Thread.java:842) [?:?]
the line at the top just says that generic kick message forcibly closed something like that
are you using different UUIDs in the server.properties for the resource packs? You're also using an outdated version
They are different, are you talking about the velocity version? I had downgraded it thinking it was an issue with the latest, because i also had the issue with the latest release
Also this time it prompted the mojang loading screen, but the bar couldnt complete and restarted the load few times before kicking me with resource reload failed message at the top right on my screen
If we connect to two backend servers that both have their own resourcepack, switching from the first server to a second one, the second backend will have issues loading the resourcepack, it won't even prompt the user, it will just get stuck without doing anything however connecting to the second backend directly without connecting to the first one enables the pack to load, keep in mind that both servers have their own different packs
Proxy --> Backend1 (pack loads) --> Backend2 (pack won't load)
Proxy --> Backend2 (pack loads)
I have confirmed this situation only happens while under a velocity proxy.