Piotr Petrus (ridddle)
- ridddle
- ridddle
- Europe/Stockholm
- Yes
- No
Enter preset:
2;7,2x3,3;1;villageVillage
rs won’t generate farmers.The same but with grass instead of topmost dirt (classic superflat) will work just fine.
[11:30:29] [Server thread/INFO]: ridddle left the game
{/code}
q: Saving entity NBT
at ru.e(SourceFile:1149)
at ru.d(SourceFile:1116)
at arn.a(SourceFile:210)
at arn.a(SourceFile:99)
at nl.b(SourceFile:160)
at nl.d(SourceFile:219)
at nm.c(SourceFile:145)
at net.minecraft.server.MinecraftServer.v(SourceFile:519)
at mm.v(SourceFile:264)
at net.minecraft.server.MinecraftServer.u(SourceFile:461)
at net.minecraft.server.MinecraftServer.run(SourceFile:377)
at mc.run(SourceFile:647)
Caused by: java.lang.NullPointerException
at agx.j(SourceFile:115)
at agy.a(SourceFile:125)
at yw.b(SourceFile:212)
at ru.e(SourceFile:1137)
... 11 more
q: Saving entity NBT
at ru.e(SourceFile:1149)
at ru.d(SourceFile:1116)
at arn.a(SourceFile:210)
at arn.a(SourceFile:99)
at nl.b(SourceFile:160)
at nl.a(SourceFile:191)
at nm.a(SourceFile:655)
at net.minecraft.server.MinecraftServer.a(SourceFile:295)
at net.minecraft.server.MinecraftServer.u(SourceFile:479)
at net.minecraft.server.MinecraftServer.run(SourceFile:377)
at mc.run(SourceFile:647)
Caused by: java.lang.NullPointerException
at agx.j(SourceFile:115)
at agy.a(SourceFile:125)
at yw.b(SourceFile:212)
at ru.e(SourceFile:1137)
... 10 more
q: Saving entity NBT
at ru.e(SourceFile:1149)
at ru.d(SourceFile:1116)
at arn.a(SourceFile:210)
at arn.a(SourceFile:99)
at nl.b(SourceFile:160)
at nl.d(SourceFile:219)
at nm.c(SourceFile:145)
at net.minecraft.server.MinecraftServer.v(SourceFile:519)
at mm.v(SourceFile:264)
at net.minecraft.server.MinecraftServer.u(SourceFile:461)
at net.minecraft.server.MinecraftServer.run(SourceFile:377)
at mc.run(SourceFile:647)
Caused by: java.lang.NullPointerException
at agx.j(SourceFile:115)
at agy.a(SourceFile:125)
at yw.b(SourceFile:212)
at ru.e(SourceFile:1137)
... 11 more[11:30:29] [Server thread/INFO]: ridddle left the game q: Saving entity NBT at ru.e(SourceFile:1149) at ru.d(SourceFile:1116) at arn.a(SourceFile:210) at arn.a(SourceFile:99) at nl.b(SourceFile:160) at nl.d(SourceFile:219) at nm.c(SourceFile:145) at net.minecraft.server.MinecraftServer.v(SourceFile:519) at mm.v(SourceFile:264) at net.minecraft.server.MinecraftServer.u(SourceFile:461) at net.minecraft.server.MinecraftServer.run(SourceFile:377) at mc.run(SourceFile:647) Caused by: java.lang.NullPointerException at agx.j(SourceFile:115) at agy.a(SourceFile:125) at yw.b(SourceFile:212) at ru.e(SourceFile:1137) ... 11 more q: Saving entity NBT at ru.e(SourceFile:1149) at ru.d(SourceFile:1116) at arn.a(SourceFile:210) at arn.a(SourceFile:99) at nl.b(SourceFile:160) at nl.a(SourceFile:191) at nm.a(SourceFile:655) at net.minecraft.server.MinecraftServer.a(SourceFile:295) at net.minecraft.server.MinecraftServer.u(SourceFile:479) at net.minecraft.server.MinecraftServer.run(SourceFile:377) at mc.run(SourceFile:647) Caused by: java.lang.NullPointerException at agx.j(SourceFile:115) at agy.a(SourceFile:125) at yw.b(SourceFile:212) at ru.e(SourceFile:1137) ... 10 more q: Saving entity NBT at ru.e(SourceFile:1149) at ru.d(SourceFile:1116) at arn.a(SourceFile:210) at arn.a(SourceFile:99) at nl.b(SourceFile:160) at nl.d(SourceFile:219) at nm.c(SourceFile:145) at net.minecraft.server.MinecraftServer.v(SourceFile:519) at mm.v(SourceFile:264) at net.minecraft.server.MinecraftServer.u(SourceFile:461) at net.minecraft.server.MinecraftServer.run(SourceFile:377) at mc.run(SourceFile:647) Caused by: java.lang.NullPointerException at agx.j(SourceFile:115) at agy.a(SourceFile:125) at yw.b(SourceFile:212) at ru.e(SourceFile:1137) ... 11 moreThey just keep coming, repeatedly, even after I /save-all. Reboot helps.
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnCount:1,SpawnRange:4,SpawnData:{Size:3},RequiredPlayerRange:64,Delay:10,MinSpawnDelay:10,MaxSpawnDelay:11,MaxNearbyEntities:1}Even reduced to
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime}Just won’t spawn a single Slime. Difficulty is not Peaceful, I double checked.
Video proof:
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnCount:1,SpawnRange:4,SpawnData:{Size:3},RequiredPlayerRange:64,Delay:10,MinSpawnDelay:10,MaxSpawnDelay:11,MaxNearbyEntities:1}
Video proof:
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnCount:1,SpawnRange:4,SpawnData:{Size:3},RequiredPlayerRange:64,Delay:10,MinSpawnDelay:10,MaxSpawnDelay:11,MaxNearbyEntities:1}Video proof: http://usetapes.com/v/TQQ1qEYHiC
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnCount:1,SpawnRange:4,SpawnData:{Size:3},RequiredPlayerRange:64,Delay:10,MinSpawnDelay:10,MaxSpawnDelay:11,MaxNearbyEntities:1}
Also, I am really not content with trigger-happy behavior of moderators here. You could at least wait for my one response before marking the report as invalid. By doing so, you’re potentially allowing Minecraft 1.8 to be released with a show stopping bug for a fraction of Mac users.
1. By “farmers” I mean all brown robed villagers (ID 0).
2. This doesn’t affect villages in spawn chunks.I’ve tested this on at least three randomly generated superflat worlds without any preset customization.
Traveling through a superflat world and causing village
rs to generate makes all farmers who are supposed to be spawned in them pick one of other IDs. This makes the whole village seem infested with one type of villager, while in fact Farmers are supposed to be the majority in any village.I’ve personally seen villages swarming with white robed Villagers, I’ve seen silver apron Villagers and I’ve also seen black apron Villagers. I haven’t personally confirmed villages with purple robes (Clerics).
I used to have doubts about this being a random occurrence. I’ve seen it too many times now to be something on my end.
1. By “farmers” I mean all brown robed villagers (ID 0).
2. This doesn’t affect villages in spawn chunks.I’ve tested this on at least three randomly generated superflat worlds without any preset customization.
Traveling through a superflat world and causing villages to generate makes all farmers who are supposed to be spawned in them pick one of other IDs. This makes the whole village seem infested with one type of villager, while in fact Farmers are supposed to be the majority in any village.
I’ve personally seen villages swarming with white robed Villagers, I’ve seen silver apron Villagers and I’ve also seen black apron Villagers. I haven’t personally confirmed villages with purple robes (Clerics).
I
used to have doubts about this being a random occurrence. I’ve seen it too many times now to be something on myend.1. By “farmers” I mean all brown robed villagers (ID 0).
2. This doesn’t affect villages in spawn chunks.I’ve tested this on at least three randomly generated superflat worlds without any preset customization.
Traveling through a superflat world and causing villages to generate makes all farmers who are supposed to be spawned in them pick one of other IDs. This makes the whole village seem infested with one type of villager, while in fact Farmers are supposed to be the majority in any village.
I’ve personally seen villages swarming with white robed Villagers, I’ve seen silver apron Villagers and I’ve also seen black apron Villagers. I haven’t personally confirmed villages with purple robes (Clerics).
In all affected villages there wasn’t a single one Farmer (ID 0) present.
I used to have doubts about this being a random occurrence. I’ve seen it too many times now to be something on my end.












