greener.ca
- Greener
- greener
- Europe/Stockholm
- Yes
- No
MC-82752
Low
crash-2017-04-30_18.30.12-server.txt
I think the light level check for jungle biomes on passive mobs is reversed. Daytime: only thing that spawns is ocelots and slimes. Night time: hostile mobs and the rest of the passive mobs, including parrots.
Maybe they generate upon chunk generation, but not naturally thereafter? Was this a brand new world and in fresh chunks?
I've created a custom superflat world of jungle biome, in 1.12-pre2 or Minecraft 1.12 Pre-Release 2, the only things that spawn naturally are ocelots. Am I doing something wrong?
Edit: typos and the actual release name so the moderators and helpers can find this with their fancy filters
java.lang.NullPointerException: Ticking player server crash while accessing a furnace
Expected:
Right clicking on a furnace doesn't crash the server.Observed:
Right clicking a furnace crashes the server.Reproduction steps:
I wish I knew, been trying all afternoon.I have a saved version of the world that crashes every time. Can provide a link privately.
If I break this specific furnace and replace it, the new furnace doesn't crash the server. I parsed the .mca associated with the block and it seems the furnace doesn't actually exist within the chunk's tile entities.
Block in question is:
/setblock 215 12 -368 minecraft:furnace[facing=east,lit=false]
{CookTime:0s,BurnTime:0s,Items:[],RecipesUsedSize:0s,CookTimeTotal:0s,Lock:""}
A banner within the area represented on the outermost pixel of a map can not be marked. With a freshly crafted map, this is only one block on each side, but as you zoom out it becomes as much as sixteen (thirty-two, when you consider that the next map over has the same problem!)
Decompiled code analysis on 1.19.4:
net.minecraft.item.map.MapState
The logic and range used to determine if a banner falls within the current map bounds is incorrect.
line 294 in `private void addIcon` and
line 386 in `public boolean addBanner`
```java
if (f >= -63.0F && g >= -63.0F && f <= 63.0F && g <= 63.0F)
```Range >=-63 and <=63 is too narrow and will miss a row of 1 block on each side of the map. This is compounded once the scale is calculated as up to 16 blocks on each side will be missed once the banner coordinate is converted to a `float` on the 128 block scale of the map. The logic should be >-64 and <64, this will ensure all positions in all scales are included on the map. The range of blocks on the map if the center of the map is 0,0 is -64 to 63 in both axes.
solution:
```java
if (f > -64.0F && g > -64.0F && f < 64.0F && g < 64.0F)
```
A banner within the area represented on the outermost pixel of a map can not be marked. With a freshly crafted map, this is only one block on each side, but as you zoom out it becomes as much as sixteen (thirty-two, when you consider that the next map over has the same problem!)
Decompiled code analysis on 1.19.4:
net.minecraft.item.map.MapState
The logic and range used to determine if a banner falls within the current map bounds is incorrect.
line 294 in `private void addIcon` and
line 386 in `public boolean addBanner`
```java
if (f >= -63.0F && g >= -63.0F && f <= 63.0F && g <= 63.0F)
```Range >=-63 and <=63 is too narrow and will miss a row of 1 block on each side of the map. This is compounded once the scale is calculated as up to 16 blocks on each side will be missed once the banner coordinate is converted to a `float` on the 128 block scale of the map. The logic should be >=-64 and <64, this will ensure all positions in all scales are included on the map. The range of blocks on the map if the center of the map is 0,0 is -64 to 63 in both axes.
solution:
```java
if (f >= -64.0F && g >= -64.0F && f < 64.0F && g < 64.0F)
```
I've made a fabric mod using mixins that fixes this server side if devs are interested.
Banners, player indicator and decorations can not be marked on the outermost pixel of a map
The bug
A banner within the area represented on the outermost pixel of a map can not be marked. With a freshly crafted map, this is only one block on each side, but as you zoom out it becomes as much as sixteen (thirty-two, when you consider that the next map over has the same problem!)
Code analysis and fix
Decompiled code analysis on 1.
19.4:net.minecraft.item.map.MapState
The logic and range used to determine if a banner falls within the current map bounds is incorrect.
line 294 inprivate void addIcon andline 386 inpublic boolean addBannerif (f >= -63.0F && g >= -63.0F && f <= 63.0F && g <= 63.0F)Range >=-63 and <=63 is too narrow and will miss a row of 1 block on each side of the map. This is compounded once the scale is calculated as up to 16 blocks on each side will be missed once the banner coordinate is converted to a float on the 128 block scale of the map. The logic should be >=-64 and <64, this will ensure all positions in all scales are included on the map. The range of blocks on the map if the center of the map is 0,0 is -64 to 63 in both axes.
Solution:
if (f >= -64.0F && g >= -64.0F && f < 64.0F && g < 64.0F)I've made a fabric mod using mixins that fixes this server side if devs are interested.
The bug
A banner within the area represented on the outermost pixel of a map can not be marked. With a freshly crafted map, this is only one block on each side, but as you zoom out it becomes as much as sixteen (thirty-two, when you consider that the next map over has the same problem!)
Code analysis and fix
Decompiled code analysis on 1.20.4:
net.minecraft.item.map.MapState
The logic and range used to determine if a banner falls within the current map bounds is incorrect.
in {{private void addIcon}} and public boolean addBanner
if (f >= -63.0F && g >= -63.0F && f <= 63.0F && g <= 63.0F)Range >=-63 and <=63 is too narrow and will miss a row of 1 block on each side of the map. This is compounded once the scale is calculated as up to 16 blocks on each side will be missed once the banner coordinate is converted to a float on the 128 block scale of the map. The logic should be >=-64 and <64, this will ensure all positions in all scales are included on the map. The range of blocks on the map if the center of the map is 0,0 is -64 to 63 in both axes.
Solution:
if (f >= -64.0F && g >= -64.0F && f < 64.0F && g < 64.0F)Plus a few changes in the player tracking:
if (f < -64.0f) { b = -128; } if (g < -64.0f) { c = -128; } if (f >= 64.0f) { b = 127; } if (g >= 64.0f) { c = 127; }
and
byte b = (byte)((double)(f*2.0f)); byte c = (byte)((double)(g*2.0f));
I've made a fabric mod using mixins that fixes this server side if devs are interested.
In 18w22c I no longer experience a game crash when I (re)test these commented on seeds:
8223045022386406090 commented on by Meri Diana and Xavom
-7269461605076408993 commented on by greener.ca
-6968998364217797098 commented on by Bret Ryder at/near chunk 55,71
The 3rd on the list, I approached said chunk from 4 directions each in different tests. I also launched the game with default JVM arguments, and using -Xmx3G (memory bug: MC-121318).
I think it might be signs from 1.7
Try this:
Then:
related to my comment above, I attached a screenshot from NBTExplorer, maybe it has to do with this? Signs in 1.7 have "null" in NBT for lines that have no text.
I can confirm my suspicions, using NBTExplorer, I searched for Signs that had 'null' instead od '""' for one of their text fields, found 2 that must have been placed in the 1.7 days. Once I removed them in 1.8.8, 15w31c lets me in no issues. Yay! This is probably just part of a larger JSON strict parsing issue.
Any world created in 1.7 that has a sign will generate this error.
Edit: this is on server
This is also present in 15w32a
Yup, this just happened to some poor pigs. Affects 15w32b
Tested with 15w32c
Entities still disappear in portals and console messages are the same.
This is also present in 15w32c
This bug affects the latest snapshots, could we get an affects 15w43c? Maybe they can fix this for release?
---- Minecraft Crash Report ----// I'm sorry, Dave.
Time: 10/27/15 11:12 PMDescription: Exception in server tick loopjava.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) at java.util.HashMap$KeyIterator.next(HashMap.java:1453) at ln.a(SourceFile:180) at net.minecraft.server.MinecraftServer.D(SourceFile:626) at lb.D(SourceFile:314) at net.minecraft.server.MinecraftServer.C(SourceFile:546) at net.minecraft.server.MinecraftServer.run(SourceFile:450) at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– System Details --Details: Minecraft Version: 15w43c Operating System: Linux (amd64) version 3.13.0-29-generic Java Version: 1.8.0_45, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 338889136 bytes (323 MB) / 1495793664 bytes (1426 MB) up to 1743257600 bytes (1662 MB)
JVM Flags: 0 total; IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 0 / 20; [] Is Modded: Unknown (can't tell) Type: Dedicated Server (map_server.txt)
and in the console:
00:15:01] RCON Client #207/ERROR: Failed to save chunkjava.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1207) ~[?:1.8.0_45] at java.util.TreeMap$KeyIterator.next(TreeMap.java:1261) ~[?:1.8.0_45] at lq.a(SourceFile:691) ~[minecraft_server.15w43c.jar:?] at lq.a(SourceFile:674) ~[minecraft_server.15w43c.jar:?] at ash.a(SourceFile:232) ~[minecraft_server.15w43c.jar:?] at ash.a(SourceFile:102) [minecraft_server.15w43c.jar:?] at lp.b(SourceFile:147) [minecraft_server.15w43c.jar:?] at lp.a(SourceFile:166) [minecraft_server.15w43c.jar:?] at lq.a(SourceFile:885) [minecraft_server.15w43c.jar:?] at ay.a(SourceFile:36) [minecraft_server.15w43c.jar:?] at j.a(SourceFile:81) [minecraft_server.15w43c.jar:?] at j.a(SourceFile:64) [minecraft_server.15w43c.jar:?] at lb.a_(SourceFile:588) [minecraft_server.15w43c.jar:?] at nd.run(SourceFile:80) [minecraft_server.15w43c.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
Yup, present in 15w44a
Yup, 15w44b
Yup 45a
47a. YupOops.. 46a
still present in 16w07a
Affects 16w07b
Affects 1.9-pre1
affects 1.9-pre2
affects 1.9
Same issue here on a world that has been previously running snapshots
the server is running in the background, just the logging engine, log4j, seems to not be able to read the config file in the jar, so it doesn't write anything to the console or latest.log
sounds like your Cmd key is pressed, is there a cat on your keyboard?
Affects 18w11a.
Affects 18w16a
Uploaded a crash log
The world is 2.23 GB, I'd rather not post it publicly, but I can provide a link in private.
I have removed the datapacks from the world referenced in
MC-135231and it still crashes.I ran into this today on 1.15.1, banners on edges can't be marked.
Can we get a confirmation and an affects 1.15.1 please?
Affects 1.15.2 Pre-Release 1
Affects 1.15.2 Pre-Release 2
This affects 1.15.2
Affects 20w09a
Yup, affects 20w11a
Affects 20w13b
Affects 20w14a
Affects 20w15a
This is fixed with 1.14.60 on iOS 13.4 iPhone X using an Xbox one controller. I was able to assign these buttons and use them.
Affects 20w16a
I agree. Oh and affects 20w17a
Affects 20w22a
Affects 1.16-pre1
affects 1.16 Pre-release 3
affects 1.16 Pre-release 8
Affects 1.16 Release Candidate 1
Affects 1.16.2 Pre-Release 1
Affects 1.16.2 Pre-release 2
affects 1.16.2 Release Candidate 1