[Solved] static WorldSavedData

[Flemmli97]

I have a WorldSavedData which I have a static field for that gets initialized during the WorldEvent.Load. This saves me for example stuff like client-server sync. Is there a downside to this or something else i am missing if i do it this way?

Edited September 7, 2018 by Flemmli97

[LexManos]

You should almost never make anything in MC static.

This thing that saves you 'client-server sync'... what happens on dedicated servers? or lan play where there are multiple clients?

Things should be logically separated by the sides/world they are in.

Also, what happens when multiple worlds load? you say it gets initalized in WorldEvent.Load? Well you do know that is called for all dimensions right? And it can be called multiple times for the same world as they are loaded/unloaded.

[Flemmli97]

ok. what about this then? i have a list of blockpos that i update daily (so i dont have to use ticking tiles). its not a woldsaveddata and since the client doesnt know about it it should be fine? (one instance of the list is created for each world(dimension))

[Cadiboo]

On 09/05/2018 at 8:04 AM, Flemmli97 said:

ok. what about this then? i have a list of blockpos that i update daily (so i dont have to use ticking tiles). its not a woldsaveddata and since the client doesnt know about it it should be fine? (one instance of the list is created for each world(dimension))

it seems you are trying to improve performance. Why don't you make tickable TileEntities with something like

if (getWorld().getWorldTime() % 200 != 0) return;

in their update() methods? them? this makes them only update every 10 seconds (world time is in ticks, 20 ticks per second)