Update: Re-downloading server jar which fixed debug spam in console helped the issue. Can be closed.
In my test world I found other villages with Farmer type villager but all of them were Shepherds.
Still, something is buggy here.
Hmm I can see how this is actually a suggestion.
However, the trade GUI item has a normal Minecraft item count and standard black floating label. Isn’t it the same as any other inventory slot just that you cannot directly edit?
Confirmed, this happens only in 1.8 snapshots, did not happen in 1.7.
I showed a pen with water to make sure that chicken won’t glitch through the fence. This experiment can be recreated with any other pen type, the chicken will always despawn as though it was a monster.
Tails: Please elaborate or add a source saying it works as intended. It’s an animal and animals don’t despawn with range.
Oh, that’s why. This seems weird because 1) chicken riders are very rare, 2) chickens can wind up underground on their own, possibly creating the lag too.
I think it would be just more logical to create a second egg version with damage value 1, which cannot be picked up by mobs. Or prevent mobs from picking up eggs whatsoever. Currently this despawn mechanic prevents resource-scarce worlds like Skyblock or superflat maps from accessing one more renewable resource.
Thank you for explaining though.
Is it possible that slime chunks affect this? I made a void map to make sure nothing else interefered with mob spawner mechanics and could not get any spawns:
http://usetapes.com/v/fghpJAKf2e
Yes! It definitely depends on slime chunks! Used my world’s seed and http://chunkbase.com/apps/slime-finder, created a spawner in a slime chunk and boom, slimes started spawning like mad.
Proof: http://usetapes.com/v/TQQ1qEYHiC
Can we update the issue or should I make the new one?
I figured out what this is and I’m sorry for wasting your time: it is the issue with chunks not rendering. Climbing that tree revealed leaves which were simply in a higher chunk which didn’t render.
I don’t understand how this can be seriously flagged as Works As Intended.
You’re introducing a behavior which cannot possibly be forseen by players. Consider this:
1. Fill every slot in your inventory with cobblestone but one
2. In that empy slot put a stack of empty buckets
3. Start picking up lava or water
What happens is this: you start dropping lava/water buckets because they can’t fit in the inventory. You don’t destroy 15 buckets to get 1 full bucket.
So following this logic, furnace should drop 15 buckets to the ground and leave 1 water bucket in fuel slot.
Can I respectfully ask why? I have both Java 6 (supplied by Apple through Software Update) and Java 7 installed through Oracle’s JDK installer. Minecraft used to run swimmingly until I installed Pre Release 2 which caused two black outs. I didn’t change Java version, but Minecraft did install new lwjgl version. How is this remotely my fault?
Edit: On top of that, your link is just for OS X 10.5. I run 10.9 and the tutorial you linked is 5 years old.
I Googled for a way to force Minecraft to use Java 7 and it seems to be stable now.
I still insist that it is a problem with Minecraft 18 pre-2 on OS X because:
1. Even the newest version of OS X (10.9) ships with Java 6
2. Minecraft 1.7.10 and even snapshot 14w34d caused no issues when run under Java 6
Conclusions:
1. Something changed between last snapshot and pre-release, possibly unstable lwjgl seeing as .minecraft/libraries/ has new folders called 2.9.2-nightly-20140822
2. Minecraft 1.8 might be broken for a fraction of Mac user base – they will most likely not know to seek help by downloading Java 7 from Oracle’s servers.
I think it’s imperative to get this information out to developers. They might not know how to fix it immediately but they should be aware of this issue which seems to have resurfaced. You closing the ticket automatically with your first
commandcomment makes this impossible.That turorial is heavily outdated. New OS X versions are only distributed via Mac App Store and Java 6 is updated through the same App Store mechanic, system-wide. My Java 6 is up to date, because it’s a version provided by Apple. If a user wants to install Oracle Java, they can only install Java 7, as Oracle’s Java 6 is no longer supported for OS X. Which brings us back to my original issue with your suggestion: it’s outdated.
Still happens with 1.8-pre3
Attached files to the issue.
Exactly the same thing happens no matter the launcher version, non-dev or dev – and those files seem to agree.
Seems so. It stopped hanging on launch and I can’t seem to break it anymore, intentionally or not. Thanks, D!