Giter Club home page Giter Club logo

folia's People

Contributors

denwav avatar jpenilla avatar jroy avatar kashike avatar kennytv avatar machine-maker avatar martijnpu avatar minidigger avatar noahvdaa avatar owen1212055 avatar powercasgamer avatar shoelesstom avatar siroshun09 avatar sofianedjerbi avatar spottedleaf avatar willqizza avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

folia's Issues

Iconsistent redstone ticking under load

Expected behavior

Normal redstone ticking frequency under load.

Observed/Actual behavior

Delays can be observed in redstone contraptions, most obviously in high-frequency redstone clocks. Sometimes redstone goes faster, sometimes slower.

This can be easily observed when watching items going through hoppers when the server is under chunk loading.
Video 1: Items going through hoppers 2 by 2
Video 2: Blocking redstone (every player can see it, it's not client side)

Steps/models to reproduce

This is generally easy to reproduce.

1- Teleport far away /tp 100000 100 3000
2- Place two hoppers, one above the other
3- Place a stack of random items in the hopper above
4- Watch the items. They go 2 by 2, sometimes slower/faster than vanilla.

This can be observed with observer clocks / repeater redstone clock, but it is a little bit harder to trigger.

Plugin and Datapack List

None.

Folia version

[17:08:44 INFO]: Checking version, please wait...
[17:08:44 INFO]: This server is running Folia version git-Folia-"dddaab9" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: dddaab9)
You are running the latest version
Previous version: git-Folia-"41c5548" (MC: 1.19.4)

Other

I didn't change any config file.
This issue seems to stay when you trigger it.
It is important to mention that this issue is not caused by low tps !

Entity#teleportAsync fails while riding entities

Expected behavior

On Paper, while riding an horse/pig/donkey/mule, with or without a saddle, teleporting a player using teleportAsync dismounts the player and teleports it. Getting the future in an async task returns true.

Observed/Actual behavior

On Folia, while riding an horse/pig/donkey/mule, with or without a saddle, teleporting a player through teleportAsync does nothing. Getting the future in an async task returns false. I've also tested this while travelling between the same chunk, different chunks and different ticking regions.

Steps/models to reproduce

In game, mount an entity (tested with horses, pigs, donkeys and mules) and execute a command executing this:
player.teleportAsync(player.getLocation().add(new Vector(1, 0, 0)));
If debugging, get the future in an async task (using the proper scheduler depending on the server implementation) and log it in console.

Plugin and Datapack List

Only the test plugin containing only the test command (Bukkit type).

Folia version

This server is running Folia version git-Folia-22 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: d34fb87)
You are running the latest version
Previous version: git-Folia-19 (MC: 1.19.4)

Other

Having parrots on your shoulder (not while riding) doesn't cause problems. They also get teleported (at 1 block distance).

Villagers "forgetting jobsite blocks"

Expected behavior

Villagers became insensitive to their workbenches and sometimes did not take their jobs

Observed/Actual behavior

They would have picked up work very quickly and moved around the workbench

Steps/models to reproduce

Just give a villager (with default spawn reason) a job site block and after about 20 minutes it occurs.

Plugin and Datapack List

plugins:
image

datapackets:
image

Folia version

This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version

Other

I think this issue is very similar to an open issue on Paper: PaperMC/Paper#9154
And I tried removing all datapackets and plugins for testing, and the results are still :(

Writable books don't turn into Written books

Expected behavior

After signing a writable_book, it should turn into a written_book.

Observed/Actual behavior

writable_book don't turn into a written_book when signed.

Steps/models to reproduce

1- Take a writable_book
2- Write "a"
3- Click on "Sign"
4- Title = "a"
5- Click on "Sign and close"

Plugin and Datapack List

> plugins
[16:39:02 INFO]: Server Plugins (0):

Folia version

> version
[16:38:34 INFO]: This server is running Folia version git-Folia-"7072994" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 7072994)
You are running the latest version
Previous version: git-Folia-"ed7a5c5" (MC: 1.19.4)

Other

When logging out, everything written on the writable_book disappear. Same steps as above, but don't sign the book. Log out and log back.
Works fine with git-Paper-"1704bf7"

Problems when building the project

Expected behavior

When building the project I expect to build the executable files in build/libs dir

Observed/Actual behavior

image

Steps/models to reproduce

Cloning the latest repository
running ./gradlew applyPatches

Plugin and Datapack List

didn't come there yet

Folia version

latest commit March 31 around 1:35pm UTC+1

Other

Since there is no docu how to compile this project I used the one which Folia is forked from
https://github.com/PaperMC/Paper#how-to-compiling-jar-from-source

Problem with some Entity functions

Expected behavior

Expected do get results from:

  • player.getLocation().getChunk().getTileEntities()
  • .getWorld().getNearbyLivingEntities
  • getWorld().getNearbyEntities()

Observed/Actual behavior

[14:45:39] [Region Scheduler Thread #0/ERROR]: Could not pass event ServerTickEndEvent to CoolProtection v1.6
java.lang.IllegalStateException: Cannot getEntities asynchronously
at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:86) ~[folia-1.19.4.jar:git-Folia-"7072994"] at net.minecraft.world.level.Level.getEntities(Level.java:1157) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.craftbukkit.v1_19_R3.CraftWorld.getNearbyEntities(CraftWorld.java:1099) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.craftbukkit.v1_19_R3.CraftWorld.getNearbyEntities(CraftWorld.java:1085) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.craftbukkit.v1_19_R3.CraftWorld.getNearbyEntities(CraftWorld.java:1076) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.World.getNearbyEntitiesByType(World.java:1074) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.World.getNearbyEntitiesByType(World.java:1025) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.World.getNearbyLivingEntities(World.java:856) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]

Steps/models to reproduce

Call

public void test(Player player) {
int currentLiving = player.getWorld().getLivingEntities().size();
int currentEntities = player.getWorld().getEntities().size();
int currentChunkEntities = player.getLocation().getChunk().getEntities().length;

//Fails from here

    int currentChunkTileEntities = player.getLocation().getChunk().getTileEntities().length;
    int nearbyLivingEntities = player.getWorld().getNearbyLivingEntities(player.getLocation(), 30, 200).size();;
    int nearbyEntities = player.getWorld().getNearbyEntities(player.getLocation(), 30, 200, 30).size();;

//print..
}

Plugin and Datapack List

1 plugin been adapted

Folia version

[14:52:02 INFO]: Checking version, please wait...
[14:52:03 INFO]: This server is running Folia version git-Folia-"7072994" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 7072994)
You are running the latest version
Previous version: git-Folia-"00cfbaa" (MC: 1.19.4)

Other

No response

ConcurrentModificationException is thrown for packet is `45`

i don't know how to reproduce this but it just got thrown randomly when players are mass joining

note: set connection-throttle to -1 in bukkit.yml to disable connection throttled kick

System information / folia version

  • folia commit : 5b74945

  • intel i9 9900k

  • 64GB of ram

  • Running archlinux

java args

java -Xms40G -Xmx40G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true -jar folia-paperclip-1.19.4-R0.1-SNAPSHOT-reobf.jar --nogui

console logs at that time

[12:04:33] [ServerMain/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
[12:04:34] [ServerMain/INFO]: Loaded 7 recipes
[12:04:34] [Server thread/INFO]: Starting minecraft server version 1.19.4
[12:04:34] [Server thread/INFO]: Loading properties
[12:04:34] [Server thread/INFO]: This server is running Folia version git-Folia-"5b74945" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 5b74945)
[12:04:34] [Server thread/WARN]: [!] The timings system cannot be enabled on Folia, and has been scheduled for removal from Paper in the future.
    We recommend installing the spark profiler as a replacement: https://spark.lucko.me/
    For more information please visit: https://github.com/PaperMC/Paper/issues/8948
