Alfie Leadbitter

I'm having a similar issue. I had some oak planks that were directly in contact with a burning netherrack block and the fire didn't spread. When I set fire to the planks myself, it spread fine, and when I replaced the planks, they still wouldn't set alight from the netherrack. I can only assume this is related.

I have the same farm (though incomplete at the moment and without pigmen or golems) and the same problem. Possibly worse, as I haven't had a single spawn at all

I'm having the same issue, I think. I started building a pigman spawner above the bedrock layer, but nothing has spawned on it at all. I killed all entities (which also destroyed all my decorative item frames and armour stands in the overworld, so thats a little annoying) and it didn't change anything. I'm playing in 18w31a

Disregard this. turns out this was reported a bunch of times in other ways and has already been fixed in the current version

This issue has persisted into 1.13's full release for me. Danny Kessler's solution didn't work for me

Oh damn. Apologies, but I just realised i was making the recommended NBT edits to a similarly named back up world. Made the edits to the world that was crashing and it worked.

Added just now.

Oh, sorry. My crash reports gave the same "Exception Ticking World" and "Bound must be positive" remarks, and the nature of the crashes was similar, so I thought I was having this issue.

I didn't want to make an extra thread in case it was a duplicate.

Getting the same problem here. In pre-8, I went through a nether portal to the overworld, and it crashed. It reopened fine, then some time later the same thing happened, nether to overworld, crash. When I was returned to the launcher pre-9 was available, so I downloaded that and reopened the world, assuming it would be fine like last time, but now that world crashes upon opening. I tried the solution proposed by HurricanKai, but turning mobSpawning to false didn't work.

Thank you, Kraif. Couldn't find that when I searched, for some reason.