mirror of
https://github.com/Minestom/Minestom.git
synced 2024-12-28 12:07:42 +01:00
Added info about chunk potential memory leak
This commit is contained in:
parent
2285c9622a
commit
f1d046753c
@ -41,7 +41,11 @@ import java.util.concurrent.CopyOnWriteArraySet;
|
||||
* Chunks can be serialized using {@link #getSerializedData()} and deserialized back with {@link #readChunk(BinaryReader, ChunkCallback)},
|
||||
* allowing you to implement your own storage solution if needed.
|
||||
* <p>
|
||||
* You can create your own implementation of this class by extending it and create the objects in {@link InstanceContainer#setChunkSupplier(ChunkSupplier)}.
|
||||
* You can create your own implementation of this class by extending it
|
||||
* and create the objects in {@link InstanceContainer#setChunkSupplier(ChunkSupplier)}.
|
||||
* <p>
|
||||
* You generally want to avoid storing references of this object as this could lead to a huge memory leak,
|
||||
* you should store the chunk coordinates instead.
|
||||
*/
|
||||
public abstract class Chunk implements Viewable, DataContainer {
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user