My friend trying to put a vs2 on a server and he gets this error message. Any ideas what we are doing wrong?
Valkyrienskies-common.mixins.json:feature.container_distance_check.MixinContainer: Interface mixin contains a non-public method! Found includeShipsInDistanceCheck(Lnet/minecraft/world/entity/player/Player;DDD)D in valkyrienskies-common.mixins.json:feature.container_distance_check.MixinContainer
I’m not sure what kind of log is that I’ll get a full log file if it’s necessary
Here are some common incompatibilities as of 26 Jan 2024:
Can cause crashes:
Amendments?
Connector extras
Cosmos Heroes
Eating Animation
Epic Fight / Weapons of Miracles
forgero
Groovy mod loader
liquid burner mod
Let me despawn
Leawinds third person
Ready player fun?
regions unexplored
Rubidium - use embeddium
Shoulder surfing
Sound physics remastered
TerraFirmaCraft
The Aether
Timeless and classic - use tac-zero
Webdisplays
Can cause visual problems (invisible ships etc):
2032 world height
Acedium
immersive portals
Leawinds third person - freeze game on eureka helm
No see no tick
Optifine (use embeddium, iris/oculus and simple zoom for alternatives)
Very many players
Other problems:
plug-in / mod hybrid server
Smaller than default world border - can’t interact with ships (only 1.16 maybe?)
Starlight (server-side) - too many physics frames
simple hats - lag?
does potato tick - broken physics
nostalgia tweaks - broken sounds
Deep Mob Learning: Refrabicated - broken rendering of ships
Vanilla server jar - unable to move
Paladin’s furniture - ships crashing AND splitting on assembly
Embeddium (Rubidium) Extras - Lag when ships are made (Use Embeddium++ instead)??? Not reproducable
A binary search can be used to find an incompatibility between VS and your modpack. How it works:
Disable half your mods, except VS its addons and dependencies
Test to see if the problem persists
If the problem is gone, you know the conflict was in the disabled half. If not, its still in your current half
Go back to step 1, except with only the half that has the incompatibility, and half the half
Continue until the problem goes away. You then should know what mod was the issue
If new problems arise while testing, its possible you’ve disabled a mods dependency but not the mod itself. You should try to disable dependency mods last (e.g. citadel, framework, etc.)
It’s also recommended to use a new world, or a copy of your world, since loading a world with a mod missing will delete any of that mods content from the world.
I’ll check its mods.toml when I get the chance to see if it doesn’t specify forge version :thonk:
15 replies not shown · View on Discord
:clueless: