Defending myself
Before I begin, I will include an incredibly important piece of logs here for you to keep in mind. This error only comes up when my Minecraft client is interrupted while it is writing a packet. Scenarios like this only happen when it's interrupted on the server-side (meaning I was kicked from the server). This does not occur when I disconnect on my own accord. I will be using this to differentiate instances of me disconnecting on my own accord vs. getting kicked/banned.
[17:29:06] [main/ERROR]: Writing packet:
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@1f3023fa[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@536fa9c2[Wrapped task = com.replaymod.recording.packet.PacketListener$$Lambda$5343/0x0000000801a51ba8@44c3ff46]] rejected from java.util.concurrent.ThreadPoolExecutor@3f568d1b[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 56240]
at Not Enough Crashes deobfuscated stack trace.(1.16.5+build.6) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2057) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:827) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) ~[?:?]
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:123) ~[?:?]
at java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:714) ~[?:?]
at com.replaymod.recording.packet.PacketListener.save(PacketListener.java:202) ~[replaymod-1.16.4-2.5.2.jar:?]
at com.replaymod.recording.packet.PacketListener.lambda$save$1(PacketListener.java:167) ~[replaymod-1.16.4-2.5.2.jar:?]
at net.minecraft.util.thread.ThreadExecutor.executeTask(ThreadExecutor:191) ~[?:?]
at net.minecraft.util.thread.ReentrantThreadExecutor.executeTask(ReentrantThreadExecutor:23) ~[?:?]
at net.minecraft.util.thread.ThreadExecutor.runTask(ThreadExecutor:153) ~[?:?]
at net.minecraft.util.thread.ThreadExecutor.runTasks(ThreadExecutor:130) ~[?:?]
at net.minecraft.client.MinecraftClient.render(MinecraftClient:1015) ~[?:?]
at net.minecraft.client.MinecraftClient.run(MinecraftClient:681) ~[?:?]
at net.minecraft.client.main.Main.main(Main:215) [intermediary-minecraft-1.16.5-client.jar:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:567) ~[?:?]
at net.fabricmc.loader.game.MinecraftGameProvider.launch(MinecraftGameProvider.java:226) [fabric-loader-0.11.3.jar:?]
at net.fabricmc.loader.launch.knot.Knot.launch(Knot.java:146) [fabric-loader-0.11.3.jar:?]
at net.fabricmc.loader.launch.knot.KnotClient.main(KnotClient.java:28) [fabric-loader-0.11.3.jar:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:567) ~[?:?]
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:210) [NewLaunch.jar:?]
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:245) [NewLaunch.jar:?]
at org.multimc.EntryPoint.listen(EntryPoint.java:143) [NewLaunch.jar:?]
at org.multimc.EntryPoint.main(EntryPoint.java:34) [NewLaunch.jar:?]
Display More
For some reason, the Skyblock server gave my client a real hard time whenever I joined it. I have excluded the errors caused by the Skyblock server that came up every time I joined to keep the logs readable.
"He was banned multiple times"
A claim frequently brought up throughout this thread is that I was ban bypassing "multiple times". A claim like this requires evidence of me knowing I was banned in the first place and showing intent to bypass in the first place. The opposing side has yet to present evidence that shows any of the following:
- I was banned at all before EvaXephon
- I knew I was banned in the first place, and intentionally bypassed my ban to get around it
Until I read this thread, I was completely unaware that my previous names were even banned in the first place. I had assumed that I was only banned by IP and under the username EvaXephon. Until I was banned under EvaXephon, I had not received a ban message.
I've included the client-side logs of my sessions on the Skyblock server, along with the username I used. In between bluewestwood and cat, I believe my connection was throttled and I had issues connecting. However, on my end I was only getting blank disconnected messages. After a few seconds, I was able to get on though. This also occurred between ballsack and CuckedFunningly.
It is in EvaXephon's logs where you see a unique message about failing to write packets. As I previously mentioned before, this only comes up when the client is interrupted (usually by getting kicked or banned whilst online) whilst it's writing a packet to send to the server, not when leaving on your own accord. This would explain why it only shows up in the EvaXephon session, and not the others. The point I'm trying to make here is simple: I wasn't kicked with a ban message until the name EvaXephon was banned, which means either I was banned before but I didn't know because I was not kicked with a ban message yet or the claim I was banned or bypassed more than once intentionally is completely false. I bypassed only once, and I made it perfectly clear what I was joining for in the username ip_check.
I'll admit my handling with ip_check wasn't great and could have been better, but there's nothing I can do about it now except learn and move on.
"He hacked and cheated multiple times"
True. Most of the anticheat detections were from me deliberately setting it off (using fly and going off an edge repeatedly) to mess with Red. I'm cheeky like that.