So, trying my best to run a Vanilla server, but at every point, Mojang has seemed to make things very difficult and finds ways to make something a 10 step process, instead of 1 step, as it should be.
For example, I am trying to setup a NPC to sell custom mob spawners (spawn horses, sheep, villagers, etc.). Partial code is below...
tag:{
BlockEntityTag:{
SpawnCount:4,
MaxNearbyEntities:6,
SpawnRange:8,
Delay:60,
MinSpawnDelay:180,
MaxSpawnDelay:1800,
RequiredPlayerRange:16,
EntityId:Cow,
SpawnData:{id:Cow}
}
The Custom Villager sells these just fine, and they work just fine... as long as you are a Server Operator... SERVER OP OR NOTHING! When a regular player places a spawner, it ignores all tag data and places as a Pig Spawner every time! I mean, why Mojang... WHY!? Why do you say we can have all this cool stuff to play with, but then, LIMIT EVERYTHING!
If I set up a NPC to sell a Mob Spawner to players using custom settings, ALLOW THE PLAYERS TO USE THEM! Seriously, I'm losing so much faith in Mojang, when all these features seem to just, not work. Seems to use half of any custom code in this game, you MUST be a Server OP... it's just... it just doesn't make ANY sense! I mean, sure, making the code and putting it in, you need OP, but using something created by an OP, you ALSO need OP to use???? NO SENSE!
Is this a bug Mojang? Because the code works. Why you wouldn't allow players to put one of these down with the Tags in place is beyond me, especially since players cannot normally obtain these!!
Please fix, because this is an issue... and a long standing one from my understanding, and it is a completely broken feature.
Signed,
A Currently Hindered Server Admin, Waiting For Mojang To Fix Some Code
Comments 8
How exactly would a "non-mod" copy command blocks? A regular player not only does not have access to command blocks, but they also cannot enter code into command blocks. I don't understand your response.
CRT+pick block in creative copied all that data, and puts it in the BlockEntityTag, the same tag you use.
For server sequrity the tag is blocked out, as I mentioned above.
This also applies to survival players, as creavtive players can just give the item+nbt to a player, and they could break everything with it.
Imagine a player modding an item in their inventory that is a spawner that spawns FallingSand that turns into command blocks running /kill @e. It is a security issue. This is why dispensers were changed to not place a command block, because somebody could mod a command block into their inventory that contains such data without being OP'd.
My server, my security. Thanks for the thought, but I would like to have this option, without Mojang dictating exactly what is in my best interest.
This site is for bug reports only. For feature suggestions or changes please see: Minecraft Suggestions on Reddit.
Kumasasa, you sure handle issues very cleverly. Take valid points about broken features and just mark them as resolved. Seriously, it shows how much you actually care about this game.
Since you are directing me to Reddit tho, I guess I will tell it how it is over there, about the constant incompetence of Mojang Dev's and crew handling such issues as these.
https://www.reddit.com/r/minecraftsuggestions/comments/45vdp7/at_war_again_only_ops_may_use/
This is very likely for server sequrity implemented, as the block entity tag also gets used by other stuff, eg command blocks, this is very likely so a non mod can't go around and copy command blocks all over the place.
Because of that the BlockEntityTag in general is completely blocked for non ops.
I'd rather say this is a feature/change suggestion, which belongs to the reddit