MC-4433Fallingsand spawners failing to save properly, and causing crashes
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.
Environment
Windows 7, Java V7
Linked Issues
is duplicated by3
Created Issue:
Fallingsand spawners failing to save properly, and causing crashes
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 pandemoniumWhat I think it is, is that the game fails to save the attributes of the spawner for some raisin.
This is most disconcerting.
Environment
Windows 7, Java V7
Attachments2
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adams
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
Not a duplicate of MC-4433.
You've simply managed to create a FallingSandSpawner with an invalid EntityID:
-- Entity being rendered -- Details: Entity Type: FallingSand (pw) Entity ID: 64683 Name: Faldende blok
Remove it, and your world is usable again.
You have placed FallingSandSpawners with an invalid ID:
-- Entity being rendered -- Details: Entity Type: FallingSand (pw) Entity ID: 10336477 Name: Falling Block
Nevertheless a duplicate of (unmodded) MC-4433 (and already fixed)
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Well that's a disappointment. I remember that external editing used to be at least somewhat "supported" when it comes to bugs (e.g. MC-4433), and not having access to these values causes the loss of quite some custom map and gameplay potential.
In either case, if there's no point in storing the data as it's regenerated on login anyways, then it's wasting disk space (abiet little).
You did it again:
Can you read my whole post, please?
I did.
Tested your world.
Got
The point is, it works properly in 1.4.5, however it does not in 12w49a.
Which raisin?
I got Entity ID 46872 in my crash in 12w49a.
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.
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?
Regression
see
MC-7496re-regressed