sancarn

I have agreed that with @unknown that this post should be transferred to her as I am no longer active on Mojira. Thanks

This is simply the hashset at work and I believe it is intended (no idea why but whatever...)

@Scott R. Godin - Why not use the spawn command to spawn entities in minecarts? I assume that's what you want to do 🙂

@Boompoet - What's standard? And how did it fail? If your droppers stopped working then file a bug report. There is no reason for a dropper elevator to fail except from how you wired it.

@Boompoet - Not really true... Dropper elevators don't fail at all. And if you have large volumes of items then you just need to increase the number of dropper elevators you're using 🙂.

It doesn't particularly matter if this remains this way it's just not ideal and will break many people's worlds 🙂

It's not "unfixable" as Panda has showed... and has even done himself (he fixed it on his own in the video you probably didn't watch...)

That being said there is very good reason for this to be fixed. There have been multiple occasions as a map maker that I have needed an invisible mob of any size to detect player clicks for instance. The main thing to remember is slimes are exceptionally good for map making because of the fact they can be any size. That is so powerful and the only problem at the moment is you can't use them... Because whenever it gets near a player the player dies... Not great as a map maker.

Also might I just say, it doesn't make any sense. Every single mob does damage through AI except slimes... noAI stops every mob damaging you... except slimes. For consistency this should be implemented. The fact that many people have suggested it just goes to show that even though it does not fit to mojang's definition of a bug, to the rest of the community it is. Therefore, at least in my opinion, it should be fixed or another work around added.

@Djfe kinda the good thing about minecarts is the custom rotations.

I'm curious as to why this is intended behaviour?

@Galaxy_2Alex, Yes. This is still an issue

Okay perhaps not a feature but it's working as intended. The position of the player is set to the position of the enderpearl. That's what the enderpearls do still.

Ceilings aren't garunteed death if you use a single enderpearl and it is your own fault if you use multiple, get stuck in a wall and die.

Enderpearls aren't unusable/useless if you know how to use them and this brings far more uses than it does otherwise. Like for example teleporting above bedrock in the nether and allowing you to get through, otherwise impassable regions.

This is a feature request more than a bug report. The enderpearl teleports you to it's own location. Since the enderpearl is smaller than the player the player gets partially stuck inside the block they are teleporting to. If the player crouches he will be stuck in the block. This is a feature of the game and is programmed this way.

This is more of a feature request and should be posted on the official minecraft suggestions reddit here: www.reddit.com/r/minecraftsuggestions

This is basically the same issue as this: MC-44780

The 'issue', if it isn't a feature, is chunk loading is now based on view/render distance and Mobs don't spawn in unloaded chunks.This is most likely a feature but it's not in any change logs...

This is because the world beyond the far lands is still generated beyond the wall, it's just not rendered. However rendering from the map comes straight from the map-generation/decoration code.

The far lands are meant to be hard to get to anyway so there really would be no need to fix this bug. The bug, I believe, will be unfixable with the current engine. If maps were to use rendering data they would be incredibly laggy, I think.

Well by that token these:

https://mojang.atlassian.net/browse/MC-15515
https://mojang.atlassian.net/browse/MC-1004

shouldn't be classed as bugs. For the very reason that you need mcedit to create spawners which spawn potions and custom mobs. You need mcedit or other NBT editors to create custom potions. These 2 bugs were also 'forcing' the game to do something that it wasn't designed to do. So by that token they should not have been classed as bugs and they should not have been 'fixed'.

However they were... So your logic doesn't follow through.

P.s. you are also not modding at all... You are changing the block id of the sand entity. That is NBT data editing. That hasn't got anything to do with mcedit. MCEdit just makes the spawners to make these sand entities with the edited NBT data spawn. The structure spawners do not force the game to do anything unusual.

Like healing potions don't normally give you 20 hearts of health back, sand entities don't normally turn into stone. However if you modify the NBT data of the sand or the potion you can change it such that it will do these things. This is not modding. If anything these are not bugs as the NBT data has been allowed, by Mojang, to be edited since Dinnerbone implemented this as a feature.

That's the thing though. Sand entites are coded to transform, when they land, into a block of a certain ID value. Minecraft is designed to allow this. The fact that it may not be possible in survival doesn't have much standing since there are many things which aren't obtainable in survival. You have to remember the structure spawners do not force the game to do anything unnatural or magical. They do not exploit a bug, but a feature that was added by DB. It is perfectly natural for a sand entity of ID value 1 to turn into stone when it lands.

Equally it should be perfectly natural for a sand entity with ID value 36 should turn into block 36 when it lands. This is all within the constraints of the code. There's no modding required for this kind of thing to happen.

No your not getting the point. Falling sand entities CAN and DO turn into other blocks.
http://www.youtube.com/watch?v=G4IdOzIwZDI
Watching that will show you that minecraft does support sand turning into other blocks. You will see that here falling sand entities are created which turn into stairs etc. However the only block that doesn't do this is block 36. Sand entities can turn into every block except for block 36. Block 36 is an exception therefore this has to be classed as a bug.

There currently isn't any implementation for thrown potions to instantly change what they are. If they had implemented a way to throw a splash potion of poison and for it to turn into a splash potion of regeneration in mid air you'd expect to be able to do the same thing but with damage and health potions right? If you couldn't you would naturally class it as a bug.

This is the same situation here. If structure spawners works for sand, stone, sponge, chests, furnaces, bedrock... you would expect it to work for block 36. It doesn't and so it should be classed as a bug.

By 'standard features' what do you mean exactly? An Health potion with strength 5 cannot be spawned in naturally in a world. The maximum strength is 2.

"you basically telling Minecraft to act in a way its not meant to." Well... no. I'm telling minecraft to create a sand which will turn into a certain block id. This itself is something which doesn't happen naturally yet this was added as a feature. A special case of the feature that doesn't work is still known as a bug right?

Just because it is a very special case doesn't necessarily mean it should be ignored and classed as "working as intended". The issue is not resolved either and I don't really see why it should be classed as resolved... =S I must be missing something extremely obvious here?

Wait....
https://mojang.atlassian.net/browse/MC-15515
https://mojang.atlassian.net/browse/MC-1004

Both of these reports require external 3rd party tools like MCEdit yet they were classed as bugs, not suggestions, and they were fixed and ultimately the bug report was resolved. Yet now you are telling me this bug doesn't apply because it requires MCEdit and custom spawners? I cannot see any sense in that... You can't say it is a bug once when previously it has been classed as a bug!

Direct quotation from the report:
"Open MCEdit and use the Change Spawners filter..."

and another

"The ability to set these properties on spawners was a deliberate feature in 1.4.
If a feature doesn't work as intended, that's a bug."

Wait... Structure spawners are a feature. This is a bug to that feature. This is a bug. NOT a suggestion.

Well it was worth a shot =)