[12:04:34] [Server thread/INFO]: Server Ping Player Sample Count: 12
[12:04:34] [Server thread/INFO]: Using 4 threads for Netty based IO
[12:04:34] [Server thread/INFO]: [ChunkTaskScheduler] Chunk system is using 1 I/O threads, 4 worker threads, and gen parallelism of 4 threads
[12:04:34] [Server thread/INFO]: [io.papermc.paper.threadedregions.TickRegions] Regionised ticking is enabled with 2 tick threads
[12:04:34] [Server thread/INFO]: Default game type: CREATIVE
[12:04:34] [Server thread/INFO]: Generating keypair
[12:04:34] [Server thread/INFO]: Starting Minecraft server on *:25565
[12:04:34] [Server thread/INFO]: Using epoll channel type
[12:04:34] [Server thread/INFO]: Paper: Using libdeflate (Linux x86_64) compression from Velocity.
[12:04:34] [Server thread/INFO]: Paper: Using OpenSSL 3.0.x (Linux x86_64) cipher from Velocity.
[12:04:34] [Server thread/INFO]: Server permissions file permissions.yml is empty, ignoring it
[12:04:34] [Server thread/WARN]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
[12:04:34] [Server thread/WARN]: The server will make no attempt to authenticate usernames. Beware.
[12:04:34] [Server thread/WARN]: While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
[12:04:34] [Server thread/WARN]: To change this, set "online-mode" to "true" in the server.properties file.
[12:04:34] [Server thread/INFO]: Preparing level "world"
[12:04:35] [Server thread/INFO]: Done (0.644s)! For help, type "help"
[12:04:35] [Region Scheduler Thread #0/INFO]: Initialising world 'world' before it can be ticked...
[12:04:35] [Region Scheduler Thread #1/INFO]: Initialising world 'world_nether' before it can be ticked...
[12:04:35] [Region Scheduler Thread #0/INFO]: Initialised world 'world'
[12:04:35] [Region Scheduler Thread #1/INFO]: Initialised world 'world_nether'
[12:04:35] [Region Scheduler Thread #0/INFO]: Timings Reset
[12:04:35] [Region Scheduler Thread #1/INFO]: Timings Reset
[12:04:35] [Region Scheduler Thread #1/INFO]: Initialising world 'world_the_end' before it can be ticked...
[12:04:35] [Region Scheduler Thread #1/INFO]: Initialised world 'world_the_end'
[12:04:38] [User Authenticator #0/INFO]: UUID of player Bot1 is 51a4b33d-8b80-3bde-806f-de4086b03058
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot2 is 16beaa94-ff1b-37a7-8afb-c22dcb8c16d1
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot3 is 73f370b4-497b-347a-a6bb-50d07eb88947
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot4 is c760baae-cdc1-3595-98d0-c7a6e074d851
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot5 is 957bd75a-2799-3660-aa34-d1833e9c00b3
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot6 is 88f0f096-1002-3386-8cc0-5371a30bd66f
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot7 is 9aa06467-c242-3704-9d28-2b9ef52e9d26
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot8 is a2aded80-15d4-38c5-8a6f-e532eedf9bde
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot9 is 84789adf-47f8-367c-b639-0544ccf93ad2
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot10 is dd0e24e4-744e-3f4c-97dc-32ceefa9fdd7
[12:04:39] [User Authenticator #0/INFO]: UUID of player Bot11 is 1197a1e1-1f22-395d-ae93-9836bfcec466
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot12 is d1b6b006-dda2-300d-82c6-b45b3c57f0d4
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot13 is 0685a1bc-d22d-3055-b860-88b198c1a2c2
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot14 is 611d3f14-4877-3dbb-8d40-ab6a074c914d
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot15 is 8760a068-783d-3a3f-9b76-d3d4e0d6745e
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot16 is ef73d3ac-37cd-3dd5-8cfc-4dbbd1edd821
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot17 is 3ef33022-674b-3084-a65c-2c10160c0032
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot18 is c8c9bfd6-8b01-3923-952e-74536f6e7be2
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot19 is d2bb8e6b-93cc-3625-a4fd-9447af52a436
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot20 is 95d3d273-86a4-3189-a5ea-5db62fc595c7
[12:04:40] [User Authenticator #0/INFO]: UUID of player Bot21 is b7ccb05e-738a-32e8-9eb0-8b3b7f3b8024
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot22 is c191f968-26fc-3ffb-92b3-1ba1749a805d
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot23 is 4bed3014-3d38-3d24-b552-e7e0414f54a5
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot24 is 213529b1-842e-387b-844b-0ceb4da44fa6
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot25 is e531232d-50da-3758-b66a-f8d7ccea92c2
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot26 is 49569e3b-2b5f-30a7-9e0a-7f0d26686e86
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot27 is 8c8969e2-2f04-313c-9e5d-073809d5ec24
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot28 is 6d1e9b08-0897-3d82-ba6a-c9e699b3da8d
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot29 is 2ad22741-6ec0-3ba2-aa1d-14b62fc4daa1
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot30 is a3e2f10f-84f1-3a52-b890-4b6fb146dc3b
[12:04:41] [User Authenticator #0/INFO]: UUID of player Bot31 is 8eb19bfd-e68e-35a8-801c-c27a82f0b745
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot32 is 82621a37-d95f-316b-9d7c-1856fbdfdb69
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot33 is 9af54f45-75e8-3832-9159-c58dda2a086f
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot34 is a919da3c-7eae-3f1e-8cdf-fd6735579788
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot35 is 48d28f71-031b-3df7-8c44-8e3d99e68f35
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot36 is 3f91aea2-4986-3101-96ed-1fec5b798cbb
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot37 is 46257f64-e88c-3c3f-98f5-ce5bb158fc41
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot38 is 06d39180-b01b-3935-92db-6e077d3f23f7
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot39 is 466315ed-f2e1-30e2-9e4c-797d844d733c
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot40 is e6433613-18be-3660-add1-1006fe71dd15
[12:04:42] [User Authenticator #0/INFO]: UUID of player Bot41 is 157b7deb-d01a-3c71-bf23-6aac9f599ee4
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot42 is 65144518-66c8-3344-aff9-4c6ab4f183c2
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot43 is e5ce7fa8-0627-3864-8c4f-aaa03af25094
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot44 is a06cb4f4-2263-3936-b61f-600ee5a8ffaf
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot45 is 3a874029-86d9-358f-8860-712e1bbc1a0f
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot46 is 07248cf9-b0f5-31a5-b4e2-2b6bce1cfe33
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot47 is 1ec7eee3-883c-310d-af2a-ed22731121b5
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot48 is 88461141-a850-3588-8b4e-61681c124f5f
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot49 is cc99f2bb-8c71-3323-8d3d-290e2a2fc8a8
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot50 is f3c57ce0-d710-3b16-ae15-de6580b9477f
[12:04:43] [User Authenticator #0/INFO]: UUID of player Bot51 is 95dcc0c1-cd91-3d1a-a510-1fbd285c7f32
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot52 is b9fd63f9-b648-30c7-9048-00e66f5c8b8c
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot53 is d33bcc6b-0217-39e5-929e-33a5b67be642
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot54 is 6426de2f-03e4-3d37-b801-2ff0cbb07240
[12:04:44] [Netty Epoll Server IO #3/ERROR]: Packet encoding of packet ID 40 threw (skippable? false)
java.util.ConcurrentModificationException: null
	at java.util.HashMap.computeIfAbsent(HashMap.java:1221) ~[?:?]
	at net.minecraft.resources.RegistryOps$1.lookup(RegistryOps.java:26) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at net.minecraft.resources.RegistryOps.owner(RegistryOps.java:52) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at net.minecraft.resources.RegistryFileCodec.encode(RegistryFileCodec.java:35) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at net.minecraft.resources.RegistryFileCodec.create(RegistryFileCodec.java:20) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.FieldEncoder.encode(FieldEncoder.java:24) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$1.encode(MapCodec.java:39) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$Instance$8.encode(RecordCodecBuilder.java:376) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$2.encode(RecordCodecBuilder.java:112) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$MapCodecCodec.encode(MapCodec.java:96) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.OptionalFieldCodec.encode(OptionalFieldCodec.java:42) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.OptionalFieldCodec.encode(OptionalFieldCodec.java:17) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$Instance$6.encode(RecordCodecBuilder.java:295) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$2.encode(RecordCodecBuilder.java:112) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$MapCodecCodec.encode(MapCodec.java:96) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.FieldEncoder.encode(FieldEncoder.java:24) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$1.encode(MapCodec.java:39) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$Instance$4.encode(RecordCodecBuilder.java:223) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$2.encode(RecordCodecBuilder.java:112) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$MapCodecCodec.encode(MapCodec.java:96) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.FieldEncoder.encode(FieldEncoder.java:24) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$1.encode(MapCodec.java:39) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$Instance$6.encode(RecordCodecBuilder.java:297) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.RecordCodecBuilder$2.encode(RecordCodecBuilder.java:112) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$MapCodecCodec.encode(MapCodec.java:96) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.ListCodec.encode(ListCodec.java:31) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.ListCodec.encode(ListCodec.java:19) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder$1.encode(Encoder.java:25) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Codec$2.encode(Codec.java:76) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.KeyDispatchCodec.encode(KeyDispatchCodec.java:98) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.MapCodec$MapCodecCodec.encode(MapCodec.java:96) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.BaseMapCodec.encode(BaseMapCodec.java:52) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.UnboundedMapCodec.encode(UnboundedMapCodec.java:43) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.codecs.UnboundedMapCodec.encode(UnboundedMapCodec.java:17) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder$1.encode(Encoder.java:25) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Codec$2.encode(Codec.java:76) ~[datafixerupper-6.0.6.jar:?]
	at com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-6.0.6.jar:?]
	at net.minecraft.network.FriendlyByteBuf.writeWithCodec(FriendlyByteBuf.java:138) ~[?:?]
	at net.minecraft.network.protocol.game.ClientboundLoginPacket.write(ClientboundLoginPacket.java:38) ~[?:?]
	at net.minecraft.network.PacketEncoder.encode(PacketEncoder.java:41) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at net.minecraft.network.PacketEncoder.encode(PacketEncoder.java:14) ~[folia-1.19.4.jar:git-Folia-"5b74945"]
	at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:107) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:863) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:968) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:856) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:113) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:940) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:966) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:934) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:984) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1025) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:306) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
	at net.minecraft.network.Connection.doSendPacket(Connection.java:486) ~[?:?]
	at net.minecraft.network.Connection.lambda$sendPacket$11(Connection.java:460) ~[?:?]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:403) ~[netty-transport-classes-epoll-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]
[12:04:44] [Region Scheduler Thread #1/INFO]: Bot2 joined the game
[12:04:44] [Region Scheduler Thread #0/INFO]: Bot3 joined the game
[12:04:44] [Region Scheduler Thread #1/INFO]: Bot2[/192.168.0.150:59336] logged in with entity id 3 at ([world]-4621.5, 89.0, 4131.5)
[12:04:44] [Region Scheduler Thread #0/INFO]: Bot3[/192.168.0.150:59352] logged in with entity id 2 at ([world]8355.5, 84.0, 7067.5)
[12:04:44] [Region Scheduler Thread #0/INFO]: Bot3 lost connection: Internal Exception: io.netty.handler.codec.EncoderException: java.util.ConcurrentModificationException
[12:04:44] [Region Scheduler Thread #0/INFO]: Bot3 left the game
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot55 is 791fa2a4-6d1b-326c-9e19-b81c030915ac
[12:04:44] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@5d3ee067[id=51a4b33d-8b80-3bde-806f-de4086b03058,name=Bot1,properties={},legacy=false] (/192.168.0.150:59328) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:04:44] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@77aa0660[id=c760baae-cdc1-3595-98d0-c7a6e074d851,name=Bot4,properties={},legacy=false] (/192.168.0.150:59354) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot56 is fc28034d-3802-3dc7-b0d4-87d02b46c9a9
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot57 is 8a9142b1-b9a0-321d-b519-48b8306ac759
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot58 is 276481dc-6fc0-3b11-a636-c898ab4fa1e2
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot59 is c3266127-5720-347b-b955-e92b734fc805
[12:04:44] [User Authenticator #0/INFO]: UUID of player Bot60 is 89485a5f-c947-3cb6-ab6f-3fa6b18acf65
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot61 is 0c3758fd-498d-341d-a10f-26d543b642f8
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot62 is 965f694b-dd01-3238-b32d-db380e1a2540
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot63 is 4a2ec1ed-ba52-3ff3-8b0a-0ac430811ee9
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot64 is b3e20521-9235-396c-8988-463a63c8a637
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot65 is a20d7dda-5128-30de-8c70-834af698d790
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot66 is f7b2a7ca-0177-3337-bc8b-c1da4dd7b24d
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot67 is c1704215-d86b-3598-a165-37db547771d3
[12:04:45] [Region Scheduler Thread #1/INFO]: Bot53 joined the game
[12:04:45] [Region Scheduler Thread #1/INFO]: Bot53[/192.168.0.150:52272] logged in with entity id 16 at ([world]8200.5, 64.0, 3720.5)
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot68 is 427aedbc-3c47-36d0-9424-9f03c1fb5324
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot69 is f42725c8-db5b-38f2-8ac7-9c99f51a709a
[12:04:45] [User Authenticator #0/INFO]: UUID of player Bot70 is 1fb3078a-de4d-3ee6-b900-354c8365c17a
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot71 is 62adbc57-eda5-3e5e-b6d2-6f733f087592
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot72 is 6922d170-22a7-39f7-a8f6-d97250474c02
[12:04:46] [Region Scheduler Thread #1/INFO]: Bot31 joined the game
[12:04:46] [Region Scheduler Thread #1/INFO]: Bot31[/192.168.0.150:59578] logged in with entity id 14 at ([world]-972.5, 69.0, -2412.5)
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot73 is dca9bee8-7973-30d6-a91c-099c25680577
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot74 is c7adf7d1-6c4b-354a-b128-dee7e8c3ae02
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot75 is f4a749dc-1aec-32c0-a84b-88f36d5f5ae2
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot76 is eafeea39-5257-3d21-a142-1383ae9aac8e
[12:04:46] [Region Scheduler Thread #0/INFO]: Bot40 joined the game
[12:04:46] [Region Scheduler Thread #0/INFO]: Bot40[/192.168.0.150:59664] logged in with entity id 15 at ([world]-6681.5, 78.0, -8843.5)
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot77 is 1f99c37f-59c5-33b6-93bf-a3eda5cae819
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot78 is 2b2efe30-ea3c-3cc6-b140-283c179e2937
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot79 is 573a6a59-e87c-3215-85a5-9d3d9f33e686
[12:04:46] [User Authenticator #0/INFO]: UUID of player Bot80 is 1bc4dbb0-ea23-30e4-87f7-8813f279fdf3
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot81 is 0144ac32-0b17-372e-8d31-9f6343f30b69
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot82 is 017cd439-7c52-3267-b10f-1857cc851207
[12:04:47] [Region Scheduler Thread #0/INFO]: Bot67 joined the game
[12:04:47] [Region Scheduler Thread #0/INFO]: Bot67[/192.168.0.150:52422] logged in with entity id 25 at ([world]6928.5, 108.0, 8765.5)
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot83 is 53a55e58-0072-3e34-8e97-5ed77dc08ee1
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot84 is 7cefe449-0918-3b44-af80-062ca770f226
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot85 is 4ffacc43-f83d-3d4e-9188-b09b8f575e80
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot86 is 4e377799-9db3-351e-868a-7ba9e6c36b83
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot87 is d741d244-713e-3067-8e10-ce9e139abecf
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot88 is 4112f704-5c9f-3918-be78-12ff271d4953
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot89 is 7b5b5b5b-e130-3814-930e-686864293ddd
[12:04:47] [User Authenticator #0/INFO]: UUID of player Bot90 is e357d29c-8ffb-356d-a606-8edd58ef4146
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot91 is 60ca0979-f61c-3d03-beef-4447fd96adf8
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot92 is c1792362-fbcc-30af-8d27-ed6ad5809dbc
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot93 is f0531ed4-8ec5-3dd9-b794-2f6d887b3907
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot94 is cc068fff-4415-34b9-b129-51d26b82270b
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot95 is f43be5d3-d050-3438-b399-a16a3e5bd4de
[12:04:48] [Region Scheduler Thread #1/INFO]: Bot34 joined the game
[12:04:48] [Region Scheduler Thread #1/INFO]: Bot34[/192.168.0.150:59598] logged in with entity id 28 at ([world]-4168.5, 72.0, 4739.5)
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot96 is 768d6d90-7c6d-3544-80ce-88e2ccf6c8cd
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot97 is 620b3ac8-3e21-3c7a-a28b-64db928023f9
[12:04:48] [Region Scheduler Thread #0/INFO]: Bot29 joined the game
[12:04:48] [Region Scheduler Thread #0/INFO]: Bot29[/192.168.0.150:59560] logged in with entity id 33 at ([world]1313.5, 82.0, -8461.5)
[12:04:48] [Region Scheduler Thread #0/INFO]: Bot10 joined the game
[12:04:48] [Region Scheduler Thread #0/INFO]: Bot10[/192.168.0.150:59404] logged in with entity id 26 at ([world]5889.5, 69.0, 2830.5)
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot98 is 9ea716ac-5eae-3381-a2ff-bb08d8efecfe
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot99 is 53ec36c0-4db9-37fc-a326-e9bc9e3ef20c
[12:04:48] [User Authenticator #0/INFO]: UUID of player Bot100 is 978e039a-6f13-326b-b242-cfe9792ee0c2
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot101 is db9f25ab-0b7f-3169-b7f9-a5bee3e23ca3
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot102 is 1638452a-ea53-3b98-8e82-ec74efe84b7e
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot103 is 89054a70-fc22-3d4a-b925-ef87692253f6
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot104 is 19f168f7-67d2-38df-a88f-4ffc6837baf7
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot105 is 5e8cd999-d36a-3697-a678-05b6fe6d1fa5
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot106 is 947f67f0-d7a6-3928-8501-4aad864c87f9
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot107 is 5440d951-299f-3317-a7c9-c56ac57fe05d
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot108 is 0c9a754b-705b-3aaf-a8a7-d48142e30b27
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot109 is 8c1ecfea-2272-3ffa-8916-0100b4dc2e4e
[12:04:49] [User Authenticator #0/INFO]: UUID of player Bot110 is f53ec406-88f0-384c-b680-8e334098d503
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot111 is 587fe2ba-2fe7-3acc-8772-b14b40256c1a
[12:04:50] [Region Scheduler Thread #1/INFO]: Bot46 joined the game
[12:04:50] [Region Scheduler Thread #1/INFO]: Bot46[/192.168.0.150:52220] logged in with entity id 38 at ([world]-9142.5, 67.0, 2963.5)
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot112 is 3564e6d3-7586-3b57-9ecb-c35be031c7ef
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot113 is 254bd880-39f4-3358-8ce2-70c58eb1cec2
[12:04:50] [Region Scheduler Thread #0/INFO]: Bot78 joined the game
[12:04:50] [Region Scheduler Thread #0/INFO]: Bot78[/192.168.0.150:52524] logged in with entity id 40 at ([world]-4108.5, 78.0, -1057.5)
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot114 is aa917787-6123-32f3-a7fb-0e85a6e3a561
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot115 is 485e1710-8da2-3e03-82fb-ca236b1b14f8
[12:04:50] [Region Scheduler Thread #1/INFO]: Bot23 joined the game
[12:04:50] [Region Scheduler Thread #1/INFO]: Bot23[/192.168.0.150:59510] logged in with entity id 39 at ([world]-7245.5, 64.0, -4396.5)
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot116 is 3d916bb1-4c1a-3476-8df0-d4aae7d31d26
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot117 is e336ed0a-e928-3109-9458-e4400a9baf0b
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot118 is 1f4d1ae5-f592-3b51-b892-aed1eaaacae5
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot119 is ec6611b4-92eb-3c72-b833-4f3fdb17ff91
[12:04:50] [User Authenticator #0/INFO]: UUID of player Bot120 is 9ac58a61-ab38-3d0a-9cbd-438b919fdaa9
[12:04:52] [Region Scheduler Thread #0/INFO]: Bot28 joined the game
[12:04:52] [Region Scheduler Thread #0/INFO]: Bot28[/192.168.0.150:59556] logged in with entity id 44 at ([world]-1709.5, 63.0, 9514.5)
[12:04:52] [Region Scheduler Thread #0/INFO]: Bot75 joined the game
[12:04:52] [Region Scheduler Thread #0/INFO]: Bot75[/192.168.0.150:52502] logged in with entity id 53 at ([world]6860.5, 63.0, 6566.5)
[12:04:53] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@32e6ef59[id=957bd75a-2799-3660-aa34-d1833e9c00b3,name=Bot5,properties={},legacy=false] (/192.168.0.150:59368) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:04:53] [Region Scheduler Thread #0/INFO]: Bot91 joined the game
[12:04:53] [Region Scheduler Thread #0/INFO]: Bot91[/192.168.0.150:52606] logged in with entity id 61 at ([world]3647.5, 86.0, -1195.5)
[12:04:54] [Region Scheduler Thread #1/INFO]: Bot98 joined the game
[12:04:54] [Region Scheduler Thread #1/INFO]: Bot98[/192.168.0.150:52694] logged in with entity id 62 at ([world]-2666.5, 64.0, 3977.5)
[12:04:54] [Region Scheduler Thread #0/INFO]: Bot66 joined the game
[12:04:54] [Region Scheduler Thread #0/INFO]: Bot66[/192.168.0.150:52420] logged in with entity id 63 at ([world]-3000.5, 66.0, 7786.5)
[12:04:54] [Region Scheduler Thread #1/INFO]: Bot33 joined the game
[12:04:54] [Region Scheduler Thread #1/INFO]: Bot33[/192.168.0.150:59594] logged in with entity id 64 at ([world]-4816.5, 77.0, 4705.5)
[12:04:55] [Region Scheduler Thread #0/INFO]: Bot71 joined the game
[12:04:55] [Region Scheduler Thread #0/INFO]: Bot71[/192.168.0.150:52454] logged in with entity id 66 at ([world]-1442.5, 64.0, -3740.5)
[12:04:56] [Region Scheduler Thread #1/INFO]: Bot111 joined the game
[12:04:56] [Region Scheduler Thread #1/INFO]: Bot111[/192.168.0.150:52808] logged in with entity id 68 at ([world]2004.5, 76.0, -1596.5)
[12:04:57] [Region Scheduler Thread #1/INFO]: Bot99 joined the game
[12:04:57] [Region Scheduler Thread #1/INFO]: Bot99[/192.168.0.150:52698] logged in with entity id 65 at ([world]-3168.5, 65.0, 5735.5)
[12:04:57] [Region Scheduler Thread #1/INFO]: Bot16 joined the game
[12:04:57] [Region Scheduler Thread #1/INFO]: Bot16[/192.168.0.150:59450] logged in with entity id 67 at ([world]6427.5, 70.0, 3498.5)
[12:04:58] [Region Scheduler Thread #0/INFO]: Bot56 joined the game
[12:04:58] [Region Scheduler Thread #0/INFO]: Bot56[/192.168.0.150:52302] logged in with entity id 79 at ([world]6014.5, 67.0, 2139.5)
[12:04:58] [Region Scheduler Thread #1/INFO]: Bot73 joined the game
[12:04:58] [Region Scheduler Thread #1/INFO]: Bot73[/192.168.0.150:52486] logged in with entity id 70 at ([world]2428.5, 64.0, 3271.5)
[12:04:58] [Region Scheduler Thread #0/INFO]: Bot25 joined the game
[12:04:58] [Region Scheduler Thread #0/INFO]: Bot25[/192.168.0.150:59528] logged in with entity id 74 at ([world]-6822.5, 70.0, -2691.5)
[12:04:59] [Region Scheduler Thread #1/INFO]: Bot109 joined the game
[12:04:59] [Region Scheduler Thread #1/INFO]: Bot109[/192.168.0.150:52792] logged in with entity id 83 at ([world]-6070.5, 63.0, 5477.5)
[12:04:59] [Region Scheduler Thread #0/INFO]: Bot110 joined the game
[12:04:59] [Region Scheduler Thread #0/INFO]: Bot110[/192.168.0.150:52802] logged in with entity id 84 at ([world]7465.5, 67.0, 2047.5)
[12:05:00] [Region Scheduler Thread #1/INFO]: Bot9 joined the game
[12:05:00] [Region Scheduler Thread #1/INFO]: Bot9[/192.168.0.150:59394] logged in with entity id 85 at ([world]-6234.5, 64.0, 3968.5)
[12:05:00] [Region Scheduler Thread #0/INFO]: Bot13 joined the game
[12:05:00] [Region Scheduler Thread #0/INFO]: Bot13[/192.168.0.150:59424] logged in with entity id 87 at ([world]-3397.5, 70.0, -63.5)
[12:05:01] [Region Scheduler Thread #0/INFO]: Bot76 joined the game
[12:05:01] [Region Scheduler Thread #0/INFO]: Bot76[/192.168.0.150:52512] logged in with entity id 88 at ([world]2991.5, 63.0, -9700.5)
[12:05:02] [Region Scheduler Thread #0/INFO]: Bot52 joined the game
[12:05:02] [Region Scheduler Thread #0/INFO]: Bot52[/192.168.0.150:52268] logged in with entity id 86 at ([world]6835.5, 64.0, -4133.5)
[12:05:03] [Region Scheduler Thread #1/INFO]: Bot107 joined the game
[12:05:03] [Region Scheduler Thread #1/INFO]: Bot107[/192.168.0.150:52764] logged in with entity id 91 at ([world]-6765.5, 71.0, 9438.5)
[12:05:04] [Region Scheduler Thread #0/INFO]: Bot118 joined the game
[12:05:04] [Region Scheduler Thread #0/INFO]: Bot118[/192.168.0.150:52868] logged in with entity id 107 at ([world]-6966.5, 93.0, -5799.5)
[12:05:08] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@74b9965e[id=466315ed-f2e1-30e2-9e4c-797d844d733c,name=Bot39,properties={},legacy=false] (/192.168.0.150:59650) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:09] [Region Scheduler Thread #0/INFO]: Bot116 joined the game
[12:05:09] [Region Scheduler Thread #0/INFO]: Bot116[/192.168.0.150:52854] logged in with entity id 131 at ([world]-3692.5, 66.0, 80.5)
[12:05:09] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@207033f0[id=88f0f096-1002-3386-8cc0-5371a30bd66f,name=Bot6,properties={},legacy=false] (/192.168.0.150:59374) lost connection: Timed out
[12:05:09] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@55d9db79[id=9aa06467-c242-3704-9d28-2b9ef52e9d26,name=Bot7,properties={},legacy=false] (/192.168.0.150:59378) lost connection: Timed out
[12:05:09] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@41c8ac22[id=a2aded80-15d4-38c5-8a6f-e532eedf9bde,name=Bot8,properties={},legacy=false] (/192.168.0.150:59386) lost connection: Timed out
[12:05:09] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@20fc6c9b[id=1197a1e1-1f22-395d-ae93-9836bfcec466,name=Bot11,properties={},legacy=false] (/192.168.0.150:59406) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@3032db8d[id=d1b6b006-dda2-300d-82c6-b45b3c57f0d4,name=Bot12,properties={},legacy=false] (/192.168.0.150:59414) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@27880f33[id=8760a068-783d-3a3f-9b76-d3d4e0d6745e,name=Bot15,properties={},legacy=false] (/192.168.0.150:59444) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@55a6b71a[id=3ef33022-674b-3084-a65c-2c10160c0032,name=Bot17,properties={},legacy=false] (/192.168.0.150:59456) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@35987595[id=c8c9bfd6-8b01-3923-952e-74536f6e7be2,name=Bot18,properties={},legacy=false] (/192.168.0.150:59464) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@3080ba95[id=d2bb8e6b-93cc-3625-a4fd-9447af52a436,name=Bot19,properties={},legacy=false] (/192.168.0.150:59472) lost connection: Timed out
[12:05:10] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@758c298b[id=95d3d273-86a4-3189-a5ea-5db62fc595c7,name=Bot20,properties={},legacy=false] (/192.168.0.150:59482) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@76750264[id=b7ccb05e-738a-32e8-9eb0-8b3b7f3b8024,name=Bot21,properties={},legacy=false] (/192.168.0.150:59494) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@43ddb66e[id=c191f968-26fc-3ffb-92b3-1ba1749a805d,name=Bot22,properties={},legacy=false] (/192.168.0.150:59504) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@1f9fc1b[id=213529b1-842e-387b-844b-0ceb4da44fa6,name=Bot24,properties={},legacy=false] (/192.168.0.150:59524) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@6ba4bbf7[id=49569e3b-2b5f-30a7-9e0a-7f0d26686e86,name=Bot26,properties={},legacy=false] (/192.168.0.150:59538) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@41584d62[id=8c8969e2-2f04-313c-9e5d-073809d5ec24,name=Bot27,properties={},legacy=false] (/192.168.0.150:59542) lost connection: Timed out
[12:05:11] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@1cdeac64[id=a3e2f10f-84f1-3a52-b890-4b6fb146dc3b,name=Bot30,properties={},legacy=false] (/192.168.0.150:59568) lost connection: Timed out
[12:05:12] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@79cb31af[id=82621a37-d95f-316b-9d7c-1856fbdfdb69,name=Bot32,properties={},legacy=false] (/192.168.0.150:59588) lost connection: Timed out
[12:05:12] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@3b3f5a48[id=48d28f71-031b-3df7-8c44-8e3d99e68f35,name=Bot35,properties={},legacy=false] (/192.168.0.150:59610) lost connection: Timed out
[12:05:12] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@75a7128b[id=3f91aea2-4986-3101-96ed-1fec5b798cbb,name=Bot36,properties={},legacy=false] (/192.168.0.150:59620) lost connection: Timed out
[12:05:12] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@5db2246e[id=46257f64-e88c-3c3f-98f5-ce5bb158fc41,name=Bot37,properties={},legacy=false] (/192.168.0.150:59636) lost connection: Timed out
[12:05:12] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@2fd86a5c[id=06d39180-b01b-3935-92db-6e077d3f23f7,name=Bot38,properties={},legacy=false] (/192.168.0.150:59644) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@1d2de17f[id=611d3f14-4877-3dbb-8d40-ab6a074c914d,name=Bot14,properties={},legacy=false] (/192.168.0.150:59428) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:13] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@3f352fc3[id=e5ce7fa8-0627-3864-8c4f-aaa03af25094,name=Bot43,properties={},legacy=false] (/192.168.0.150:52196) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@57a5957f[id=a06cb4f4-2263-3936-b61f-600ee5a8ffaf,name=Bot44,properties={},legacy=false] (/192.168.0.150:52198) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@5df0c0e[id=3a874029-86d9-358f-8860-712e1bbc1a0f,name=Bot45,properties={},legacy=false] (/192.168.0.150:52206) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@7fc5d191[id=1ec7eee3-883c-310d-af2a-ed22731121b5,name=Bot47,properties={},legacy=false] (/192.168.0.150:52234) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@f2867e[id=88461141-a850-3588-8b4e-61681c124f5f,name=Bot48,properties={},legacy=false] (/192.168.0.150:52246) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@781c28cf[id=cc99f2bb-8c71-3323-8d3d-290e2a2fc8a8,name=Bot49,properties={},legacy=false] (/192.168.0.150:52248) lost connection: Timed out
[12:05:13] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@75692c78[id=f3c57ce0-d710-3b16-ae15-de6580b9477f,name=Bot50,properties={},legacy=false] (/192.168.0.150:52252) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@48d975a9[id=95dcc0c1-cd91-3d1a-a510-1fbd285c7f32,name=Bot51,properties={},legacy=false] (/192.168.0.150:52264) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@3cda800b[id=6426de2f-03e4-3d37-b801-2ff0cbb07240,name=Bot54,properties={},legacy=false] (/192.168.0.150:52282) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@75f74136[id=791fa2a4-6d1b-326c-9e19-b81c030915ac,name=Bot55,properties={},legacy=false] (/192.168.0.150:52286) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@85ac3c1[id=8a9142b1-b9a0-321d-b519-48b8306ac759,name=Bot57,properties={},legacy=false] (/192.168.0.150:52316) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@5645bfef[id=276481dc-6fc0-3b11-a636-c898ab4fa1e2,name=Bot58,properties={},legacy=false] (/192.168.0.150:52328) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@2982d693[id=c3266127-5720-347b-b955-e92b734fc805,name=Bot59,properties={},legacy=false] (/192.168.0.150:52340) lost connection: Timed out
[12:05:14] [Region Scheduler Thread #1/INFO]: Bot72 joined the game
[12:05:14] [Region Scheduler Thread #1/INFO]: Bot72[/192.168.0.150:52470] logged in with entity id 143 at ([world]9107.5, 63.0, -9090.5)
[12:05:14] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@2a578d69[id=89485a5f-c947-3cb6-ab6f-3fa6b18acf65,name=Bot60,properties={},legacy=false] (/192.168.0.150:52354) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@586e383a[id=0c3758fd-498d-341d-a10f-26d543b642f8,name=Bot61,properties={},legacy=false] (/192.168.0.150:52368) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@373a9fea[id=965f694b-dd01-3238-b32d-db380e1a2540,name=Bot62,properties={},legacy=false] (/192.168.0.150:52384) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@3e97bcde[id=4a2ec1ed-ba52-3ff3-8b0a-0ac430811ee9,name=Bot63,properties={},legacy=false] (/192.168.0.150:52400) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@6de49f55[id=b3e20521-9235-396c-8988-463a63c8a637,name=Bot64,properties={},legacy=false] (/192.168.0.150:52402) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@6ad7c1c8[id=a20d7dda-5128-30de-8c70-834af698d790,name=Bot65,properties={},legacy=false] (/192.168.0.150:52416) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@51013317[id=427aedbc-3c47-36d0-9424-9f03c1fb5324,name=Bot68,properties={},legacy=false] (/192.168.0.150:52424) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@55dd97b1[id=f42725c8-db5b-38f2-8ac7-9c99f51a709a,name=Bot69,properties={},legacy=false] (/192.168.0.150:52436) lost connection: Timed out
[12:05:15] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@6b66793f[id=1fb3078a-de4d-3ee6-b900-354c8365c17a,name=Bot70,properties={},legacy=false] (/192.168.0.150:52452) lost connection: Timed out
[12:05:16] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@430ae5bf[id=c7adf7d1-6c4b-354a-b128-dee7e8c3ae02,name=Bot74,properties={},legacy=false] (/192.168.0.150:52490) lost connection: Timed out
[12:05:16] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@290faade[id=1f99c37f-59c5-33b6-93bf-a3eda5cae819,name=Bot77,properties={},legacy=false] (/192.168.0.150:52522) lost connection: Timed out
[12:05:16] [Region Scheduler Thread #1/INFO]: Bot105 joined the game
[12:05:16] [Region Scheduler Thread #1/INFO]: Bot105[/192.168.0.150:52744] logged in with entity id 148 at ([world]181.5, 69.0, -4630.5)
[12:05:16] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@23e0abdd[id=573a6a59-e87c-3215-85a5-9d3d9f33e686,name=Bot79,properties={},legacy=false] (/192.168.0.150:52526) lost connection: Timed out
[12:05:16] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@5d1cf9de[id=1bc4dbb0-ea23-30e4-87f7-8813f279fdf3,name=Bot80,properties={},legacy=false] (/192.168.0.150:52538) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@7b8dfadf[id=0144ac32-0b17-372e-8d31-9f6343f30b69,name=Bot81,properties={},legacy=false] (/192.168.0.150:52540) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@9cdfffa[id=017cd439-7c52-3267-b10f-1857cc851207,name=Bot82,properties={},legacy=false] (/192.168.0.150:52552) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@7334bf24[id=53a55e58-0072-3e34-8e97-5ed77dc08ee1,name=Bot83,properties={},legacy=false] (/192.168.0.150:52558) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@e0eef05[id=7cefe449-0918-3b44-af80-062ca770f226,name=Bot84,properties={},legacy=false] (/192.168.0.150:52562) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@7c94b8e[id=4ffacc43-f83d-3d4e-9188-b09b8f575e80,name=Bot85,properties={},legacy=false] (/192.168.0.150:52564) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@2548176[id=4e377799-9db3-351e-868a-7ba9e6c36b83,name=Bot86,properties={},legacy=false] (/192.168.0.150:52570) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@59dcb796[id=157b7deb-d01a-3c71-bf23-6aac9f599ee4,name=Bot41,properties={},legacy=false] (/192.168.0.150:59678) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:17] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@49391544[id=4112f704-5c9f-3918-be78-12ff271d4953,name=Bot88,properties={},legacy=false] (/192.168.0.150:52580) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@59212c6f[id=d741d244-713e-3067-8e10-ce9e139abecf,name=Bot87,properties={},legacy=false] (/192.168.0.150:52572) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@4aad002d[id=7b5b5b5b-e130-3814-930e-686864293ddd,name=Bot89,properties={},legacy=false] (/192.168.0.150:52594) lost connection: Timed out
[12:05:17] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@643114d6[id=e357d29c-8ffb-356d-a606-8edd58ef4146,name=Bot90,properties={},legacy=false] (/192.168.0.150:52598) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@481153b9[id=c1792362-fbcc-30af-8d27-ed6ad5809dbc,name=Bot92,properties={},legacy=false] (/192.168.0.150:52622) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@1775a4a[id=f0531ed4-8ec5-3dd9-b794-2f6d887b3907,name=Bot93,properties={},legacy=false] (/192.168.0.150:52638) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@5fc51c35[id=cc068fff-4415-34b9-b129-51d26b82270b,name=Bot94,properties={},legacy=false] (/192.168.0.150:52652) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@14023bb3[id=768d6d90-7c6d-3544-80ce-88e2ccf6c8cd,name=Bot96,properties={},legacy=false] (/192.168.0.150:52670) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@49df86a7[id=620b3ac8-3e21-3c7a-a28b-64db928023f9,name=Bot97,properties={},legacy=false] (/192.168.0.150:52684) lost connection: Timed out
[12:05:18] [Region Scheduler Thread #0/INFO]: Bot113 joined the game
[12:05:18] [Region Scheduler Thread #0/INFO]: Bot113[/192.168.0.150:52830] logged in with entity id 151 at ([world]8584.5, 70.0, -8099.5)
[12:05:19] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@28237d08[id=978e039a-6f13-326b-b242-cfe9792ee0c2,name=Bot100,properties={},legacy=false] (/192.168.0.150:52704) lost connection: Timed out
[12:05:19] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@45fc1044[id=db9f25ab-0b7f-3169-b7f9-a5bee3e23ca3,name=Bot101,properties={},legacy=false] (/192.168.0.150:52706) lost connection: Timed out
[12:05:19] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@3d1069e9[id=1638452a-ea53-3b98-8e82-ec74efe84b7e,name=Bot102,properties={},legacy=false] (/192.168.0.150:52720) lost connection: Timed out
[12:05:19] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@243150de[id=19f168f7-67d2-38df-a88f-4ffc6837baf7,name=Bot104,properties={},legacy=false] (/192.168.0.150:52736) lost connection: Timed out
[12:05:19] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@40735da1[id=947f67f0-d7a6-3928-8501-4aad864c87f9,name=Bot106,properties={},legacy=false] (/192.168.0.150:52758) lost connection: Timed out
[12:05:20] [Region Scheduler Thread #0/INFO]: com.mojang.authlib.GameProfile@383178e4[id=3564e6d3-7586-3b57-9ecb-c35be031c7ef,name=Bot112,properties={},legacy=false] (/192.168.0.150:52814) lost connection: Timed out
[12:05:20] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@195c7273[id=aa917787-6123-32f3-a7fb-0e85a6e3a561,name=Bot114,properties={},legacy=false] (/192.168.0.150:52846) lost connection: Timed out
[12:05:20] [Region Scheduler Thread #1/INFO]: Bot120 joined the game
[12:05:20] [Region Scheduler Thread #1/INFO]: Bot120[/192.168.0.150:52892] logged in with entity id 150 at ([world]-1545.5, 70.0, -1382.5)
[12:05:20] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@47cfc179[id=485e1710-8da2-3e03-82fb-ca236b1b14f8,name=Bot115,properties={},legacy=false] (/192.168.0.150:52852) lost connection: Timed out
[12:05:20] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@55c87844[id=0c9a754b-705b-3aaf-a8a7-d48142e30b27,name=Bot108,properties={},legacy=false] (/192.168.0.150:52780) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:21] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@a2725b3[id=e336ed0a-e928-3109-9458-e4400a9baf0b,name=Bot117,properties={},legacy=false] (/192.168.0.150:52860) lost connection: Timed out
[12:05:22] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@3bd1e89d[id=ec6611b4-92eb-3c72-b833-4f3fdb17ff91,name=Bot119,properties={},legacy=false] (/192.168.0.150:52884) lost connection: Timed out
[12:05:23] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@317f0063[id=65144518-66c8-3344-aff9-4c6ab4f183c2,name=Bot42,properties={},legacy=false] (/192.168.0.150:52188) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:26] [Region Scheduler Thread #1/INFO]: com.mojang.authlib.GameProfile@555a91e7[id=f43be5d3-d050-3438-b399-a16a3e5bd4de,name=Bot95,properties={},legacy=false] (/192.168.0.150:52668) lost connection: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 8
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Awaiting scheduler termination for 60s
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Scheduler halted
[12:05:28] [Region shutdown thread/INFO]: Stopping server
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Halting chunk systems
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world 'world'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Halted chunk system for world 'world'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world 'world_nether'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Halted chunk system for world 'world_nether'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world 'world_the_end'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Halted chunk system for world 'world_the_end'
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Halted chunk systems
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [83, -529] in world 'world'
[12:05:28] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 791 block chunks, 4 entity chunks, 0 poi chunks in world 'world' in 0.17s
[12:05:28] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [564, -552] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 1478 block chunks, 11 entity chunks, 0 poi chunks in world 'world' in 0.21s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [11, -290] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 693 block chunks, 1 entity chunks, 0 poi chunks in world 'world' in 0.09s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-167, 248] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 695 block chunks, 1 entity chunks, 0 poi chunks in world 'world' in 0.09s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-390, 248] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 701 block chunks, 2 entity chunks, 0 poi chunks in world 'world' in 0.13s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-465, -292] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 1476 block chunks, 3 entity chunks, 0 poi chunks in world 'world' in 0.19s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [151, 204] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 849 block chunks, 8 entity chunks, 0 poi chunks in world 'world' in 0.12s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [187, -607] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 734 block chunks, 4 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-572, 185] in world 'world'
[12:05:29] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 779 block chunks, 1 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:29] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [227, -75] in world 'world'
[12:05:30] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 785 block chunks, 2 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:30] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [427, -259] in world 'world'
[12:05:30] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 889 block chunks, 10 entity chunks, 0 poi chunks in world 'world' in 0.12s
[12:05:30] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-422, 589] in world 'world'
[12:05:30] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 710 block chunks, 4 entity chunks, 0 poi chunks in world 'world' in 0.09s
[12:05:30] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-119, 577] in world 'world'
[12:05:30] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 1507 block chunks, 9 entity chunks, 0 poi chunks in world 'world' in 0.21s
[12:05:30] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [116, 584] in world 'world'
[12:05:30] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 552 block chunks, 13 entity chunks, 0 poi chunks in world 'world' in 0.12s
[12:05:30] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-263, 307] in world 'world'
[12:05:31] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 3747 block chunks, 26 entity chunks, 0 poi chunks in world 'world' in 0.49s
[12:05:31] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-418, -553] in world 'world'
[12:05:31] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 783 block chunks, 2 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:31] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [356, 159] in world 'world'
[12:05:31] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 2976 block chunks, 18 entity chunks, 0 poi chunks in world 'world' in 0.43s
[12:05:31] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [512, 232] in world 'world'
[12:05:31] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 779 block chunks, 1 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:31] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-60, -151] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 2241 block chunks, 15 entity chunks, 0 poi chunks in world 'world' in 0.30s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [185, -339] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'world' in 0.00s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [428, 410] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 814 block chunks, 7 entity chunks, 0 poi chunks in world 'world' in 0.12s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [125, -100] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 693 block chunks, 1 entity chunks, 0 poi chunks in world 'world' in 0.09s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-427, -169] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 701 block chunks, 2 entity chunks, 0 poi chunks in world 'world' in 0.09s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [433, 547] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 791 block chunks, 4 entity chunks, 0 poi chunks in world 'world' in 0.10s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [-198, -11] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 2040 block chunks, 6 entity chunks, 1 poi chunks in world 'world' in 0.26s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [403, -156] in world 'world'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'world' in 0.00s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [0, 0] in world 'world_nether'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'world_nether' in 0.00s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving chunks around region around chunk [0, 0] in world 'world_the_end'
[12:05:32] [Region shutdown thread/INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'world_the_end' in 0.00s
[12:05:32] [Region shutdown thread/INFO]: [RegionShutdownThread] Saving players
[12:05:32] [Region shutdown thread/INFO]: Flushing Chunk IO
[12:05:32] [Region shutdown thread/INFO]: Closing Thread Pool
[12:05:32] [Region shutdown thread/INFO]: Closing Server

Villagers cannot go through nether portals

Expected behavior

Villagers should be able to travel through nether portals, like other mobs.

Observed/Actual behavior

When I villager travel through a nether portal, it disappear and this error is throw:

[01:47:02 ERROR]: Entity threw exception at world:440.64865656939077,69.0,-206.24489705607485
net.minecraft.ReportedException: Loading entity NBT
        at net.minecraft.world.entity.Entity.load(Entity.java:2502) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.restoreFrom(Entity.java:3408) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.transformForAsyncTeleport(Entity.java:3696) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.portalToAsync(Entity.java:4108) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.netherPortalLogicAsync(Entity.java:3872) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.tryNetherPortal(Entity.java:3838) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.world.entity.Entity.doPortalLogic(Entity.java:3801) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.server.level.ServerLevel.tickNonPassenger(ServerLevel.java:1322) ~[?:?]
        at net.minecraft.world.level.Level.guardEntityTick(Level.java:965) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$8(ServerLevel.java:794) ~[?:?]
        at io.papermc.paper.threadedregions.RegionizedWorldData.forEachTickingEntity(RegionizedWorldData.java:519) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:773) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1697) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1542) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:316) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:379) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:516) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        at java.lang.Thread.run(Thread.java:1589) ~[?:?]
Caused by: java.lang.IllegalStateException: World mismatch: expected world_nether but got world
        at net.minecraft.world.level.Level.getCurrentWorldData(Level.java:283) ~[?:?]
        at net.minecraft.world.level.Level.getGameTime(Level.java:1286) ~[?:?]
        at net.minecraft.world.entity.ai.Brain.stopAll(Brain.java:415) ~[?:?]
        at net.minecraft.world.entity.npc.Villager.refreshBrain(Villager.java:177) ~[?:?]
        at net.minecraft.world.entity.npc.Villager.readAdditionalSaveData(Villager.java:585) ~[?:?]
        at net.minecraft.world.entity.Entity.load(Entity.java:2400) ~[folia-1.19.4.jar:git-Folia-"ed7a5c5"]
        ... 18 more

Steps/models to reproduce

  1. Build a nether portal
  2. Push a villager inside the nether portal.
  3. The villager disappears and an error is throw.

Plugin and Datapack List

> plugins [01:48:50 INFO]: Server Plugins (0):

Folia version

> version
[01:49:18 INFO]: Checking version, please wait...
[01:49:19 INFO]: This server is running Folia version git-Folia-"ed7a5c5" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: ed7a5c5)
You are running the latest version

Other

No response

timings is not executable

timings on
[09:27:48 INFO]: Enabled Timings & Reset
[09:27:48 INFO]: Timings Reset
timings paste
[09:27:51 INFO]: Please enable timings by typing /timings on

!!!Server compilation error!!!Not behavior error!!!

Expected behavior

I encountered a problem while compiling, but I did not find the free issue publishing entry in the feedback screen, so the following question is about compilation errors.

I followed paperMC's build guidance:
//
1.To compile Paper, you need JDK 17 and an internet connection.
2.Clone this repo, run ./gradlew applyPatches, then ./gradlew createReobfBundlerJar from your terminal. You can find the
compiled jar in the project root's build/libs directory.
3.To get a full list of tasks, run ./gradlew tasks.
//

Observed/Actual behavior

//
1.To compile Paper, you need JDK 17 and an internet connection.
2.Clone this repo, run ./gradlew applyPatches, then ./gradlew createReobfBundlerJar from your terminal. You can find the
compiled jar in the project root's build/libs directory.
3.To get a full list of tasks, run ./gradlew tasks.
//

Steps/models to reproduce

I tried to compile this project and here are the steps I used:
(1)I try to git this porject and gradlew.bat build
Then I found a problem. The compiled Jar file was an empty shell and could not be used.
I searched the encyclopedia for a long time and there was something wrong with my steps.
So here's how I did it the second time:
(1)git this project
(2)build tasks
Then I follow the guidance:
//
1.To compile Paper, you need JDK 17 and an internet connection.
2.Clone this repo, run ./gradlew applyPatches, then ./gradlew createReobfBundlerJar from your terminal. You can find the
compiled jar in the project root's build/libs directory.
3.To get a full list of tasks, run ./gradlew tasks.
//
(3)gradlew.bat applyPatches
An error occurred when git reached 44%.
The specific error information is listed below.

Plugin and Datapack List

C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia>gradlew.bat applyPatches

Task :paper:patchCraftBukkit FAILED
Task :getPaperUpstreamData FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':paper:patchCraftBukkit'.

io.papermc.paperweight.PaperweightException: Command finished with 128 exit code: git -c commit.gpgsign=false -c core.safecrlf=false clone --no-hardlinks C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\work\CraftBukkit C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper.gradle\caches\paperweight\taskCache\patchCraftBukkit.repo

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

BUILD FAILED in 4m 13s
2 actionable tasks: 2 executed

Folia version

This is the debug message:
//////////////////////////////
C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia>gradlew.bat applyPatches --debug -i
Initialized native services in: C:\Users\Ayaka.gradle\native
Initialized jansi services in: C:\Users\Ayaka.gradle\native
Received JVM installation metadata from 'C:\Program Files\BellSoft\LibericaJDK-17': {JAVA_HOME=C:\Program Files\BellSoft\LibericaJDK-17, JAVA_VERSION=17.0.5, JAVA_VENDOR=BellSoft, RUNTIME_NAME=OpenJDK Runtime Environment, RUNTIME_VERSION=17.0.5+8-LTS, VM_NAME=OpenJDK 64-Bit Server VM, VM_VERSION=17.0.5+8-LTS, VM_VENDOR=BellSoft, OS_ARCH=amd64}
The client will now receive all logging from the daemon (pid: 24348). The daemon log file: C:\Users\Ayaka.gradle\daemon\8.0.2\daemon-24348.out.log
Starting 14th build in daemon [uptime: 51 mins 35.186 secs, performance: 100%, GC rate: 0.00/s, heap usage: 0% of 512 MiB, non-heap usage: 36% of 384 MiB]
Using 16 worker leases.
Watching the file system is configured to be disabled
File system watching is inactive
Starting Build
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Settings evaluated using settings file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia\settings.gradle.kts'.
Using local directory build cache for the root build (location = C:\Users\Ayaka.gradle\caches\build-cache-1, removeUnusedEntriesAfter = 7 days).
Projects loaded. Root project using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia\build.gradle.kts'.
Included projects: [root project 'folia', project ':folia-api', project ':folia-server']

Configure project :
Evaluating root project 'folia' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia\build.gradle.kts'.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for Kotlin DSL accessors for root project 'folia' is a1f6baf722c0f8281fa5999b184255b4
Skipping Kotlin DSL accessors for root project 'folia' as it is up-to-date.

Configure project :folia-api
Evaluating project ':folia-api' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia\Folia-API\build.gradle'.

Configure project :folia-server
Evaluating project ':folia-server' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia\Folia-Server\build.gradle'.
All projects evaluated.
Task name matched 'applyPatches'
Selected primary task 'applyPatches' from project :
Tasks to be executed: [task ':clonePaperRepo', task ':getPaperUpstreamData', task ':applyApiPatches', task ':applyServerPatches', task ':applyPatches']
Tasks that were excluded: []
Resolve mutations for :clonePaperRepo (Thread[Execution worker,5,main]) started.
:clonePaperRepo (Thread[Execution worker,5,main]) started.

Task :clonePaperRepo
Caching disabled for task ':clonePaperRepo' because:
Caching has not been enabled for the task
Task ':clonePaperRepo' is not up-to-date because:
Task state is not tracked.
Resolve mutations for :getPaperUpstreamData (Thread[Execution worker,5,main]) started.
:getPaperUpstreamData (Thread[Execution worker,5,main]) started.

Configure project :paper
Evaluating project ':paper' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\build.gradle.kts'.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration2 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration2 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Using local directory build cache for build ':paper' (location = C:\Users\Ayaka.gradle\caches\build-cache-1, removeUnusedEntriesAfter = 7 days).
The configuration :paper:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for Kotlin DSL accessors for project ':paper' is b4948b41110e407a1022c279a058d8e3
Skipping Kotlin DSL accessors for project ':paper' as it is up-to-date.

Configure project :paper:paper-api
Evaluating project ':paper:paper-api' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\Paper-API\build.gradle.kts'.
The configuration :paper:paper-api:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paper-api:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:paper-api:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paper-api:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for Kotlin DSL accessors for project ':paper:paper-api' is 3c377051dc897d53caa0bed38926dca8
Skipping Kotlin DSL accessors for project ':paper:paper-api' as it is up-to-date.

Configure project :paper:paper-mojangapi
Evaluating project ':paper:paper-mojangapi' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\Paper-MojangAPI\build.gradle.kts'.
The configuration :paper:paper-mojangapi:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paper-mojangapi:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:paper-mojangapi:classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paper-mojangapi:classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for Kotlin DSL accessors for project ':paper:paper-mojangapi' is 3c377051dc897d53caa0bed38926dca8
Skipping Kotlin DSL accessors for project ':paper:paper-mojangapi' as it is up-to-date.

Configure project :paper:paper-server
Evaluating project ':paper:paper-server' using build file 'C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\Paper-Server\build.gradle'.
Resolve mutations for :paper:initSubmodules (Thread[Execution worker,5,main]) started.
:paper:initSubmodules (Thread[Execution worker,5,main]) started.

Task :paper:initSubmodules
Caching disabled for task ':paper:initSubmodules' because:
Caching has not been enabled for the task
Task ':paper:initSubmodules' is not up-to-date because:
Task state is not tracked.
Resolve mutations for :paper:patchSpigotApiPatches (Thread[Execution worker,5,main]) started.
:paper:patchSpigotApiPatches (Thread[Execution worker,5,main]) started.

Task :paper:patchSpigotApiPatches UP-TO-DATE
Build cache key for task ':paper:patchSpigotApiPatches' is dfc2f696256a173c0d55cc0058d53b66
Skipping task ':paper:patchSpigotApiPatches' as it is up-to-date.
Resolve mutations for :paper:patchSpigotApi (Thread[Execution worker,5,main]) started.
:paper:patchSpigotApi (Thread[Execution worker Thread 8,5,main]) started.

Task :paper:patchSpigotApi UP-TO-DATE
Caching disabled for task ':paper:patchSpigotApi' because:
Caching has not been enabled for the task
Skipping task ':paper:patchSpigotApi' as it is up-to-date.
Resolve mutations for :paper:applyApiPatches (Thread[Execution worker Thread 8,5,main]) started.

Task :paper:applyApiPatches UP-TO-DATE
Caching disabled for task ':paper:applyApiPatches' because:
Caching has not been enabled for the task
Skipping task ':paper:applyApiPatches' as it is up-to-date.

Task :getPaperUpstreamData
Caching disabled for task ':getPaperUpstreamData' because:
Caching has not been enabled for the task
Task ':getPaperUpstreamData' is not up-to-date because:
Task state is not tracked.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration detachedConfiguration1 is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration detachedConfiguration1 is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration classpath is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration classpath is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Task name matched 'prepareForDownstream'
Selected primary task 'prepareForDownstream' from project :
The configuration :paper:decompiler is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:decompiler is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:mainSourceElements is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:paperclip is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paperclip is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:paramMappings is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paramMappings is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:remapper is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:remapper is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:spigotDecompiler is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:spigotDecompiler is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:testResultsElementsForTest is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
The configuration :paper:paramMappings is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:paramMappings is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
:paper:applyApiPatches (Thread[included builds,5,main]) started.
Resolve mutations for :paper:downloadMcManifest (Thread[included builds,5,main]) started.
:paper:downloadMcManifest (Thread[included builds,5,main]) started.

Task :paper:downloadMcManifest
Caching disabled for task ':paper:downloadMcManifest' because:
Caching has not been enabled for the task
Task ':paper:downloadMcManifest' is not up-to-date because:
Task state is not tracked.

Task :paper:downloadMcVersionManifest UP-TO-DATE
Caching disabled for task ':paper:downloadMcVersionManifest' because:
Caching has not been enabled for the task
Skipping task ':paper:downloadMcVersionManifest' as it is up-to-date.

Task :paper:downloadServerJar UP-TO-DATE
Caching disabled for task ':paper:downloadServerJar' because:
Caching has not been enabled for the task
Skipping task ':paper:downloadServerJar' as it is up-to-date.

Task :paper:extractFromBundler UP-TO-DATE
Build cache key for task ':paper:extractFromBundler' is 70b2db541c3ab2815d42632a6438302c
Skipping task ':paper:extractFromBundler' as it is up-to-date.

Task :paper:addAdditionalSpigotMappings UP-TO-DATE
Build cache key for task ':paper:addAdditionalSpigotMappings' is 10e20ab27ab34d664db37b1162bf2e3a
Skipping task ':paper:addAdditionalSpigotMappings' as it is up-to-date.

Task :paper:downloadMappings UP-TO-DATE
Caching disabled for task ':paper:downloadMappings' because:
Caching has not been enabled for the task
Skipping task ':paper:downloadMappings' as it is up-to-date.

Task :paper:filterVanillaJar UP-TO-DATE
Build cache key for task ':paper:filterVanillaJar' is 941f7fc1f25138f46576e3b01f3e9ff4
Skipping task ':paper:filterVanillaJar' as it is up-to-date.

Task :paper:generateMappings UP-TO-DATE
Build cache key for task ':paper:generateMappings' is c66ee2be0875d8b6747bad622ffc77c3
Skipping task ':paper:generateMappings' as it is up-to-date.

Task :paper:generateSpigotMappings UP-TO-DATE
Build cache key for task ':paper:generateSpigotMappings' is bf3692d34da1c294c2e72801d26087f0
Skipping task ':paper:generateSpigotMappings' as it is up-to-date.
:paper:spigotRemapJar (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:spigotRemapJar UP-TO-DATE
Build cache key for task ':paper:spigotRemapJar' is 71b5435e86d3f824009a43ffe27d8222
Skipping task ':paper:spigotRemapJar' as it is up-to-date.
Resolve mutations for :paper:cleanupMappings (Thread[Execution worker Thread 13,5,main]) started.
:paper:cleanupMappings (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:cleanupMappings UP-TO-DATE
Build cache key for task ':paper:cleanupMappings' is b4d1e29bd4d359116a53f8f19df15085
Skipping task ':paper:cleanupMappings' as it is up-to-date.
Resolve mutations for :paper:patchMappings (Thread[Execution worker Thread 13,5,main]) started.
:paper:patchMappings (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:patchMappings UP-TO-DATE
Build cache key for task ':paper:patchMappings' is 2d2028f5c732cff79fb0a8ff86e07167
Skipping task ':paper:patchMappings' as it is up-to-date.
Resolve mutations for :paper:cleanupSourceMappings (Thread[Execution worker Thread 13,5,main]) started.
:paper:cleanupSourceMappings (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:cleanupSourceMappings UP-TO-DATE
Build cache key for task ':paper:cleanupSourceMappings' is 178b8889d0eadb1d06834826ad59fc60
Skipping task ':paper:cleanupSourceMappings' as it is up-to-date.
Resolve mutations for :paper:remapJar (Thread[Execution worker Thread 13,5,main]) started.
:paper:remapJar (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:remapJar UP-TO-DATE
The configuration :paper:remapper is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:remapper is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for task ':paper:remapJar' is d2a019bd3076ceaeb3d9592644305548
Skipping task ':paper:remapJar' as it is up-to-date.
Resolve mutations for :paper:fixJar (Thread[Execution worker Thread 13,5,main]) started.
:paper:fixJar (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:fixJar UP-TO-DATE
Build cache key for task ':paper:fixJar' is 59163ea9a4ddcfbdd54cd73f6641809c
Skipping task ':paper:fixJar' as it is up-to-date.
Resolve mutations for :paper:patchCraftBukkitPatches (Thread[Execution worker Thread 13,5,main]) started.
:paper:patchCraftBukkitPatches (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:patchCraftBukkitPatches UP-TO-DATE
Build cache key for task ':paper:patchCraftBukkitPatches' is d9761f01d8f60c739d5f468adc44e586
Skipping task ':paper:patchCraftBukkitPatches' as it is up-to-date.
Resolve mutations for :paper:filterSpigotExcludes (Thread[Execution worker Thread 13,5,main]) started.
:paper:filterSpigotExcludes (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:filterSpigotExcludes UP-TO-DATE
Build cache key for task ':paper:filterSpigotExcludes' is 9fe4f1280e3d7423b93e017860635ae8
Skipping task ':paper:filterSpigotExcludes' as it is up-to-date.
Resolve mutations for :paper:spigotDecompileJar (Thread[Execution worker Thread 13,5,main]) started.
:paper:spigotDecompileJar (Thread[Execution worker Thread 13,5,main]) started.

Task :paper:spigotDecompileJar UP-TO-DATE
The configuration :paper:spigotDecompiler is both resolvable and consumable. This is considered a legacy configuration and it will eventually only be possible to be one of these.
The configuration :paper:spigotDecompiler is both consumable and declarable. This combination is incorrect, only one of these flags should be set.
Build cache key for task ':paper:spigotDecompileJar' is 3409a5a97306284a8c9f39bf2efe5023
Skipping task ':paper:spigotDecompileJar' as it is up-to-date.
Resolve mutations for :paper:patchCraftBukkit (Thread[Execution worker Thread 13,5,main]) started.
:paper:patchCraftBukkit (Thread[Execution worker Thread 13,5,main]) started.

Task :getPaperUpstreamData
Resolve mutations for :paper:downloadMcVersionManifest (Thread[included builds,5,main]) started.
:paper:downloadMcVersionManifest (Thread[included builds,5,main]) started.
Resolve mutations for :paper:downloadServerJar (Thread[included builds,5,main]) started.
:paper:downloadServerJar (Thread[included builds,5,main]) started.
Resolve mutations for :paper:extractFromBundler (Thread[included builds,5,main]) started.
:paper:extractFromBundler (Thread[included builds,5,main]) started.
Resolve mutations for :paper:addAdditionalSpigotMappings (Thread[included builds,5,main]) started.
:paper:addAdditionalSpigotMappings (Thread[included builds,5,main]) started.
Resolve mutations for :paper:downloadMappings (Thread[included builds,5,main]) started.
:paper:downloadMappings (Thread[included builds,5,main]) started.
Resolve mutations for :paper:filterVanillaJar (Thread[included builds,5,main]) started.
:paper:filterVanillaJar (Thread[included builds,5,main]) started.
Resolve mutations for :paper:generateMappings (Thread[included builds,5,main]) started.
:paper:generateMappings (Thread[included builds,5,main]) started.
Resolve mutations for :paper:generateSpigotMappings (Thread[included builds,5,main]) started.
:paper:generateSpigotMappings (Thread[included builds,5,main]) started.
Resolve mutations for :paper:spigotRemapJar (Thread[included builds,5,main]) started.

Task :paper:patchCraftBukkit FAILED
Caching disabled for task ':paper:patchCraftBukkit' because:
Caching has not been enabled for the task
Task ':paper:patchCraftBukkit' is not up-to-date because:
Task has failed previously.

Task :getPaperUpstreamData FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':paper:patchCraftBukkit'.

io.papermc.paperweight.PaperweightException: Command finished with 128 exit code: git -c commit.gpgsign=false -c core.safecrlf=false clone --no-hardlinks C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper\work\CraftBukkit C:\File\Desktop\Folia\Folia-bulid-2023.4.23\Folia.gradle\caches\paperweight\upstreams\paper.gradle\caches\paperweight\taskCache\patchCraftBukkit.repo

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --debug option to get more log output.
Run with --scan to get full insights.

BUILD FAILED in 8s
2 actionable tasks: 2 executed

Other

I try to use this command.
gradlew.bat cleanBuildCache

I'm sure it's not my Internet.

Spawning multiple Nether Portals before Player teleports

Expected behavior

  • Build a new Nether Portal
  • Throw X Items through it
  • Step into Portal
    -> 1 Portal with dropped items

Observed/Actual behavior

-> Many new Portals, one for each item

Steps/models to reproduce

  • Go to Nether
  • Build a new portal, in an Area where no other portals are
  • Activate portal
  • Throw X items through the portal
  • After X Items use Portal with player
    -> X Target Portals are generated when generating new Chunks

Plugin and Datapack List

Plugins: BlueMap-3.13-folia
Datapacks: none

Folia version

git-Folia-"41c5548" (MC: 1.19.4)

Other

Maybe an Exploit for Obsidian?

"java.lang.IllegalStateException: Already sent chunk [x, y] to player ..." - Double sending chunk to a player

Stack trace

[13:50:12 ERROR]: [io.papermc.paper.threadedregions.TickRegionScheduler] Region #19793 centered at chunk [-25, 2] in world 'world' failed to tick:
java.lang.IllegalStateException: Already sent chunk [8, 0] to player EntityPlayer['BEBRA_B_POPE'/2383115, uuid='10d4f404-b483-3340-91f5-fe6f1d600cb7', l='ServerLevel[world]', x=-2.06, y=71.00, z=9.72, cpos=[-1, 0], tl=71871, v=true](BEBRA_B_POPE at -2.06269412992101,71.00133597911214,9.717645408324085)
        at net.minecraft.server.level.ChunkHolder.addPlayer(ChunkHolder.java:136) ~[?:?]
        at net.minecraft.server.level.ChunkMap.updateChunkTracking(ChunkMap.java:733) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader$PlayerChunkLoaderData.sendChunk(RegionizedPlayerChunkLoader.java:491) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader$PlayerChunkLoaderData.midTickUpdate(RegionizedPlayerChunkLoader.java:885) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader.tickMidTick(RegionizedPlayerChunkLoader.java:247) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.threadedregions.RegionizedTaskQueue$RegionTaskQueueData.drainTasks(RegionizedTaskQueue.java:232) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1523) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:316) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar:git-Folia-"d34fb87"]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]

Plugin and Datapack List

no plugins

Actions to reproduce (if known)

No response

Folia version

version
[16:13:15 INFO]: This server is running Folia version git-Folia-"d34fb87" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: d34fb87)
You are 7 version(s) behind
Download the new version at: https://papermc.io/downloads
Previous version: git-Paper-499 (MC: 1.19.4)

Other

No response

Possible bug in teleportAsync

Stack trace

java.lang.IllegalStateException: Player is already removed from player chunk loader
      at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader.removePlayer(RegionizedPlayerChunkLoader.java:158) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ChunkMap.removePlayerFromDistanceMaps(ChunkMap.java:213) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ChunkMap.updatePlayerStatus(ChunkMap.java:1016) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ChunkMap.removeEntity(ChunkMap.java:1103) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerChunkCache.removeEntity(ServerChunkCache.java:871) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerLevel$EntityCallbacks.onTrackingEnd(ServerLevel.java:2837) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerLevel$EntityCallbacks.onTrackingEnd(ServerLevel.java:2715) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.chunk.system.entity.EntityLookup.entityStatusChange(EntityLookup.java:288) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.chunk.system.entity.EntityLookup$EntityCallback.onRemove(EntityLookup.java:848) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.world.entity.Entity.setRemoved(Entity.java:5328) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.world.entity.Entity.remove(Entity.java:693) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.world.entity.LivingEntity.remove(LivingEntity.java:745) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.world.entity.player.Player.remove(Player.java:1496) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerLevel.removePlayerImmediately(ServerLevel.java:1701) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerPlayer.transformForAsyncTeleport(ServerPlayer.java:1396) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.level.ServerPlayer.transformForAsyncTeleport(ServerPlayer.java:188) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.world.entity.Entity.teleportAsync(Entity.java:3780) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at org.bukkit.craftbukkit.v1_19_R3.entity.CraftEntity.lambda$teleportAsync$1(CraftEntity.java:1336) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at org.bukkit.craftbukkit.v1_19_R3.entity.CraftEntity.teleportAsync(CraftEntity.java:1351) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at org.bukkit.entity.Entity.teleportAsync(Entity.java:199) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
      ...
      ...
      ...
      at fr.xephi.authme.listener.PlayerListener.onPlayerJoin(PlayerListener.java:184) ~[AuthMe-5.6.0-SNAPSHOT.jar:?]
      at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor51.execute(Unknown Source) ~[?:?]
      at org.bukkit.plugin.EventExecutor$2.execute(EventExecutor.java:77) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
      at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:77) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:git-Folia-"7072994"]
      at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
      at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:54) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:126) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:615) ~[folia-api-1.19.4-R0.1-SNAPSHOT.jar:?]
      at net.minecraft.server.players.PlayerList.placeNewPlayer(PlayerList.java:404) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.network.ServerLoginPacketListenerImpl.lambda$handleAcceptedLogin$1(ServerLoginPacketListenerImpl.java:204) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.threadedregions.RegionizedTaskQueue$PrioritisedQueue$ChunkBasedPriorityTask.executeInternal(RegionizedTaskQueue.java:489) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.threadedregions.RegionizedTaskQueue$PrioritisedQueue.executeTask(RegionizedTaskQueue.java:419) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.threadedregions.RegionizedTaskQueue$RegionTaskQueueData.drainTasks(RegionizedTaskQueue.java:248) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1523) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:316) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:383) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar:git-Folia-"7072994"]
      at java.lang.Thread.run(Thread.java:1589) ~[?:?]

Plugin and Datapack List

AuthMeReloaded

Actions to reproduce (if known)

  1. Call Bukkit.isOwnedByCurrentRegion(entity)
  2. If it returns true, call .teleportAsync(entity, loc)

Folia version

Latest commit, 7072994

Other

teleportAsync() documentation tells that it should return a future with the result of the teleport, it shouldn't throw an exception if the teleport is not possible.

Redstone components freezing

Expected behavior

Vanilla redstone.

Observed/Actual behavior

Here is everything AFAIK:

  • The main issue is redstone that freeze sometimes on chunk loading.
  • Blocks can be deleted, but if you replace them, the redstone keep freezing.
  • It seems to affect only redstone "modules" (i.e every redstone component except redstone dust)
  • This bug doesn't appear if the chunk is already loaded. (i.e you'll never see live redstone freezing)
  • If you delete/replace the block, it doesn't solve anything, placed blocks are freezed.
  • Affected blocks don't react to redstone signals
  • Loading the region file on Paper don't solve this issue.
  • If you wait few minutes (30-60 mins) it run fine again.

Steps/models to reproduce

I cannot reproduce this bug.
However, here is an affected region file

1- Download the region file
2- Put the file in world/region
3- Run Folia (or Paper)
4- Teleport: /tp 420 64 -7286
5- Redstone repeaters aren't working behind Flush button
6- Observer clocks aren't working

This region file was saved with Folia.

The Video (Affected region file opened with a test Paper instance)

Plugin and Datapack List

No plugins/datapacks.

Folia version

> version
[04:16:48 INFO]: Checking version, please wait...
[04:16:49 INFO]: This server is running Folia version git-Folia-"33d2aa8" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 33d2aa8)
You are running the latest version
Previous version: git-Folia-"7072994" (MC: 1.19.4)

Other

Since this can be loaded in Paper, maybe this is related to the way that Folia saves redstone game time / redstone state / redstone ticks?

Lodestone Crashes If Across Regions

Stack trace

[21:55:52] [Region Scheduler Thread #2/ERROR]: Thread Region Scheduler Thread #2 failed main thread check: Accessing poi chunk off-main
java.lang.Throwable: null
	at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:71) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at net.minecraft.world.entity.ai.village.poi.PoiManager.d(PoiManager.java:281) ~[?:?]
	at net.minecraft.world.entity.ai.village.poi.PoiManager.exists(PoiManager.java:199) ~[?:?]
	at net.minecraft.world.entity.ai.village.poi.PoiManager.existsAtPosition(PoiManager.java:82) ~[?:?]
	at net.minecraft.world.item.CompassItem.inventoryTick(CompassItem.java:80) ~[?:?]
	at net.minecraft.world.item.ItemStack.inventoryTick(ItemStack.java:768) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at net.minecraft.world.entity.player.Inventory.tick(Inventory.java:328) ~[?:?]
	at net.minecraft.world.entity.player.Player.aiStep(Player.java:565) ~[?:?]
	at net.minecraft.world.entity.LivingEntity.tick(LivingEntity.java:2978) ~[?:?]
	at net.minecraft.world.entity.player.Player.tick(Player.java:275) ~[?:?]
	at net.minecraft.server.level.ServerPlayer.doTick(ServerPlayer.java:796) ~[?:?]
	at net.minecraft.server.network.ServerGamePacketListenerImpl.tick(ServerGamePacketListenerImpl.java:388) ~[?:?]
	at net.minecraft.network.Connection.tick(Connection.java:624) ~[?:?]
	at io.papermc.paper.threadedregions.RegionizedWorldData.tickConnections(RegionizedWorldData.java:480) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1537) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:360) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]

Plugin and Datapack List

No Plugins

Actions to reproduce (if known)

  • Place a lodestone in 1 region
  • Create a lodestone compass with it
  • Teleport to a different region
  • Switch hotbar item to lodestone compass

Folia version

This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version
Previous version: git-Folia-"17a3236" (MC: 1.19.4)

Other

No response

Foxes duplicate sweet berries

Expected behavior

Foxes should not duplicate sweet berries

Here is a video that shows how it works on paper

Observed/Actual behavior

Foxes duplicate sweet berries.

Here is a video that shows the bug

Steps/models to reproduce

Putting foxes in an enclosure with sweet berries, the duplication happens almost systematically

Plugin and Datapack List

The server does not use datapacks or plugins

Folia version

This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)

/enchant giving mixed messages

Expected behavior

When trying to /enchant a item that doesn't support enchants to not say "Applied enchantment .... to ...'s item"

No enchantment is added as expected just a message

Steps/models to reproduce

  1. Give yourself an item that doesn't support enchantments such as oak_log
  2. do /enchant @s minecraft:unbreaking 1
  3. 2 messages, 1 which says the enchantment got applied another one that says "Oak Log cannot support that enchantment"

Folia version

This server is running Folia version git-Folia-"5b74945" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 5b74945)

Other

image

Exception ticking world

Stack trace

[20:13:02 ERROR]: [io.papermc.paper.threadedregions.TickRegionScheduler] Region #25599 centered at chunk [6237, -5615] in world 'world' fail
ed to tick:
net.minecraft.ReportedException: Exception ticking world
at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1716) ~[folia-1.19.4.jar:git-Folia-"47105ea"]
at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[folia-1.19.4.jar:git-Folia-"47105ea"]
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1542) ~[folia-1.19.4.jar:git-Folia-"47105ea"]
at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:360) ~[folia-1.19.4.jar:git-Fol
ia-"47105ea"]
at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385) ~[folia-1.19.4.ja
r:git-Folia-"47105ea"]
at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar
:git-Folia-"47105ea"]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.lang.IllegalStateException: Already sent chunk [6260, -5622] in world 'world' to player EntityPlayer['not_LOSER'/3793434, uu
id='9a609d35-ca6a-3a53-be21-3dd6d8cb3767', l='ServerLevel[world]', x=100167.27, y=63.80, z=-89813.95, cpos=[6260, -5614], tl=2457554, v=true
](not_LOSER at 100167.26906950824,63.796735600668704,-89813.94716536891)
at net.minecraft.server.level.ChunkHolder.addPlayer(ChunkHolder.java:136) ~[?:?]
at net.minecraft.server.level.ChunkTracker.updateChunkTracking(ChunkTracker.java:735) ~[?:?]
at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader$PlayerChunkLoaderData.sendChunk(RegionizedPlayerChunkLoader.java:485) ~
[folia-1.19.4.jar:git-Folia-"47105ea"]
at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader$PlayerChunkLoaderData.updateQueues(RegionizedPlayerChunkLoader.java:860
) ~[folia-1.19.4.jar:git-Folia-"47105ea"]
at io.papermc.paper.chunk.system.RegionizedPlayerChunkLoader.tick(RegionizedPlayerChunkLoader.java:244) ~[folia-1.19.4.jar:git-Folia
-"47105ea"]
at net.minecraft.server.level.ServerChunkCache.tick(ServerChunkCache.java:598) ~[?:?]
at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:739) ~[?:?]
at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1697) ~[folia-1.19.4.jar:git-Folia-"47105ea"]
... 6 more
[20:13:02 INFO]: [RegionShutdownThread] Awaiting scheduler termination for 60s
[20:13:02 INFO]: [RegionShutdownThread] Scheduler halted

Plugin and Datapack List

[20:43:36 INFO]: Server Plugins (32):
[20:43:36 INFO]: Bukkit Plugins:
[20:43:36 INFO]: - ArmorStandEditor, BBeeChecker, BetterRTP, BlueMap, ChestShop, Chunky, CoreProtect, DeluxeMenus, EditableSigns, Essential
s
[20:43:36 INFO]: EssentialsChat, EssentialsGeoIP, EssentialsProtect, EssentialsSpawn, FallingSnow, FastAsyncWorldEdit, FoliaFlow, FramedIma
ge, GSit, InvSeePlusPlus
[20:43:36 INFO]: InvSeePlusPlus_Clear, InvSeePlusPlus_Give, LiteSignIn, LuckPerms, PlaceholderAPI, PosCommands, SurvivalPlots, UniHologram,
Vault, ViaBackwards
[20:43:36 INFO]: ViaRewind, ViaVersion

Actions to reproduce (if known)

No response

Folia version

build of latest folia(1.19.4)

Other

The more players there are,the higher the probability of this problem occuring.

Save-all doesn't work

Expected behavior

save-all saves all chunks and player data in Paper.

Observed/Actual behavior

> version
[08:23:23 INFO]: Checking version, please wait...
[08:23:24 INFO]: This server is running Folia version git-Folia-"105f6d6" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 105f6d6)
You are running the latest version
> save-all
[08:23:30 INFO]: Unknown command. Type "/help" for help.

Steps/models to reproduce

Type save-all in the console.

Plugin and Datapack List

None

Folia version

[08:23:24 INFO]: This server is running Folia version git-Folia-"105f6d6" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 105f6d6)
You are running the latest version

Other

No response

Loading invalid chunk crashes server instead of just throwing an exception

Loading Chunks with invalid data, for example heightmaps that don't match the world height, crashes a Folia server. On Paper, an exception is thrown and logged, but the server keeps running.

Steps to reproduce:

  1. Download the world: world.zip (Datapack is included).
  2. Run Folia with the world. Everything should work normally. The world height should be 512.
  3. Stop the server and delete the world_height.zip datapack. The world height is now vanilla.
  4. Start the Folia server and try to join it. The server will instantly stop with a Chunk system crash propagated from unrecoverableChunkSystemFailure error. https://pastes.dev/8xcPKOkrVT
  5. Now do the same with a Paper server. The following errors will be thrown, but the server will keep running: https://pastes.dev/POXbmGPMRf

Full Folia log: https://pastes.dev/z9x1hQM8Ax (relevant part should be above)

Im aware that this pretty cursed in general, but its a behaviour difference from Paper so I thought I report it.

ChunkHolder at [x, y] in world 'world' does not exist to untrack chunk

Stack trace

Paste.gg link
Server crashed at latest stacktrace.

Plugin and Datapack List

A simple plugin that use teleportAsync on random coordinates. Used to replicate #45, but ended up with this stacktrace

Actions to reproduce (if known)

When using teleportAsync a lot of time on unloaded chunks / random coordinates.

Folia version

[15:54:55 INFO]: Checking version, please wait...
[15:54:56 INFO]: This server is running Folia version git-Folia-"47105ea" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 47105ea)
You are running the latest version

Other

Might be related to #45.
View distance is 32 (to load a lot of chunks)

End gateway counter reset to 0 on server restart

Expected behavior

When the dragon dies, a new end gateway spawn.

Observed/Actual behavior

When the dragon dies, old end gateways are erased (the counter restart from the beginning: 0)

Steps/models to reproduce

1- Generate a new end
2- Kill the dragon
3- Restart
4- Summon the dragon with end crystals
5- Kill the dragon (not with /kill)
6- There is still only one end gateway

Plugin and Datapack List

None

Folia version

[20:30:19 INFO]: This server is running Folia version git-Folia-"17a3236" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 17a3236)
You are 2 version(s) behind
Download the new version at: https://papermc.io/downloads

Note: Reproductible on latest build

Other

The gateway counter is not saved correctly on shutdown ?

Cannot move entity off-main

Stack trace

https://paste.ubuntu.com/p/dnGZVGBrfb/

Plugin and Datapack List

plugins:
image

datapacket:
image

Actions to reproduce (if known)

According to the player description, at that time they were just exploring in hell and then the server crashed

Folia version

[23:06:01 INFO]: This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version

Other

No response

Command blocks not working

Expected behavior

* Set enable-command-block=true in server.properties
Join in the world, then place command block, type some command for example summon minecraft:bee ~ ~5 ~
Set command block properties to repeat; always active

Command block starts spawning bees

Observed/Actual behavior

Command block does nothing
output field also not working

Steps/models to reproduce

* Set enable-command-block=true in server.properties
Join in the world, then place command block, type some command for example summon minecraft:bee ~ ~5 ~
Set command block properties to repeat; always active

Command block doesn't spawning bees

Plugin and Datapack List

none

Folia version

This server is running Folia version git-Folia-"b1c668f" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b1c668f)
You are running the latest version

Other

Redstone also doesn't activate command block
It looks like command is just stupidly not processed, also command successfully saved in command block
When i type command in chat it works

Inactive mobs when player is nearby

Expected behavior

Normal mob behavior.

Observed/Actual behavior

Sometimes, mobs are inactive when player is nearby.
It seems to happen on chunk loading, but i'm not sure.
Video

Steps/models to reproduce

Step 1: Set time to night so enemies can spawn /time set night
Step 2: Set gamemode to survival /gamemode survival
Step 3: Invincibility, for testing purposes: /effect give @s resistance infinite 255
Step 4: TP far away: /tp 100000 100 0
Step 5: Walk till you encounter a hostile mob with no AI, repeat if needed

I can reproduce it after few tries.

Plugin and Datapack List

None

Folia version

> ver
[15:42:57 INFO]: This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)
You are running the latest version

Other

Here is everything i know:

  • It does not always happen on generation. I saw this bug on old chunks
  • Sometimes, spawning other mobs near freezed mobs also freeze them (? might be false. i can't reproduce it anymore)
  • Hitting mob does not solve the problem.
  • Logging out and logging back solve the problem.
  • Might be related to the "inactive" mob feature.

Players who slept while the server shut down cannot log in again

Expected behavior

Server stop when a player is sleeping, the player can log back.

Observed/Actual behavior

Player can't log back.

Error:

[16:27:58] [User Authenticator #0/INFO]: UUID of player skoaboi is 185cd978-a836-4a68-aa61-2debded034ab
[16:27:58] [Region Scheduler Thread #1/ERROR]: Couldn't place player in world
net.minecraft.ReportedException: Loading entity NBT
        at net.minecraft.world.entity.Entity.load(Entity.java:2502)
        at net.minecraft.world.level.storage.PlayerDataStorage.load(PlayerDataStorage.java:96)
        at net.minecraft.server.players.PlayerList.load(PlayerList.java:622)
        at net.minecraft.server.players.PlayerList.loadSpawnForNewPlayer(PlayerList.java:255)
        at net.minecraft.server.network.ServerLoginPacketListenerImpl.handleAcceptedLogin(ServerLoginPacketListenerImpl.java:215)
        at net.minecraft.server.network.ServerLoginPacketListenerImpl.tick(ServerLoginPacketListenerImpl.java:87)
        at net.minecraft.network.Connection.tick(Connection.java:624)
        at io.papermc.paper.threadedregions.RegionizedServer.tickConnections(RegionizedServer.java:263)
        at io.papermc.paper.threadedregions.RegionizedServer.globalTick(RegionizedServer.java:213)
        at io.papermc.paper.threadedregions.RegionizedServer$GlobalTickTickHandle.tickRegion(RegionizedServer.java:149)
        at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385)
        at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525)
        at java.lang.Thread.run(Thread.java:1589)
Caused by: java.lang.NullPointerException: Cannot read field "captureTreeGeneration" because the return value of "net.minecraft.world.level.World.getCurrentWorldData()" is null
        at net.minecraft.world.level.Level.getBlockState(Level.java:821)
        at net.minecraft.world.entity.LivingEntity.lambda$stopSleeping$10(LivingEntity.java:4208)
        at java.util.Optional.ifPresent(Optional.java:178)
        at net.minecraft.world.entity.LivingEntity.stopSleeping(LivingEntity.java:4207)
        at net.minecraft.world.entity.player.Player.stopSleepInBed(Player.java:1539)
        at net.minecraft.server.level.ServerPlayer.stopSleepInBed(ServerPlayer.java:1877)
        at net.minecraft.world.entity.player.Player.stopSleeping(Player.java:1549)
        at net.minecraft.server.level.ServerPlayer.readAdditionalSaveData(ServerPlayer.java:573)
        at net.minecraft.world.entity.Entity.load(Entity.java:2400)
        ... 12 more

Steps/models to reproduce

1- Sleep
2- Stop the server while sleeping
3- Start the server
4- Log back

Plugin and Datapack List

None.

Folia version

This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: https://github.com/PaperMC/Folia/commit/41c5548dee9c8c0190aea9d9a8d2b4ddc444db89)

Other

No world while sleeping ?

Call getNewScoreboard() returns excepcion

Expected behavior

Create new Scoreboard with success

Observed/Actual behavior

a null excepcion

[13:00:18 INFO]: [CoolProtection] [STDOUT] debug has ScoreboardManager org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager@233c4975
[13:00:18 INFO]: [CoolProtection] [STDOUT] AsyncPlayerChatEvent
[13:00:18 ERROR]: Could not pass event ServerTickEndEvent to CoolProtection v1.6
java.lang.UnsupportedOperationException: null
at org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager.getNewScoreboard(CraftScoreboardManager.java:45) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager.getNewScoreboard(CraftScoreboardManager.java:25) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at me.tontito.coolprotection.TpsCheck.setScoreBoard(TpsCheck.java:399) ~[CoolProtection.jar:?]

Steps/models to reproduce

CODE:
ScoreboardManager manage = Bukkit.getScoreboardManager();

    if (manage == null) {
        System.out.println("debug doesnt' have ScoreboardManager");
        return;
    } else {
        System.out.println("debug has ScoreboardManager " + manage);
    }

    System.out.println("AsyncPlayerChatEvent");

    Scoreboard board = manage.getNewScoreboard();

RESULT:
[13:00:18 INFO]: [CoolProtection] [STDOUT] debug has ScoreboardManager org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager@233c4975
[13:00:18 INFO]: [CoolProtection] [STDOUT] AsyncPlayerChatEvent
[13:00:18 ERROR]: Could not pass event ServerTickEndEvent to CoolProtection v1.6
java.lang.UnsupportedOperationException: null
at org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager.getNewScoreboard(CraftScoreboardManager.java:45) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at org.bukkit.craftbukkit.v1_19_R3.scoreboard.CraftScoreboardManager.getNewScoreboard(CraftScoreboardManager.java:25) ~[folia-1.19.4.jar:git-Folia-"7072994"]
at me.tontito.coolprotection.TpsCheck.setScoreBoard(TpsCheck.java:399) ~[CoolProtection.jar:?]

Plugin and Datapack List

No datapack.
One plugin been changed for folia compatibility

Folia version

[13:03:13 INFO]: Checking version, please wait...
[13:03:13 INFO]: This server is running Folia version git-Folia-"7072994" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 7072994)
You are running the latest version
Previous version: git-Folia-"00cfbaa" (MC: 1.19.4)

Other

No response

End Gate portal doesn't work. (The portal that you throw an enderpearl into and it brings you to the end city islands.)

Expected behavior

Ender pearl goes through and teleports you to the islands.

Observed/Actual behavior

Ender pearls do not work at all when thrown through the portal.

Steps/models to reproduce

Throw an enderpearl through the end gate.

Plugin and Datapack List

N/A

Folia version

[15:39:03 INFO]: This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)
You are 2 version(s) behind

1 version was just debug. And the other was: dddaab9

Other

I teleported through the portal by breaking the bedrock around it and it had a landable area for the enderpearls.

Folia block generation error

Expected behavior

It should have safely generated normal blocks following my server's packets, because blocks elsewhere on my server were normal

Observed/Actual behavior

But....Okay, look this then you can know the problems
image

Steps/models to reproduce

I think this is a completely random error, because most of my server is normal, including the error map I showed has been generated on the Paper server and copied to Folia, but Folia is still in the wrong state

But I observed a problem, at first Folia did load the maps normally, but as the loading maps got bigger and started to freeze from a certain edge, the maps started to get strange and made the normal loading maps wrong, which happened in the ocean, including the rivers along the oceans

Maybe it's an issue with my packets, but I can't 100% guarantee that this is the case, because the rest of the maps on my server are complete and error-free, so I chose to give you feedback

Plugin and Datapack List

plugins:
image

datapackets:
image

Folia version

[20:20:50 INFO]: Checking version, please wait...
[20:20:50 INFO]: This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version

Other

This is a little bit wrong report, in that time server only output these things...

https://paste.ubuntu.com/p/XBJ8P9Ytwh/

Error

Stack trace

paste your stack trace or a paste.gg link here!
[10:56:49 ERROR]: [ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadPool] Exception thrown from thread 'Tuinity Chunk System Worker #0' in queue 'ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadPool$PrioritisedPoolExecutorImpl@7a1415e7'
net.minecraft.world.level.chunk.MissingPaletteEntryException: Missing Palette entry for index 9.
        at net.minecraft.world.level.chunk.LinearPalette.valueFor(LinearPalette.java:76) ~[?:?]
        at net.minecraft.world.level.chunk.PalettedContainer.get(PalettedContainer.java:208) ~[?:?]
        at ca.spottedleaf.starlight.common.light.StarLightEngine.getBlockState(StarLightEngine.java:297) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.starlight.common.light.StarLightEngine.performLightDecrease(StarLightEngine.java:1333) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.starlight.common.light.BlockStarLightEngine.propagateBlockChanges(BlockStarLightEngine.java:201) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.starlight.common.light.StarLightEngine.blocksChangedInChunk(StarLightEngine.java:427) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at io.papermc.paper.chunk.system.light.LightQueue$ChunkTasks.run(LightQueue.java:265) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at io.papermc.paper.chunk.system.scheduling.queue.RadiusAwarePrioritisedExecutor$Task.run(RadiusAwarePrioritisedExecutor.java:468) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadPool$PrioritisedThread.pollTasks(PrioritisedThreadPool.java:278) ~[folia-1.19.4.jar:git-Folia-"41c5548"]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedQueueExecutorThread.run(PrioritisedQueueExecutorThread.java:62) ~[folia-1.19.4.jar:git-Folia-"41c5548"]

Plugin and Datapack List

[10:57:57 INFO]: Paper Plugins:
[10:57:57 INFO]: - MiniScoreBoard
[10:57:57 INFO]: Bukkit Plugins:
[10:57:57 INFO]: - Chatty, Chunky, CoreProtect, floodgate, FreedomChat, LuckPerms, spark, TAB, Vault, ViaBackwards
[10:57:57 INFO]: ViaVersion

Actions to reproduce (if known)

idk

Folia version

[10:58:25 INFO]: This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)
You are running the latest version

Other

No response

Conversations API results in chat breaking

Expected behavior

Bukkit Conversations API can be used as normal

Observed/Actual behavior

Once a conversation is begin()ed with a player, every chat message they say results in this:

[00:04:52 ERROR]: Chain link failed, continuing to next one
java.lang.UnsupportedOperationException: null
        at net.minecraft.server.network.ServerGamePacketListenerImpl.broadcastChatMessage(ServerGamePacketListenerImpl.java:2550) ~[?:?]
        at net.minecraft.server.network.ServerGamePacketListenerImpl.lambda$handleChat$11(ServerGamePacketListenerImpl.java:2238) ~[?:?]
        at java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:718) ~[?:?]
        at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]

Steps/models to reproduce

Scala snippet of the code I am using to invoke the conversations API:

private case class PromptState(
    promise: Promise[String],
    conversation: Conversation,
)

class Prompts(using plugin: Plugin):
    private val prompts = scala.collection.concurrent.TrieMap[UUID, PromptState]()

    def prompt(player: Player, prompt: String): Future[String] =
        if prompts.contains(player.getUniqueId()) then
            val state = prompts(player.getUniqueId())
            state.promise.failure(Exception("cancelled by another prompt"))
            state.conversation.abandon()
            prompts.remove(player.getUniqueId())

        val promise = Promise[String]()
        given ctx: ExecutionContext = EntityExecutionContext(player)

        val bukkitPrompt = new StringPrompt:
            override def getPromptText(context: ConversationContext): String =
                prompt
            override def acceptInput(context: ConversationContext, input: String): Prompt =
                prompts(player.getUniqueId()).promise.complete(Try(input))
                prompts.remove(player.getUniqueId())
                Prompt.END_OF_CONVERSATION

        val conversation = ConversationFactory(plugin)
            .withModality(false)
            .withLocalEcho(false)
            .withFirstPrompt(bukkitPrompt)
            .buildConversation(player)
            
        val state = PromptState(promise, conversation)
        Future { player.closeInventory() }
        conversation.begin()
        prompts(player.getUniqueId()) = state
        promise.future

Plugin and Datapack List

Only my own code (findable at https://github.com/BlueMoonVineyard/BallCore/tree/work/jblackquill/folia)

Folia version

> version
[00:09:49 INFO]: Checking version, please wait...
[00:09:49 INFO]: This server is running Folia version git-Folia-"ed7a5c5" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: ed7a5c5)
You are 1 version(s) behind
Download the new version at: https://papermc.io/downloads

Other

No response

World generation crashes the server

Stack trace

paste your stack trace or a paste.gg link here!

https://mclo.gs/LwjfUMD

Plugin and Datapack List

[12:29:00 INFO]: Paper Plugins:
[12:29:00 INFO]: - MiniScoreBoard
[12:29:00 INFO]: Bukkit Plugins:
[12:29:00 INFO]: - Chatty, Chunky, CoreProtect, DiscordSRV, floodgate, FreedomChat, LuckPerms, spark, TAB, Vault
[12:29:00 INFO]: ViaBackwards, ViaVersion

Actions to reproduce (if known)

No response

Folia version

[12:29:13 INFO]: This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)
You are 2 version(s) behind
Download the new version at: https://papermc.io/downloads

Other

i'll try now to update to dddaab9 , but still wanted to report in case if that was not related to this

API: Location Tick Times

Is your feature request related to a problem?

As a regionised server software, we don't know what current API Bukkit#getTickTimes, Bukkit#getAverageTickTime and Bukkit#getTPS should return.
It might be great to get significative TPS info based on region tick times.

Describe the solution you'd like.

Deprecate Bukkit#getTickTimes and Server#getTickTimes
Deprecate Bukkit#getAverageTickTime and Server#getAverageTickTime
Deprecate Bukkit#getTPS and Server#getTPS
Add Bukkit.getTickTimes(@NotNull Location): Give Tick Times based on Location Region Tick Times

Describe alternatives you've considered.

Bukkit.getTickTimes(@NotNull Entity): Give Tick Times based on Entity Region Tick Times
Same with getTPS getAverageTickTimes.

Other

No response

Entities going through portails lose their weapon

Expected behavior

Push a mob with a weapon through a portal, on the other side of the portal it is the same entity with the same weapon.

Observed/Actual behavior

Push a mob with a weapon through a portal, on the other side of the portal it is the same entity but without weapon, and persistent.

Steps/models to reproduce

1- Build a nether portal
2- Summon a zombified piglin with a sword /summon zombified_piglin
3- Push it through the portal
4- Zombified piglin is now persistent and without its sword.

Plugin and Datapack List

None

Folia version

[19:49:33 INFO]: This server is running Folia version git-Folia-"33d2aa8" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 33d2aa8)
You are running the latest version
Previous version: git-Folia-"7072994" (MC: 1.19.4)

Other

This bug seems to make entities persistent
Works with skeletons, wither skeletons...

Works fine on git-Paper-"1704bf7"

Packet error when changing player position during onPlayerMove

Stack trace

Mar 31 02:10:28 debianrack java[3112484]: [02:10:28 ERROR]: Failed to handle packet net.minecraft.network.protocol.game.ServerboundMovePlayerPacket$Pos@186d4068, suppressing error
Mar 31 02:10:28 debianrack java[3112484]: java.lang.UnsupportedOperationException: Must use teleportAsync while in region threading
Mar 31 02:10:28 debianrack java[3112484]:       at org.bukkit.craftbukkit.v1_19_R3.entity.CraftPlayer.teleport(CraftPlayer.java:1264) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at org.bukkit.craftbukkit.v1_19_R3.entity.CraftPlayer.teleport(CraftPlayer.java:1213) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.server.network.ServerGamePacketListenerImpl.handleMovePlayer(ServerGamePacketListenerImpl.java:1622) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket.handle(ServerboundMovePlayerPacket.java:29) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket$Pos.handle(ServerboundMovePlayerPacket.java:66) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.network.protocol.PacketUtils.lambda$ensureRunningOnSameThread$0(PacketUtils.java:52) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.network.protocol.PacketUtils.lambda$ensureRunningOnSameThread$1(PacketUtils.java:75) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at io.papermc.paper.threadedregions.EntityScheduler.executeTick(EntityScheduler.java:173) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1533) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:316) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:379) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:516) ~[folia-1.19.4.jar:git-Folia-"cb81240"]
Mar 31 02:10:28 debianrack java[3112484]:       at java.lang.Thread.run(Thread.java:1589) ~[?:?]

Plugin and Datapack List

AuthMeReloaded

Actions to reproduce (if known)

The following code causes the error:

public void onPlayerMove(PlayerMoveEvent event) {
// ....
// "cancel" the event
event.setTo(event.getFrom());
// ....
}

I don't know why AuthMeReloaded uses this line instead of event.setCancelled(true), but it should work anyway, or at least give an explicit error, and not just a stacktrace

Folia version

This server is running Folia version git-Folia-"cb81240" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: cb81240)
Error obtaining version information
Previous version: git-Folia-"5b74945" (MC: 1.19.4)

Other

No response

Player cant join

Stack trace

[19:54:33 INFO]: vodaept[/test:57686] logged in with entity id 1733 at ([world]937238.162192892, 117.75, 781957.1901814165)
[19:54:33 ERROR]: Thread Netty Epoll Server IO #4 failed main thread check: Cannot read world asynchronously
java.lang.Throwable: null
        at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:57) ~[folia-1.19.4.jar:?]
        at org.bukkit.craftbukkit.v1_19_R3.block.CraftBlock.getNMS(CraftBlock.java:86) ~[folia-1.19.4.jar:?]
        at org.bukkit.craftbukkit.v1_19_R3.block.CraftBlock.isEmpty(CraftBlock.java:508) ~[folia-1.19.4.jar:?]
        at com.willfp.libreforge.conditions.impl.ConditionInAir.isMet(ConditionInAir.kt:10) ~[libreforge-4.13.0-all.jar:?]
        at com.willfp.libreforge.conditions.impl.ConditionInAir.isMet(ConditionInAir.kt:8) ~[libreforge-4.13.0-all.jar:?]
        at com.willfp.libreforge.conditions.ConditionBlock.isMet(ConditionBlock.kt:36) ~[libreforge-4.13.0-all.jar:?]
        at com.willfp.libreforge.conditions.ConditionList.getNotMetLines(ConditionList.kt:47) ~[libreforge-4.13.0-all.jar:?]
        at com.willfp.ecoenchants.display.EnchantDisplay.display(EnchantDisplay.kt:82) ~[EcoEnchants v10.12.1.jar:?]
        at com.willfp.eco.core.display.Display.display(Display.java:98) ~[eco-6.59.0-all.jar:?]
        at com.willfp.eco.internal.spigot.proxy.v1_19_R3.common.packet.display.PacketWindowItems.modifyWindowItems(PacketWindowItems.kt:76) ~[eco-6.59.0-all.jar:?]
        at com.willfp.eco.internal.spigot.proxy.v1_19_R3.common.packet.display.PacketWindowItems.onSend(PacketWindowItems.kt:49) ~[eco-6.59.0-all.jar:?]
        at com.willfp.eco.internal.events.EcoEventManagerKt.handleSend(EcoEventManager.kt:23) ~[eco-6.59.0-all.jar:?]
        at com.willfp.eco.internal.spigot.proxy.v1_19_R3.common.packet.EcoChannelDuplexHandler.write(EcoChannelDuplexHandler.kt:39) ~[eco-6.59.0-all.jar:?]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:879) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:863) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:968) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:856) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.ChannelDuplexHandler.write(ChannelDuplexHandler.java:115) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at me.neznamy.tab.shared.features.injection.NettyPipelineInjector$TabChannelDuplexHandler.write(NettyPipelineInjector.java:128) ~[TAB-4.0.0-SNAPSHOT.jar:?]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:879) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:863) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:968) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:856) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:120) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:940) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:966) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:934) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1020) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:311) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
        at com.comphenix.protocol.injector.netty.channel.NettyChannelProxy.writeAndFlush(NettyChannelProxy.java:227) ~[ProtocolLib.jar:?]
        at com.comphenix.protocol.injector.netty.channel.NettyChannelProxy.writeAndFlush(NettyChannelProxy.java:233) ~[ProtocolLib.jar:?]
        at net.minecraft.network.Connection.doSendPacket(Connection.java:486) ~[?:?]
        at net.minecraft.network.Connection.lambda$sendPacket$11(Connection.java:460) ~[?:?]
        at com.comphenix.protocol.injector.netty.channel.NettyEventLoopProxy.lambda$proxyRunnable$2(NettyEventLoopProxy.java:48) ~[ProtocolLib.jar:?]
        at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:403) ~[netty-transport-classes-epoll-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
        at java.lang.Thread.run(Thread.java:1589) ~[?:?]
[19:54:33 INFO]: vodaept lost connection: Internal Exception: java.lang.IllegalStateException: Cannot read world asynchronously
[19:54:33 INFO]: [voicechat] Disconnecting client vodaept

Plugin and Datapack List

image

Actions to reproduce (if known)

No response

Folia version

Latest

Other

No response

Clarify API naming scheme

I think the type naming is inconsistent, with itself, and with other aspects of the existing API. To be clear, I don't care which we go with, but I do feel that consistency is important for an API (not as big a deal for the impl). The API uses z instead of s in types already, like FertilizeEggEvent and oxidized relating to copper. The API isn't consistent with itself already, like Effect#OXIDISED_COPPER_SCRAPE but I feel like we should push for consistency in all new things.

Also, the term RegionisedScheduler doesn't seem to mesh with GlobalRegionScheduler and EntityScheduler. Those aren't GlobalisedRegionScheduler or EntitisedScheduler. I think the names for different schedulers should be RegionScheduler, GlobalScheduler, and EntityScheduler removing this problem with s and z in the first place.

WorldData creates a nullpointer at fawe

Expected behavior

Fawe use for regeneration of chunks some methods. Normally getBlockEntity gives us every block tile entity from the chunk.

Observed/Actual behavior

The chunk level data random empty.

Steps/models to reproduce

  1. Clone IntellectualSites/FastAsyncWorldEdit#2171 branch from me.
  2. Clear a section with FAWE and try to regenerate the cleared area.

Plugin and Datapack List

image

Folia version

image

Other

No response

Unusable datapacks

Expected behavior

7LOG_SRGY4C9TFI$1AI5HG3

Observed/Actual behavior

%IC)J97A2KH 5488XI IQRW

Steps/models to reproduce

I am using translation software, so what I said may be incorrect. I apologize
I added several datapacks of vanilla that can be used normally under paper, but there are several issues with function under folia

Plugin and Datapack List

I found that the “/datapack list” command cannot be used

Folia version

[20:45:00 INFO]: This server is running Folia version git-Folia-"ed7a5c5" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: ed7a5c5)
You are running the latest version
Previous version: git-Purpur-1947 (MC: 1.19.4)

Other

In addition, I found that the “/datapack list” command cannot be used

"java.lang.IllegalStateException: Illegal recursive processTicketUpdates" (already holding ticket lock) during ChunkProvider tick

Stack trace

https://paste.gg/p/anonymous/034189458a1e4d8c8a2add6e47308dc2

Plugin and Datapack List

Chunky

However this issue was also occuring without it so...

Actions to reproduce (if known)

Teleport far out when the server is under heavy load.

Folia version

[02:05:39 INFO]: This server is running Folia version git-Folia-"41c5548" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 41c5548)
You are running the latest version

Other

No response

Async entity addEffect call on raid completion

Stack trace

[05:31:07] [Region Scheduler Thread #9/ERROR]: Thread Region Scheduler Thread #9 failed main thread check: Cannot add effects to entities asynchronously
java.lang.Throwable: null
        at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:78) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1123) ~[?:?]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1119) ~[?:?]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1110) ~[?:?]
        at net.minecraft.world.entity.raid.Raid.tick(Raid.java:410) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.world.entity.raid.Raids.tick(Raids.java:75) ~[?:?]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:735) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1697) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1542) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:360) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]
