Andy (Romaq) Smith

MCPE-47354 may be a duplicate, or at least related to this. 1.12.0, players on my BDS server commented a villager "rerolled" after being tagged & traded with multiple times. It's possible we fouled up. We are going to try making https://youtu.be/4h8Yifosh7U SilentWhisper's Trading Hall where a mistake will be less likely, and the villagers won't be moving to confuse things or break the work-station connection. ... Just now found another "rerolled" villager. This is in an Iron Farm where the villagers circulate, and the work-station link might be an issue, or lack of pathfinding to a bed.

If we can verify this bug from a "solid" trading farm with the caution of doing some trades to lock in from rerolling, it would help a good deal to pin this thing down.

EDIT: Robin is on my server, the above is her direct report on this.

May be related to MCPE-41337 (or duplicate), but note you MUST do some trading to "lock in" the trade or the villager may "reroll". At the moment I'm explicitly looking for, "We labeled, did some trades, thought it was locked in, and the villager rerolled anyway." We MAY have been mistaken, so we are looking to try https://youtu.be/4h8Yifosh7U which will pin our villagers in place and make mistakes less likely to happen.

Duplicate of MCPE-30863, flagged as "postponed", this falls into the category of, "It's not a bug, it's a Platform Specific Feature!" Please post in https://feedback.minecraft.net/hc/en-us/community/topics/360001191251-Parity this feature, and comment the link when it shows. Notch knows the Devs must be tired of me hitting the #MinecraftParity drum. 😞

This problem directly relates to MCPE-49939 with some hidden data tag as a "root" cause. These two bugs should be looked at together so the "root solution" fixes them both. It may also be useful if anyone can verify items affected by this bug affect villager trades, and reported accordingly on the "trades" issue.

Same problem. If I "/give" myself stone with no data/ no json, the trade works just fine. The "work-around' for people with cheats (but no desire to ACTUALLY cheat) is to dump cooked stone, replace with that exact amount of "given" stone. I suspect the villager is rejecting some "data tag" on cooked stone. I've not looked to see what data tag is on cooked stone, perhaps someone can do that and verify. At this time, I'm not aware of any other trade refusals than the cooked stone.

It could be as simple as having a data tag of "0" vs. a data tag of "NULL".

This was just pointed out to me by a player... "silked stone" vs. "smelted cobble-stone" do not stack. So the same "hidden data tag" makes this bug related to MCPE-44649, and should affect the same items. Both bugs should be looked at for solving the root data tag problem.

Same issue on a private LAN game, all the same as reported here. I have skin abrasions from my wife chewing on my arm on how armor and bows are not dropping. I had to look this bug up to save my arm from further damage. 😞

Yup, and I see a Villager-splosion in your near future in that crop cage. 😞

Ok, we'll have to look at the food then. We were trying to be "nice" giving the villagers garden areas, but it would appear having farms within the village contributes to this problem. I'm the admin, I just don't know how to /kill @e[type=Minecraft:villager,nbt=
{profession:unemployed-something-something-goes-here}] to kill the excessive unemployed among them. While this doesn't actually "help" with the bug, my hope is to mitigate the 400+ unemployed villager problem tied into this bug.

Another note with this specific to 1.14.1, I believe Villagers were removed from the Passive Mob Cap, but if there isn't another cap Villagers fall under, guess what? You have an EXPLOSION of villagers as there is no longer anything to stop infinite breeding if you have the conditions that allow it. Yay!

The server admin to which she refers is still flailing trying to figure out how to excise ONLY the unemployed villagers, but I'm coming pretty close to "kill them all and let's consider shutting down the 1.14.1 server and playing some other version for a while." This has been active since MARCH? Seriously?

They are 1.13 "dedicated" packs. I'll search for this and update privately, then watch for the 1.14 Hermitcraft Vanilla Tweaks update. 🙂 Thank you! I'd never have come up with that one.

D'oh! I didn't think of that.

