ERROR]: Detected setBlock in a far chunk in paper 1.17-R0.1-EXPERIMENTAL-3.jar

[rrvk]

Stack trace

[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=33, z=660}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=32, z=660}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=31, z=660}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=33, z=661}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=32, z=661}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=31, z=661}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7600, y=30, z=661}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7599, y=33, z=659}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7599, y=32, z=659}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7599, y=31, z=659}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]
[11:12:03 ERROR]: Detected setBlock in a far chunk [-475, 41], pos: MutableBlockPosition{x=-7599, y=30, z=659}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/structure_feature / minecraft:ruined_portal]

Plugin list

None

Actions to reproduce (if known)

Create a world with this seed: 1357739335676506647 Then teleport to -7609 91 496 (/execute in minecraft:overworld run tp @s -7609.19 91.60 496.79 709.87 90.00) Look arround and see the error in de logging

Paper version

version [11:16:28 INFO]: This server is running Paper version git-Paper-"d76f8e0" (MC: 1.17) (Implementing API version 1.17-R0.1-SNAPSHOT) Error obtaining version information

Agreements

• [X] I am running the latest version of Paper available from https://papermc.io/downloads.
• [X] I have searched for and ensured there isn't already an open issue regarding this.
• [X] My version of Minecraft is supported by Paper.

Other

No response

[Aurelien30000]

That's probably a valid warning. Occured also running around my test map, too quickly I guess.

[thboehi]

I've the same error on my server, running Paper 1.17-24

[speedypotato]

Encountered this issue on seed 32845940991, paper 1.17-36. Triggered near world spawn, flying around in creative mode.

[Alim1236]

Encountered on vanilla server on 1.17 - triggered when I used /teleport to a get to a faraway coordinate

[BillyGalbreath]

I can confirm this. It does look intentional by Mojang, though. We might want to add a toggle to suppress the message, though?

[pop4959]

Yeah, just looks like debug information that they forgot to remove IMO.

[electronicboy]

Looks like they generally just converted the old out of bounds exception to be a warn rather than a straight up error, ideally we fix this crap but generally, I err on committing to stuff this deep not even mojang wanna fix... :L

[MaximMaximS]

Encountered on brand new 1.17 server, without even joning the world.

[Elijahzeal]

I've just experienced the same bug while using Chunky & ChunkBorder on a Purpur 1.17 - 1233 build - Seed: 5052018685391277943. Triggered while no users were online and doing a pre-generation.

[NoXXoN123]

Yeah same problem. I got this error: [16:58:26 ERROR]: Detected setBlock in a far chunk [-2, -8], pos: MutableBlockPosition{x=-31, y=134, z=-113}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/configured_feature / expansion:asteroids/blue_ice_blobs] Does anyone have any idea why?

[Zarepheth]

I think the problem is that once these errors start happening, they don't stop, and within a minute can cause the Minecraft logs to overflow with well over 100,000 entries.

[kribjo]

I get these in Paper 1.18.1-181 when pregenerating chunks with the Chunky plugin (v.1.2.173). Only had it happen once though (on pregenerating/expanding a circular world from ~8 000 blocks radius to over 10 000 blocks radius), and it was just on eight adjacent blocks, very close to the world edge:

[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9959, y=-50, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9957, y=-50, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9956, y=-51, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9956, y=-50, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9955, y=-51, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9955, y=-50, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9954, y=-51, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]
[22:03:59 ERROR]: Detected setBlock in a far chunk [-623, -78], pos: BlockPosition{x=-9953, y=-51, z=-1248}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]

[Owen1212055]

Note: This patch prevents this message from appearing multiple times now. However, this can be debugged by entering into debug mode.

[lynxplay]

Closing this as it does not seem to have been an issue after the addition of the patch 👍 If the issue persists on 1.19.3, feel free to comment.

[Albuquerquess]

I`d this problem again!

[Pvtatomxne]

I`d this problem again!

I have the same problem, also with Untamed Wilds. Firstly had the problem on my server, which froze up instantly after this message got displayed and even crashes a short time after. This also gets my singleplayer worlds to freeze up, but not crash. Hope anyone finds a solution for this.

[electronicboy]

Untamed mods has nothing to do with paper; and the general fix for this stuff is to stick within the bounds of the world-gen region that mojangs system provides, it would be on the mod to fix that.