#NeonNetwork not showing up in game
1 messages · Page 1 of 1 (latest)
[38;2;211;211;211m[[0m[38;2;50;205;50m12:29:31.993[0m[38;2;211;211;211m] [0m[38;2;139;0;0m'NeonNetwork v2026.02.13+054803' is incompatible:[0m
[38;2;211;211;211m[[0m[38;2;50;205;50m12:29:31.994[0m[38;2;211;211;211m] [0m[38;2;211;211;211m- NeonNetwork is only compatible with the following MelonLoader Versions:[0m
[38;2;211;211;211m[[0m[38;2;50;205;50m12:29:31.994[0m[38;2;211;211;211m] [0m[38;2;211;211;211m - 0.6.1[0m
this was in my log file but i use 0.6.1 and have never changed version
solved the issue by getting schmovin''s nl and nn dlls but i'm still curious what went wrong
hhuhhhhhh???
post melonloader/latest.log when you're available
@ancient ginkgo @latent nebula
actually im also pinigng @patent rover and merging this in cause this could be the same issue
should i send them as is or should i try to re download the dlls that were faulty?
yeah i just realized that
QWDKIOWQD<L:WQ
neonnetwork's latest version is built with nwcommon which now more explicitly checks for 0.6.1
i will have my friend check this too
ic
i swear i remember downloading 0.6.1 but i guess i'm misremembering
this gonna be a dumb question but how did they give you dlls? is that different than just redownloading from the githubs?
yeah sure enough it works perfectly when i use 0.6.1
i can't believe i saw what was wrong but i was just like "nah i'm sure i have the right version" and didn't even check
neonlite should've warned you at least once
why'd you think i asked to see your latest.log
no shade intended but you absolutely can't trust end users sometimes
LKWQIDHJQWMOKLDWQ
i been a developer for a loooong time atp i know how it is
LKQWODJMLWQD
@analog vine getting reports you had the same issue
if every1 else could "undo" any fixes and then do this when yall're avail
no clue if relevant but all i did to like 'unfix' was just readding white's storage in plugins
MelonLoader v0.6.2 Open-Beta
^
2/2 so far
WQDJOKQW<PD
can we get 3/3
it's fixing it bcv white's storage isn't downloading the new ver
that was built with NWCommon which checks for v0.6.1 and only v0.6.1 instead of v0.6.1+
okok i think i see
should i try to see if i can make melonloader like not auto update itself in the future?
how tf 😭
if it did auto update you would be on 0.7.1
oh no wait thats so possible i dont read well
the last 0.6 version was 0.6.5
tysm stxtic 
yep
intriguing
NeonLite should've warned yall bro
ermm when would it have done that
if i stay on 0.6.1 like it should be good like for the forseeable future?
yea
awesome :D
the first startup after installing 3.0.10+6
it also says "this will not show up again
😭
prob didnt read it I WILL be honest with you and I AM sorry...
ur good yall dw 😭
.6.1 right?
yeah
alr ty ty
That’s insane that that’s what it was 😭
I wonder why it would suddenly change
@sly jungle is this why your neonnetwork isn’t working?
this is why @dull grove
the amount of people that literally just ignored the warning neonlite gives is crazy

I’m a pussy and get petrified I’ll mess up my save data if I don’t follow everything so when I got that warning I fixed it immediately
QWDKOWQDLWQ
it absolutley wo0uldn't do anything like that it depends on the mods you use ig
but
yeah 0.6.1 is just more stable for neon white
in general
Interesting
I’ve only had major issues like once and it was because of fucking event tracker corrupting something
After this ttt and any green related level crashed my game lmao
oh
cause the trigger fucked up
u can just delete the trackerPB.txt in the ghost directory
i'm so curious what this warning looks like