[05:31:07] [Region Scheduler Thread #9/ERROR]: [io.papermc.paper.threadedregions.TickRegionScheduler] Region #20599 centered at chunk [23, -12] in world 'world' failed to tick:
net.minecraft.ReportedException: Exception ticking world
        at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1716) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1542) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at io.papermc.paper.threadedregions.TickRegions$ConcreteRegionTickHandle.tickRegion(TickRegions.java:360) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:385) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.lang.IllegalStateException: Cannot add effects to entities asynchronously
        at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:79) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1123) ~[?:?]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1119) ~[?:?]
        at net.minecraft.world.entity.LivingEntity.addEffect(LivingEntity.java:1110) ~[?:?]
        at net.minecraft.world.entity.raid.Raid.tick(Raid.java:410) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        at net.minecraft.world.entity.raid.Raids.tick(Raids.java:75) ~[?:?]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:735) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1697) ~[folia-1.19.4.jar:git-Folia-"b97116b"]
        ... 6 more

Plugin and Datapack List

N/A

Actions to reproduce (if known)

No response

Folia version

This server is running Folia version git-Folia-"b97116b" (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: b97116b)
You are running the latest version

Other

No response

Possible memory problem

Expected behavior

Expected no problems, as observed in Paper

Observed/Actual behavior

  1. On Paper, the stress test ran for about 5 hours with no problems, just delayed ticks ~100.

