Waxed weather blocks don't NEED to exist because they can't get any more weathered. It'd be redundant.
This is the noise settings json I was using. It's the exact same as the one in the vanilla worldgen files provided by slicedlime.
{
"bedrock_roof_position": -10,
"bedrock_floor_position": 0,
"sea_level": 63,
"disable_mob_generation": false,
"structures": {
"stronghold": {
"distance": 32,
"spread": 3,
"count": 128
},
"structures": {
"minecraft:jungle_pyramid": {
"spacing": 32,
"separation": 8,
"salt": 14357619
},
"minecraft:nether_fossil": {
"spacing": 2,
"separation": 1,
"salt": 14357921
},
"minecraft:stronghold": {
"spacing": 1,
"separation": 0,
"salt": 0
},
"minecraft:shipwreck": {
"spacing": 24,
"separation": 4,
"salt": 165745295
},
"minecraft:monument": {
"spacing": 32,
"separation": 5,
"salt": 10387313
},
"minecraft:endcity": {
"spacing": 20,
"separation": 11,
"salt": 10387313
},
"minecraft:swamp_hut": {
"spacing": 32,
"separation": 8,
"salt": 14357620
},
"minecraft:bastion_remnant": {
"spacing": 27,
"separation": 4,
"salt": 30084232
},
"minecraft:desert_pyramid": {
"spacing": 32,
"separation": 8,
"salt": 14357617
},
"minecraft:igloo": {
"spacing": 32,
"separation": 8,
"salt": 14357618
},
"minecraft:pillager_outpost": {
"spacing": 32,
"separation": 8,
"salt": 165745296
},
"minecraft:mansion": {
"spacing": 80,
"separation": 20,
"salt": 10387319
},
"minecraft:mineshaft": {
"spacing": 1,
"separation": 0,
"salt": 0
},
"minecraft:ocean_ruin": {
"spacing": 20,
"separation": 8,
"salt": 14357621
},
"minecraft:fortress": {
"spacing": 27,
"separation": 4,
"salt": 30084232
},
"minecraft:village": {
"spacing": 32,
"separation": 8,
"salt": 10387312
},
"minecraft:buried_treasure": {
"spacing": 1,
"separation": 0,
"salt": 0
},
"minecraft:ruined_portal": {
"spacing": 40,
"separation": 15,
"salt": 34222645
}
}
},
"noise": {
"random_density_offset": true,
"density_factor": 1.0,
"density_offset": -0.46875,
"simplex_surface_noise": true,
"bottom_slide": {
"target": -30,
"size": 0,
"offset": 0
},
"size_horizontal": 1,
"size_vertical": 2,
"height": 256,
"sampling": {
"xz_scale": 0.9999999814507745,
"y_scale": 0.9999999814507745,
"xz_factor": 80.0,
"y_factor": 160.0
},
"top_slide": {
"target": -10,
"size": 3,
"offset": 0
}
},
"default_block": {
"Name": "minecraft:stone"
},
"default_fluid": {
"Properties": {
"level": "0"
},
"Name": "minecraft:water"
}
}
Will I need to create a new issue, or edit this one?
After further investigation, this only occurs on worlds updated from any 1.14.3 pre-release.
Can confirm, this is quite annoying. It goes away for nearby chunks when I reload chunks using F3, but shows up as soon as i move out of the immediate area.
Can confirm for 1.14 release
Confirmed for 1.14 pre-release 1
Confirmed. Amount of delay varies, but is usually quite long and noticeable.
This isn't a bug so much as an annoyance. I doubt Mojang is going to do anything about this.
Same for when using a hopper to place items into an inventory, including things with no UI such as composters.
Can confirm for 19w11a. POI not registered for eu{coordinates}. For me, it happens when a hopper tries to input into a composter. It would help if I had any idea what POI is...
Here's my crash report:
---- Minecraft Crash Report ----
// You're mean.
Time: 3/13/19 1:40 PM
Description: Ticking block entity
java.lang.IllegalStateException: POI never registered at eu{x=93, y=72, z=90}
at aoz.a(SourceFile:72)
at aox.a(SourceFile:36)
at vc.c(SourceFile:1274)
at vc$$Lambda$3083/2131146735.run(Unknown Source)
at afy.execute(SourceFile:77)
at vc.a(SourceFile:1273)
at bfy.a(SourceFile:252)
at blu.b(SourceFile:249)
at blu.a(SourceFile:37)
at blu$b.e(SourceFile:402)
at agw.a(SourceFile:100)
at bsp.a(SourceFile:310)
at bsp.a(SourceFile:274)
at bsp.v(SourceFile:180)
at bsp.a(SourceFile:122)
at bsp.g(SourceFile:109)
at bfy.K(SourceFile:620)
at vc.a(SourceFile:401)
at net.minecraft.server.MinecraftServer.b(SourceFile:814)
at net.minecraft.server.MinecraftServer.a(SourceFile:753)
at dwc.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:628)
at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Server thread
Stacktrace:
at aoz.a(SourceFile:72)
at aox.a(SourceFile:36)
at vc.c(SourceFile:1274)
at vc$$Lambda$3083/2131146735.run(Unknown Source)
at afy.execute(SourceFile:77)
at vc.a(SourceFile:1273)
at bfy.a(SourceFile:252)
at blu.b(SourceFile:249)
at blu.a(SourceFile:37)
at blu$b.e(SourceFile:402)
at agw.a(SourceFile:100)
at bsp.a(SourceFile:310)
at bsp.a(SourceFile:274)
at bsp.v(SourceFile:180)
at bsp.a(SourceFile:122)
at bsp.g(SourceFile:109)
-- Block entity being ticked --
Details:
Name: minecraft:hopper // bsp
Block: Block{minecraft:hopper}[enabled=true,facing=down]
Block location: World: (93,73,90), Chunk: (at 13,4,10 in 5,5; contains blocks 80,0,80 to 95,255,95), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Block: Block{minecraft:hopper}[enabled=true,facing=down]
Block location: World: (93,73,90), Chunk: (at 13,4,10 in 5,5; contains blocks 80,0,80 to 95,255,95), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Stacktrace:
at bfy.K(SourceFile:620)
at vc.a(SourceFile:401)
-- Affected level --
Details:
Level name: ยง4Beet
All players: 1 total; [vd['SailorDoge'/820, l='ยง4Beet', x=88.79, y=82.12, z=56.72]]
Chunk stats: ServerChunkCache: 3906
Level seed: -6035552635704855193
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options: {}
Level spawn location: World: (-225,64,-209), Chunk: (at 15,4,15 in -15,-14; contains blocks -240,0,-224 to -225,255,-209), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 13351973 game time, 1351460 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 1 (now: false), thunder time: 1 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: true
Stacktrace:
at net.minecraft.server.MinecraftServer.b(SourceFile:814)
at net.minecraft.server.MinecraftServer.a(SourceFile:753)
at dwc.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:628)
at java.lang.Thread.run(Thread.java:745)
-- System Details --
Details:
Minecraft Version: 19w11a
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 3394462200 bytes (3237 MB) / 4697620480 bytes (4480 MB) up to 6442450944 bytes (6144 MB)
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx6G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
Player Count: 1 / 8; [vd['SailorDoge'/820, l='ยง4Beet', x=88.79, y=82.12, z=56.72]]
Data Packs: vanilla, file/Arrow Motion (incompatible), file/Exolumina Data Pack (incompatible), file/More Items Helper (incompatible)
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Confirmed for 19w06a. It seems to happen when the campfire is just inside/outside loaded chunks, or just out of render distance.
Can confirm for 19w05a
Can confirm. From what I've seen, they appear further off target the higher up they are, although this could be a coincidence.
Can confirm for 19w02a
I can confirm that this does happen, I've had a lot of problems because of it
I can also confirm, every block that had its name changed (the copper blocks) did not update properly.