search

anegostudios / VintageStory-Issues

Vintage Story's public issue tracker for reporting bugs, crashes and the like
41 stars 16 forks source link

Inconsistencies between dedicated server and singleplayer in worldgen #3846

Open Auseawesome opened 2 months ago

Auseawesome commented 2 months ago

Game Version

v1.19.7

Platform

Linux

Modded

Modded

SP/MP

Multiplayer

Description

Using exact same mods: https://mods.vintagestory.at/tpnet https://mods.vintagestory.at/commonlib

Worldgen errors on server (linux), but works fine in singleplayer (windows).

This error gets spammed when generating the world on server, if you enable worldgen mods, a lot of features fail to generate, whereas it works fine on client. I did not report this to mod authors as this appears to be an issue with a builtin function rather than directly with the mod

How to reproduce

  1. Make a singleplayer world with listed mods, it works
  2. Make world with same mods and settings on dedicated server, worldgen issue

Screenshots

No response

Logs

Server worldgen log: server-worldgen.txt

Error message spammed in main log: 27.4.2024 15:04:39 [Server Notification] Tried to get block outside generating chunks! Set RuntimeEnv.DebugOutOfRangeBlockAccess to debug.

Auseawesome commented 2 months ago

I have tested this without any non-worldgen mods and this error still occured

Auseawesome commented 2 months ago

Located the issue, forgot to disable duplicate mods, caused a conflict.

Auseawesome commented 2 months ago

Nevermind, managed to replicate this again without the duplicated mods, it seems to be really inconsistent, I'm going to try to narrow down the cause. I have no idea why it is different between singleplayer and dedicated or if it is a linux/windows difference

Auseawesome commented 2 months ago

@Craluminum2413 is the invalid tag because of what I posted or because it shouldn't have been here in the first place, if it's because of the duplicate mods, could you remove the tag?

Auseawesome commented 2 months ago

Updated issue with the 2 mods that cause this issue to arise, found these by brute force. Common lib is just a library and doesn't appear to cause it on it's own. This issue isn't to do with actual error itself, but discrepancy with it happening on some machines and not on others

Auseawesome commented 2 months ago

Additional info: running server through pterodactyl, I've heard from others running it on linux they haven't had the error, potentially some issue with that?