2 . On Folia, after about 44m it starts complaining with:

[2641.978s][warning][gc,alloc] Netty Server IO #3: Retried waiting for GCLocker too often allocating 256 words
version[3327.573s][warning][gc,alloc] Server console handler: Retried waiting for GCLocker too often allocating 331 words
[3327.857s][warning][gc,alloc] Tuinity Chunk System Worker #1: Retried waiting for GCLocker too often allocating 520397 words
[10578.627s][warning][gc,alloc] Region Scheduler Thread #0: Retried waiting for GCLocker too often allocating 524288 words
After some more time, server stops receiving new players and outputting red errors.

[09:31:27 ERROR]: Too many chained neighbor updates. Skipping the rest. First skipped position: -1697, 56, -3444
[09:31:28 ERROR]: Too many chained neighbor updates. Skipping the rest. First skipped position: -1702, 50, -3259
[09:31:29 ERROR]: Too many chained neighbor updates. Skipping the rest. First skipped position: -1645, 60, -3288
[09:31:32 ERROR]: Too many chained neighbor updates. Skipping the rest. First skipped position: -1610, 62, -3255

Steps/models to reproduce

Teste was conducted using Paper and Folia, same map, same startup parameters, pre-generated map and using stress test code with 20 bots (all active).

set JAR=folia-1.19.4-26.jar / paper-1.19.4-513.jar
set MINRAM=1G
set MAXRAM=4G
set FLAGS=-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Daikars.new.flags=true -Dusing.aikars.flags=https://mcflags.emc.gs
echo Starting server...
java -Xms%MINRAM% -Xmx%MAXRAM% %FLAGS% -jar %JAR% --nogui