Thank you VERY Much for testing it out. The "Gold Standard" test would be to compare a good size flying machine. I sure wish I could pull that off, I may have to build one and see how laggy it goes on a farm in the current Snapshot. That will take me some time.

I filed MC-138834, looks like it should be here. Snapshot 18w44a, heavy on resource packs, pure Vanilla Server. I have crash reports I can repost here if desired, but this bug seems too random for me yet to really pin it down so I can dump texture packs and KNOW they are the problem.

The world upload is over 10Mb, so it won't go. The list from bottom to top:

PureBDCraft 256x MC113-r5
BDCraft Sounds MC113
PureBDCraft Noteblock English MC113
PureBDCraft More3D Block MC113
PureBDCraft Damaged Items MC113
age 25 kelp tops (from Xisumavoid's Vanilla Tweaks)
PureBDCraft Font MC113
wrenchrp (from Xisumavoid's Vanilla Tweaks)

If I get this error on a more regular basis, I'll start dumping texture packs. I dumped a screenshot showing what memory I'm using, 4G setting. I'm guessing I should actually lower it by roughly half, I certainly don't need to add more mem. 🙂 MC-138539 and MC-137795 are currently causing more (and easily replicable) issues. We can hold on this to see if someone else reports this problem. Otherwise, I'm inclined to suspect the stack of texture packs until I can more easily replicate things, dump texture packs, do it again (or not).

I can in its current state. Unfortunately I'm not getting that specific crash message again anywhere I can pin down, and it hasn't happened again. So it's going to be a real bear trying to pin it down. It could be the BDCraft resource pack, 1.13-R5 or one of the BDCraft add-ons. And if I don't get that crash again, I've no clue what to tell you. 😞 I'll get the backup going and start down/ uploading after I send this, then edit this message that I've sent.

That crash just happened. I'm still getting together the world backup from a remote server.

Thank you. Hopefully we'll have someone able to verify if the new lighting engine can deal with opaque pistons without the pain 1.13 Snapshots had. 🙂 I can't build one, so proper testing is out of my skill set.

We are getting cooked meat using unenchanted swords on our server. We are using some of Xisumavoid's data packs and a few custom, but nothing that should touch mob drops.

A recent crash is enclosed unrelated to the "cooked meat" issue. Let me know if you want me to force a crash or send a copy of any "interesting" data packs.

Confirmed with a remote server, 18w44a. At least, "Confirmed until I looked up this as a bug." Now it's working properly. Stupid bugs and their bug-report detectors. This may be an "intermittent" thing with quirkiness in reproduction, but it is on a server with 3 people on it, only 2 in the same general location. Slow crops 30 min. ago, now crops are fine after reporting. As reported, affects leaf decay and other things affected by /gamerule randomTickSpeed.

Ok, out of Spawn Chunks, we set randomTickSpeed to 999, no effect. As soon as my wife and I got back to our base in spawn chunks, everything sprang up and it is evident the 999 randomTickSpeed was working. This may have something to do with the status of loaded chunks. The third person (jorispiepo) was away from our location the whole time, but online.

My understanding is that the lighting engine is being worked on to "solve" the lag issues introduced by having, for instance, pistons being opaque. I do understand what I'm seeing in Meri Diana's images, but could we have a specific use case such as https://youtu.be/7eWWl-tIWvE "1.13 News: Pistons And Slimeblocks No Longer Transparent" by ilmango?

Per https://minecraft.net/en-us/article/minecraft-snapshot-18w43a "New Light engine!" To my way of thinking, I don't care so much if an armor stand is "lit" or "unlit" within a piston. I care that a relatively simple flying machine used for cane and bamboo farms shuts my server down for lag from rendering. So ilmango's video (at least of a simple flying machine) compared with MC 1.13.2 would be more useful to evaluate, "Is this really a problem now?" If my pistons are transparent when extended, I don't know why I'd really care. Hammering my server TPS over lighting, I'd care about a great deal.

This behavior appears to have been reintroduced with at least Snapshot 18w44a. I still get pushed out of the water, eventually, but it looks like it's back otherwise. 😞