Neptunity and I were having fun on there otherwise I wouldn't care enough to even make this. They're equally as confused since during the whole thing they were <5 feet away but w/e.
Started playing and everything was completely fine for hours then poof, supposed log spam starts right after the dev, admins, and mods join. Kinda weird timing if I was actually cheating lol.
I got to read into Vulcan a bit more and talked to some people, and think it was repeatedly false flagging Criticals Type A and Speed/Invalid friction. The speed part especially feels like some stupid initial hiccup or desync (connection blip, chunk loading, whatever) basically made Vulcan think I was standing where I shouldn't be, so the entire long log is it flagging its own stroke as 'sPEeD iSsUE". Once it gets out of sync with its perfect friction model, every movement packet looks wrong, especially with 85 ping and high FPS from Sodium/Iris tied in to the other stuff. Small things that don't do much unless added on top of each other, especially going through a paranoid anti-cheat.
Not to mention the tons of Criticals Type A is already sketchy enough. Supposedly somebody watched me and saw some 'questionable behavior' which is funny because did they just not.. look? I wonder if it's along the same thought process as those that would yell about people aimbotting in Gmod when they know how to flick. Minecraft has had the same crit combat system since 1.9 and it's pretty damn easy to figure out. Hell, if i'm surrounded by mobs and using something like crit cheats, why not just go full blown aimbot?? Jump up to hit from above once the attack bar charges to get natural crits, that's literally how -Y velocity works in 1.9+. Jump backwards, look around for other places to jump while scanning for other mobs. Repeat. Spazzy? Yeah. Vulcan pisses its pants when someone actually lands crits with decent FPS in the few hundreds and a bit of flicking, then pisses its pants harder with any desync. Like shit, someone watching me just saw how minecraft combat works lmao. I know I was bad at Gmod but that doesn't mean I'm shit at other games.
My mods are standard Fabric QoL/performance: Sodium + Iris, Mouse Tweaks, Jade, Zoomify, ImmersiveUI, OpSec (that's the whole "Unresolved" thing, solely client-side privacy and nothing game-fuckening, as OpSec isn't just a 'minecraft' thing). Those mods already freak Vulcan out, let alone paired with OpSec. Vulcan docs openly say false positives are expected and their changelogs are full of fixes for exactly this Criticals Type A + Speed/Invalid friction stuff on Fabric 1.21.11. None of the mods were grabbed from anywhere sketchy or odd either, coming from the normal official download links from commonly downloaded modrinth pages with millions of other downloads.
The hardcore point is I have zero reason to cheat on a chill non-competitive Vanilla+ SMP lmfao. I was in the middle of building a starter base and neither speed nor crits would be any sort of benefit compared to the trillions of other options that would be available in that situation.
Ah yeah, everything fine for two hours but the second I see staff join I'll turn on speed to cross my two chunk wide border faster and farm some crits on a server with gravestones and a /back command... while dying to the same mob five times and literally getting a 5-death streak achievement.
My mans, this is very silly.
Been part of this community for years without any issues until now. Absolutely WILD.
I got to read into Vulcan a bit more and talked to some people, and think it was repeatedly false flagging Criticals Type A and Speed/Invalid friction. The speed part especially feels like some stupid initial hiccup or desync (connection blip, chunk loading, whatever) basically made Vulcan think I was standing where I shouldn't be, so the entire long log is it flagging its own stroke as 'sPEeD iSsUE". Once it gets out of sync with its perfect friction model, every movement packet looks wrong, especially with 85 ping and high FPS from Sodium/Iris tied in to the other stuff. Small things that don't do much unless added on top of each other, especially going through a paranoid anti-cheat.
For context, I have been using Vulcan for years and am very familiar with its false positives and checks. Speed and Criticals have been developed and improved over the years, not perfect, but false positives tend to not get tripped repeatedly like this. Funnily enough, if Neptunity was not playing on your internet, I would accept your excuse of desync or connection issues, as Neptunity did not set off a single Vulcan check. 85 ping is perfectly fine and does not set off Vulcan. Every chunk is already generated and I can confirm that there were no server "blips" or anything on our side that would cause this to happen.
Additionally - We have had 2 instances of hacking in our server with the same checks being thrown off, both of which have admitted to using hacks/mods/advantage plugins, etc. Same amount of checks being thrown off, same type of checks, etc. So I really find it unhealthy to the community and the minecraft server to accept the opinions of "some people" and someone who read into Vulcan "a bit". This is not even including my own history with the plugin with several false positives and even more real checks.
We have several players who play with your exact mods that you sent here with none of them setting off a single check. Also another add - Sending a screenshot of your mod folder provides 0 evidence as files can be deleted.
So, my man, as respectfully as I can write: Either you are playing minecraft on a potato, your personal connection to your internet is garbage, or a sun is leaking cosmic radiation into your pc. This is not the result of "high fps", those false positives tend to show up as "Bad packets".
Not to mention the tons of Criticals Type A is already sketchy enough. Supposedly somebody watched me and saw some 'questionable behavior' which is funny because did they just not.. look? I wonder if it's along the same thought process as those that would yell about people aimbotting in Gmod when they know how to flick. Minecraft has had the same crit combat system since 1.9 and it's pretty damn easy to figure out. Hell, if i'm surrounded by mobs and using something like crit cheats, why not just go full blown aimbot?? Jump up to hit from above once the attack bar charges to get natural crits, that's literally how -Y velocity works in 1.9+. Jump backwards, look around for other places to jump while scanning for other mobs. Repeat. Spazzy? Yeah. Vulcan pisses its pants when someone actually lands crits with decent FPS in the few hundreds and a bit of flicking, then pisses its pants harder with any desync. Like shit, someone watching me just saw how minecraft combat works lmao. I know I was bad at Gmod but that doesn't mean I'm shit at other games.
I personally watched you for several minutes in spectator. You were critting most shots without jumping, as well as hitting mobs without looking at it. Everything I saw matches Vulcan logs. Vulcan would also set off for unnatural mouse and head movement if you were just "good" at the game and have hundreds of FPS, which you set off zero of those types of checks. So this answer means literally nothing, and kinda proves how little you actually know about Vulcan. The speed and critical checks are all being set off because of your lack of Y movement. You were simply not jumping, telling signs of having the "criticals" cheat on with a hacked client or mod.
We copied your entire mod list, I personally tried it on two different machines, even on my phones HOTSPOT with a garbage connection. I could not set the anticheat off even once, even while critting mobs. But if your argument is "well ur just not as god gamer as I am" then GG's I guess.
Started playing and everything was completely fine for hours then poof, supposed log spam starts right after the dev, admins, and mods join. Kinda weird timing if I was actually cheating lol.
The hardcore point is I have zero reason to cheat on a chill non-competitive Vanilla+ SMP lmfao. I was in the middle of building a starter base and neither speed nor crits would be any sort of benefit compared to the trillions of other options that would be available in that situation.
Ah yeah, everything fine for two hours but the second I see staff join I'll turn on speed to cross my two chunk wide border faster and farm some crits on a server with gravestones and a /back command... while dying to the same mob five times and literally getting a 5-death streak achievement.
My mans, this is very silly.
Been part of this community for years without any issues until now. Absolutely WILD.
This is the only single point of evidence provided that actually works. Unfortunately I am not a TTT mod or staff so I didn't have recording set up to record 24/7. The only thing that is weird about it is the why you'd do this.
You being here for X amount of time should never exempt you from the rules, even if this is your first issue. What pains me is that you're making a huge argument that's kinda just a huge nothingburger instead of just admitting it or even saying it was an accident. It's like you're trying to die on a pile of sticks... and that's more confusing to me than anything.
I am extremely confident in my findings, and I stand behind the anticheat and its detection methods as I am way more familiar with its false positives than anyone here. With the visual accounts, logs, the amount of testing we did after you were banned... I don't think I can accept this appeal how its written and shown.
Fair note this might come out as crazed ramblings and I also certainly want to express how I have absolutely nothing against you or any sort of bias. I would love to be wrong, but it has to be proven. This is what I want to urge to staff as well, discounting the anticheat as faulty or bad on the account of one person will set a toxic precedent and allow appeals in the future to be easily dismissed on accounts like these.
Don't take words too literal. Maybe allow the community and the server to accept their own documentation. Vulcans, that is. Chill lmao. I am not angry at anybody nor anything except the anti-cheat system itself, as I know that is just simply what you guys have to go off of and I don't blame you.
alrighty
Appreciate the detail and I get where you're coming from, genuinely. But there are a few things in the actual log data and the logic here that I think are getting glossed over. You aren't the only person with experience with some sort of Minecraft dev and it's weird to get on some sort of high horse about it early on in your response. Possibly not the intention, but that's just the issue with personal interpretations. To reiterate; I am not mad at you nor anybody involved, I was happily having conversations with you specifically while it was all going on, I hold no ill regard and solely interpret things on my own, that interpretation of words can easily be interpreted wrong and not how you meant.
The setback cascade (tp=1589)
Look at the data in that Speed popup, tp=1589, v=1490. That's 1589 server-side teleports (setbacks) and 1490 violations logged. That number is enormous and it's the core of the whole thing.
Slight detour, one thing to think about with this exact thing, hacked clients and cheat mods have their own dashboards. They SHOW you your flag count. This gives more into the "why you'd do this" since after 1500 setbacks and violations, someone hacking wouldn't just... Turn it off?????? A mod client would be absolutely screaming at you before you even hit triple digits letalone quadruple digits. The fact flags kept stacking endlessly definitely gives more into the case someone isn't running a cheat and has the signature of something I would have literally zero knowledge about. The goal for cheating and specifically mod clients is to cheat and be aware of what you send out to not get caught, still directly contradicting the whole "why you'd do this"
But anyhow, when Vulcan starts setbacking aggressively, it forcibly teleports my client to a server-determined position. My client's momentum and positional state are now mismatched with what it just got sent. The very next movement packet looks wrong to Vulcan's friction model, so it flags and setbacks again. That fires off another mismatch. Then another. The entire wall of Speed Type E "Invalid friction" spam isn't me doing anything consistent, it's Vulcan's own correction loop creating a cascade where each setback causes the next flag. A speed cheater doesn't care about setbacks, they just override them. Someone actually being affected by 1589 setbacks is a client being manhandled, not someone speed hacking across two chunks. Copying a copy a few hundred times isn't gonna make the original any better.
The diff=0.0054 with min=1.0E-4 matters too.
That's literally a TINY floating point deviation, not someone blasting across the map. Sodium replaces Minecraft's rendering pipeline and changes how frame timing and math precision work, as you mentioned you have experience with it all and should know this. There's documented precedent of Optifine's FastMath causing a 1E-4 offset in prediction-based anticheat checks for exactly this reason, and Sodium does similar things under the hood. It doesn't take much deviation to start a cascade. This isn't "someone that just ReAd iN tO Vulcan" which I appreciate, it's easy google searching.
The one log image shows Criticals Type A going 1 through 10, but look at what's sitting right in the middle of it: Flight *(Type F)* 2/30. Vulcan briefly thought I was flying.
(So.. I was flying for a split second while speed hacking to get across my tiny chunk border.. Even quicker? Solid.)
That comes from Vulcan's position model being out of sync with my actual position, likely because the setback cascade was already running. When the server setbacks you to a position slightly above ground, you fall the tiny distance to the surface. If you attack during that micro-fall, you have negative Y velocity and g=false on the client, which is exactly what Criticals A checks. So part of what's being logged as "critting without jumping" is attacks landing during falls caused by Vulcan's own setbacks. The Flight flag appearing in that same sequence confirms the position model was already broken at that point. The very fact the flight issue came out of nowhere directly shows that Vulcan already freaked out and caused a negative cascade.
Speed and Criticals have been developed and improved over the years
That's... not a gotcha, that's just how software works. The fact that a check has had multiple things wrong with it and patches over the years doesn't mean it's solved, it means it's been a persistent issue lmao. Vulcan's own changelog has entries specifically fixing Criticals and Speed false positives across multiple versions. "Improved over the years" literally means it was wrong before and has been corrected multiple times. That sentence doesn't argue against a false positive, it acknowledges there's a long history of them. Chances are, it's still having an issue.
I personally watched you for several minutes in spectator. You were critting most shots without jumping, as well as hitting mobs without looking at it.
.... ok. Spectator mode in Java Edition shows a smoothed, interpolated version of the observed player between server ticks. It does not show raw sub-tick input. With several hundred FPS from Sodium, micro-jumps and quick fall transitions happen across multiple frames but within a single tick window. The spectator camera interpolates that into something that looks like no jump happened. What Vulcan actually checks (Y velocity and onGround state at packet level) and what a spectator sees visually are two different things. I'm not doubting what you saw, I'm saying what you saw in spectator doesn't map 1:1 to the packet data Vulcan works from. Not trying to be rude, just directly saying that spectator and actual network data isn't going to relate very much.
At high FPS, movement/rotation packets and attack packets can arrive server-side in a slightly different order than what I'm experiencing on my end. The attack lands while I'm looking at the mob on my screen, but the server processes the attack packet a moment before the latest rotation update.
Neptunity runs a completely vanilla client. No Sodium, no Iris, no OpSec, nothing. And they were right there, less than five feet away, watching my screen the whole time. Zero flags. Not a single one. You want to use that as evidence against me, but I'd actually flip that around and use it the other way lmao. The only meaningful variable between us was the client setup, and the client with performance mods got flagged while the vanilla one didn't. Not sure how that was supposed to be framed in the opposite of being damning, kinda the complete opposite.
We copied your entire mod list, I personally tried it on two different machines, even on my phones HOTSPOT with a garbage connection. I could not set the anticheat off even once, even while critting mobs. But if your argument is "well ur just not as god gamer as I am" then GG's I guess.
Running the same mod list on two machines, even on a hotspot, and not triggering anything, that's why false positives are rare. Not impossible. Rare. You reproduced the setup, you didn't reproduce the game state: my exact JVM version and flags, my uncapped FPS ceiling from an RTX 5050 with Sodium and Iris running full tilt, my DPI and sensitivity affecting packet send timing, and critically, the specific sequence of movement and combat events that kicked off the first setback. You can't reproduce a cascade by just loading the same mods and running around. The cascade has to be triggered. If your test never hit that first setback, it never would have turned into 1589. "I tried it and it didn't happen to me" is completely compatible with "it happened to someone else." This is (as you know) why cascades are hard to figure out for anti-cheats.
Btw you were setting off logs before we joined, your first check was [04-18-2026] [21:38:00].
So the argument with the logs starting before we joined or whatever, I triggered a few early flags, then continued playing, then got banned when staff showed up. And that's supposed to prove intent? I was building a starter base. I was using the same mods I've used the whole session. At most, during the actual play session I left + came back multiple times, installing WIAT then removing and using Jade, JEI and then uninstalling because the server didn't support it, mousetweaks, etc, still none of which would relate to anything that happened. If the first few flags were already a false positive in progress, of course I kept doing whatever I was doing. I was placing blocks and fighting mobs in a small area trying to survive 5 minutes of a night. The idea that I'd watch staff arriving and decide that's the moment to turn on speed for a two-chunk border and farm criticals on a server with /back and gravestones, while simultaneously achieving a five-death streak achievement, is genuinely not a coherent theory of events. Again, if I'm going to cheat why would I stop at criticals and speed in my small little area rather than just use a bow aimbot or straight up just give myself extra damage, or the many dozens of other cheats available for cheat clients.
Yeah. Exactly. That's the point. We actually agree on this part. There is no rational reason to cheat on a chill Vanilla+ SMP. No competitive angle. No leaderboard. No stakes. The "why" is weird and answers itself.
Speed and Criticals are not going to be guaranteed false positives
I never said they were guaranteed. I said the conditions were there for one. Vulcan's own documentation literally states false positives are expected. I'm not citing "some people" or my own casual read of things, I'm citing Vulcan's docs along with user/server error reports, dev docs directly and their own update history. Simply a case of the developer acknowledging their product's limitations in writing. Pointing to personal experience with Vulcan is fair, but it doesn't override the documentation the plugin ships with.
What happened? When a player without Vulcan bypass permissions try to use /wardrobe, Vulcan flags them as cheating and shortly after kicks them from the server. Server logs (replaced our user's nam...
Describe the false positive and how to replicate it This behaviour is hard to reproduce. It happens in fights after hitting someone or while trading hits. When it does flag it flags exactly with an...
Describe the false positive and how to replicate it 1.Use MCC(minecraft console client) to enter a server with Grim Anticheat 2.An alert appears But when I got into the server I didn't do anything,...
Describe the false positive and how to replicate it falseflag.zip https://paste.grim.ac/l77useb Grim version ver GrimAC [00:31:18 INFO]: GrimAC version 2.3.67 [00:31:18 INFO]: Libre simulation anti...
Describe the false positive and how to replicate it Load GrimAC Restart server Always simulation is failed (just walk, sometimes just stay in one place) Can I just disable Simulation? I can't under...
Describe the false positive and how to replicate it Steps to Reproduce: Connect to the server. Start moving and breaking blocks. 2025-07-27.22-01-48.mp4 Note: This issue might be triggered or made ...
Description of Issue (FOR PEOPLE THAT SAY 99.99 IS UNECESSARY THATS NOT THE POINT! A GAME AFFECTING GAMEPLAY IS NOT FINE AND ANY GAMEPLAY AFFECING MODIFICATION IS AN UNFAIR ADVANTAGE AND FLAGS ANTI...
github.com
OpSec mod confirms purely client-side privacy, explains Unresolved client brand
Wabbanode's help center covers many tutorials for managing your server across Minecraft, Rust, Valheim, Stardew Valley, Project Zomboid and more games.
wabbanode.com
Sodium, Iris confirming these are performance mods that alter frame timing
The pile of sticks thingy I actually want to address directly because it's framed in a way I disagree with pretty strongly.
"What pains me is that you're making a huge argument that's kinda just a huge nothingburger instead of just admitting it or even saying it was an accident. It's like you're trying to die on a pile of sticks."
I'm making a huge argument because I'm being asked to admit to something that didn't happen lmfao. The argument existing isn't suspicious, it's the natural result of someone who actually didn't do it not being willing to say they did.The pile of sticks was already there when I got pushed onto it, I didn't build it, otherwise I'd be perfectly fine with dying on the pile. I'm making a huge argument because I want to keep playing with Neptunity because we have been looking for a chill SMP and I thought "Oh hey, you remember that TTT community I was part of and went through some phases? They have an MC server now" and she has continued to have fun, otherwise I would have just said whatever.
And the time thing; you're right that time in a community doesn't exempt anyone from rules. I never said it did. What it does do is establish a track record. Years of playing here with these people and having zero issues doesn't prove innocence in isolation, but it's relevant context. People who cheat tend to eventually get caught doing things that look like cheating. Years of nothing and then a wall of flags tied to a specific mod + high FPS scenario during a casual mob fight on a casual server using reported cheats that wouldn't help with ANYTHING I was doing isn't some weird gotcha
I'm not trying to die on anything. I'm trying to not get buried under a false ban on a server that's part of a community full of people I've talked to for years, by an anticheat that has a documented history of producing exactly this pattern of flags under exactly these conditions. I'm trying to push back against the same BS cycle that people say these communities go through of pushing people away.
This is really really tough, the evidence is against you with no video evidence for you... this argument is cursed.
Your logic is sound, however is doesn't absolve you as a potential really dedicated hacker. I really want to encourage the staff to look through his links, most of the issues you've provided are either closed as non-reprodusible, closed being patched, or not relevant at all to Vulcan.
I also don't want to discount the visual evidence as there was someone not in spectator mode (I think) who also saw suspicious movement who have yet to say.
No matter what the outcome of this appeal is, its an eye opening event and an opportunity as a community and as a dev/staff team to really grow... to next time have that video proof, to learn what we can about the systems that run our servers, to more finely tune our anticheat or to increase its believability.
Nothing personal against you, no high horses were ridden, all I have is my logs and my infrastructure of plugins that I have to stand behind as the developer of this server (aka my baby)
I rest my case here, and leave it up to our staff team. As always, please message me if you have any further questions. I love having my growing moments, and am never afraid to admit when I'm wrong. Thank you!
This is really really tough, the evidence is against you with no video evidence for you... this argument is cursed.
Your logic is sound, however is doesn't absolve you as a potential really dedicated hacker. I really want to encourage the staff to look through his links, most of the issues you've provided are either closed as non-reprodusible, closed being patched, or not relevant at all to Vulcan.
I also don't want to discount the visual evidence as there was someone not in spectator mode (I think) who also saw suspicious movement who have yet to say.
No matter what the outcome of this appeal is, its an eye opening event and an opportunity as a community and as a dev/staff team to really grow... to next time have that video proof, to learn what we can about the systems that run our servers, to more finely tune our anticheat or to increase its believability.
Nothing personal against you, no high horses were ridden, all I have is my logs and my infrastructure of plugins that I have to stand behind as the developer of this server (aka my baby)
I rest my case here, and leave it up to our staff team. As always, please message me if you have any further questions. I love having my growing moments, and am never afraid to admit when I'm wrong. Thank you!
Appreciate the thoughtful response and the way you handled this whole thing honestly. It means a lot that you're willing to sit with it rather than just slam the door, which is sometimes the go-to for servers.
(On the closed issues point, just to clarify my intent there, I wasn't throwing those links as any sort of "aha!". The point was simply that the pattern exists and has been acknowledged by people who build and maintain these systems. Patched means it was real at some point. Non-reproducible in a lab setting is actually exactly what I'd expect given what I described about cascades needing specific conditions to kick off. None of that was meant as a "see, Vulcan is garbage" argument, more just "this specific scenario has a documented history worth weighing." type delio, I was looking around at a bunch of stuff since I like this community/server and wanted to defend what was goin on)
The dedicated hacker thing I get, and I don't have a way to fully disprove it beyond what I've already laid out. All I can say is that nothing about this situation points that direction when you look at the full picture, the context, the motive, the behavior on the server, and Neptunity standing right there flagging nothing the whole time. Not entirely a primary source/objective witness since they're my partner, though lmao.
On the other witness, genuine question, not a challenge. I'd just like to know what they saw and when if that's something that can be shared, because from my end the session was pretty uneventful outside of what's already been discussed. The only other person I came across the entire time from what I remember was (Don't need to put it here per se) and they showed me some stuff and helped me with / commands, but we mostly were around their base, they gave me some stuff in their room, we went down their elevator and out to their shop, we listened + crouch danced to their noteblock music, then I went off and that was it. I don't recall coming across anybody else the rest of time there within any sort of visual range at all since it was quite dead.
No hard feelings regardless of how this lands Protecting your baby is understandable.
I was the first person to initially realize logs were being spammed and informed the mc staff chat about it.
I also want to note that I wasn’t trying to jump to conclusions or anything in the moment!! I was just reporting what I was seeing as it happened.
I do wanna add that I was watching you in vanish (not in spectator) and do wanna comment that at the time your movements did feel a little off... However I also agree that what I saw probably didn't line up 1:1 to what was actually being sent to Vulcan. Being a former TTT staff I do like your aimbot analogy, because while at an initial glance things can seem really odd (even in first person), once you understand the mechanics and how players actually move/play at a higher level, it doesn’t always indicate anything illegitimate. That being said I’ll admit I’m not nearly as familiar with the deeper mechanics on here (especially with Vulcan!!) as I was with TTT, so I could've very well been misreading what I saw at that moment when I was watching u.
I thought for a moment that the Opsec mod was the culprit of the logs being spammed but was unable to get any logs from it, so I can’t really confirm that angle either.
At this point I don’t really feel like I have enough knowledge on Vulcan or the deeper mechanics here to confidently draw a conclusion one way or the other, so I’ll just leave it to my admin @Fiz to review everything and come to a final decision. (I was mainly just reporting what I saw, screenshotting logs, and passing that along to my peers.)
We’ve discussed this as a team with multiple admins and our dev etc, I’ve come to the conclusion to leave the ban as it is. As it stands, we have sufficient evidence with our anti cheat and trust it based on the information it gave us. I still believe some type of hacking was in play. I understand this was not the outcome you wanted and will let you know you can appeal this ban with a lead admin at a certain point in time.
If you have any further questions, you may dm me directly on discord, or another lead etc.
Protecting your baby is understandable.