Plugin and Datapack List

[21:47:10 INFO]: Bukkit Plugins:
[21:47:10 INFO]: - ViaBackwards, ViaVersion

Folia version

[20:41:07 INFO]: This server is running Folia version git-Folia-26 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 25e0cbd)
You are running the latest version
Previous version: git-Paper-513 (MC: 1.19.4)

Other

No response

Kick with shulker

Expected behavior

tested in fork: Kaiiju and Folia, same problem.

Observed/Actual behavior

https://pastes.dev/CqfoszkNBT

Steps/models to reproduce

Any action with the shulkers.

Plugin and Datapack List

i don't have plugins

Folia version

fea2422

Other

.

Will Folia release versions (1.16.5/1.17.1) in the future?

Is your feature request related to a problem?

Hello, dear team member of folia!

I am a Minecraft player who has been using your Minecraft 1.19.4 server with enthusiasm and satisfaction. However, some of my friends would like to continue using old Minecraft plugins that are only compatible with Minecraft 1.16.5.

Therefore, I would like to request that folia team could consider releasing a server version that works with Minecraft 1.16.5 in the future, to facilitate those players who wish to use old plugins and enjoy better gaming experience. I understand that this may require time and effort from your team, but if it could be realized, I believe many players would benefit.

If you need any additional information or support from us, please let us know. Thank you again for your contribution and efforts in the Minecraft community, and looking forward to your reply!

Describe the solution you'd like.

The content above

Describe alternatives you've considered.

The content above

Other

The content above

I am trying to import the API with Gradle Kotlin and it not detect nothing

Expected behavior

I am trying to import the API with Gradle Kotlin and it not detect nothing. When i use maven works

Observed/Actual behavior

With gradle:
Not loading the API

With maven:
Load the API correctly

Steps/models to reproduce

Gradle Kotlin.

Captura de pantalla 2023-04-11 a las 17 52 18

Captura de pantalla 2023-04-11 a las 17 52 39

Plugin and Datapack List

No plugin list.

Folia version

No problem with plugins. Only with the API with Gradle

Other

No response

Explain core count recommendation

The FAQ says:

What hardware will Folia run best on?

Ideally, at least 16 cores (not threads).

How did this answer come about? Why "at least 16" and not 8 or 4? It confuses me because I would think anything > 1 would be an improvement over the single-threaded implementation.

Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.