1. Drop an item, any item you want
2. Go in MCEdit and use Sethblings filter to make that item a spawner that spawns it
3. See it crash your game upon entering
There is nothing to say more about this other than you'll get this only if you are a map maker.
Linked issues
Attachments
Comments 11
I've experienced this before, but it only happened when I combined a few spawners.
I have attached the crash report. And how can this be a duplicate? I was the first to even talk to Dinnerbone about this and he was the one who told me to post it here. And I even searched for "spawner crash" and got nothing relevant :/
Also how can THIS be a duplicate of something that was posted after this was made? Please do make sense :I
Yes I had the same problem, but only for this snapshot. For now you can just downgrade to 06a. This snapshot is just a little bit of bug fixes.
Yeah, but it needs to be fixed because if this persists in next snapshots it will remain in 1.5 too, which will mean my whole map will be broken.
The problem may be in Sethbling's filter, not in the spawners themselves. I will check the crash report more thoroughly though.
So the error was this:
-- Entity being saved --
Details:
Entity Type: Item (qw)
Entity ID: 283
Entity Name: ~~ERROR~~ NullPointerException: null
Entity's Exact location: 0.00, 0.00, 0.00
Entity's Block location: World: (0,0,0), Chunk: (at 0,0,0 in 0,0; contains blocks 0,0,0 to 15,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Entity's Momentum: 0.00, 0.00, 0.00The error was the entity name. According to Sorin, dinnerbone confirmed this, so it probably isn't just a problem with Sethbling's filter.
@Sorin Iliuta
I have attached the crash report. And how can this be a duplicate? ...
Also how can THIS be a duplicate of something that was posted after this was made? Please do make sense :I
If you create a low quality ticket without regarding the guidelines then it may be resolved to a later created, better quality ticket.
And please stop complaining here and in MC-9788 about being flagged as duplictate, this is a bug tracker and no competition about being the first one to post a specific bug.
Well when I am being told it's a duplicate after searching to see it's not it bugs me a lot. Yes, I mainly came here because I want this to be fixed, because that's why this is here and right now I don't care if it is or not a duplicate, but more if it will be fixed. But it bugged me at that time for it becoming a duplicate of something made after this. Doesn't matter anymore now.
confirmed for 13w07a
True Story Confirmed for 13w07a
Please attach the crash report.