[MC-4433] Fallingsand spawners failing to save properly, and causing crashes Created: 10/Dec/12  Updated: 03/May/17  Resolved: 15/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 12w49a
Fix Version/s: Snapshot 12w50a

Type: Bug
Reporter: Adam Lyon Assignee: [Mojang] Nathan Adams
Resolution: Fixed Votes: 0
Labels: crash, falling_block, save, spawner
Environment:

Windows 7, Java V7


Attachments: Text File crash-2012-12-10_00.49.10-client.txt     Zip Archive fallingsand test world.zip    
Issue Links:
Duplicate
is duplicated by MC-8646 Ladders behaving like Falling Sand Resolved
is duplicated by MC-4406 Fallingsand spawners crashing game Resolved
is duplicated by MC-4519 Random crashing w/ Rendering Engine o... Resolved
Relates
relates to MC-7496 every time I go into my map and goes ... Resolved
CHK:
Confirmation Status: Confirmed
Game Mode: Creative

 Description   

Alllllrighty then, I know that I've talked about FallingSand glitches before, but for real this time.

1. Download and open the test world
2. Fallingsand spawner should (sort of) work
3. save and exit
4. open the text world again
5. game crashes
6. cats and dogs in love
7. total pandemonium

What I think it is, is that the game fails to save the attributes of the spawner for some raisin.

This is most disconcerting.



 Comments   
Comment by Kumasasa [ 15/Jan/13 ]

re-regressed

Comment by Kumasasa [ 14/Jan/13 ]

Regression
see MC-7496

Comment by Adam Lyon [ 11/Dec/12 ]

Normally I would agree with you, but recently it was added so that you could modify the data of the spawner and spawn not just sand, but any block as a semi-feature. Why add a feature if you're just going to make it obsolete later?

Comment by Nerdyboy6057 [ 11/Dec/12 ]

Custom spawners are a very problematic element of Minecraft, as they usually require the use of third-party applications to obtain them.

Although it is apparent that Minecraft is very insensitive to third-party modifications and elements, the use of vanilla elements to illegitimately achieve something that is naturally occurring or pivotal is of a high risk. That is, spawners 'spawn' entities, but are intended to spawn naturally and to spawn mob entities. This means that it is not very much of a risk to create a spawner that spawns pigs, for example, but it is of risk to spawn 'artificial' entities. These are block entities that are only used by the game to represent something and are not an element in itself. Hence, without a solid element to cause something, artificially creating the cause of an event without raising it is very risky.

Comment by Anon Ymus [ 11/Dec/12 ]

I got Entity ID 46872 in my crash in 12w49a.

Comment by Anon Ymus [ 11/Dec/12 ]

Which raisin?

Comment by Adam Lyon [ 10/Dec/12 ]

The point is, it works properly in 1.4.5, however it does not in 12w49a.

Comment by Kumasasa [ 10/Dec/12 ]

I did.
Tested your world.
Got

Details:
Entity Type: FallingSand (px)
Entity ID: 14512

Comment by Adam Lyon [ 10/Dec/12 ]

Can you read my whole post, please?

Comment by Kumasasa [ 10/Dec/12 ]

You did it again:

Entity Type: FallingSand (px)
Entity ID: 65
Name: Falling Block

Generated at Sun Jan 12 12:04:33 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.