Great idea. I'm all in favor of making more adventure map tools.
I suggested two related suggestions:
Forcefield Block - Basically invisible bedrock, placeable in creative mode
Block X - A design it yourself block, allowing people to create blocks with any properties they want. You could create an invisible lightsource with that if you wanted to. Or disguise a light source as cobblestone or any other material.
I think an invisible light block is universally useful enough it should be added on its own too.
Hmm... Well they can still make the spawn limit to 1 but I see what you mean. But they only attack mobs/players and it would take a lot of work for a jerk to go through all that work.
And again the heads are a rare spawn.
It's a 2.5% drop rate. That be a low chance, but I can easily see people spending a couple hours to collect heads to play a prank. Especially if it's more than one griefer working together. Not to mention that I'm sure someone will design a trap to speed up head collection.
I can see plugins being made so the Wither can only be spawned in the Nether, though that idea should have never been spoken of in the forums! Dang a plugin designer better see my idea xD
Griefing in the nether would still be pretty bad. Imagine your complex fast-travel rail system getting messed up because some jerk releases 10 withers in the tunnels.
I haven't been able to find a thread about this yet, so sorry if this already a well trod topic.
Besides wither skull rarity, what prevents people from spawning the Wither as a griefing tool? What stops people from spawning a few Withers in a crowded area and then running away? Or from letting a Wither chase you through a city so it tears holes in all the buildings?
Another cool thing is that admins could use it to directly activate machines only they can control, almost like admin telekinesis.
For example, there can be an admin only jeb door they can control by typing /true 10. This temporarily opens the door and also powers a command block set to /false 10 to reset the system.
It's also good for automated redstone too. Machines and sensors (even a whole computer) can be linked across the world using this true/false system as a wireless radio.
Command blocks can achieve very powerful effects, but they're limited in knowing when to unleash those effects due to the natural limitations of redstone technology.
I suggest adding three new server commands to the game:
/true #
/false #
/iftrue #
The first two commands would allow you to do is designate any whole number as true or false (by default they would be false).
The iftrue command would only be useable by command blocks. What it would do is cause the command block to become strongly powered for one second, able to power adjacent redstone dust. But it would only become powered if the number it is set to is true.
For example, let's say you have an adventure map where certain doors throughout the world should only open after defeating a bunch of monsters in a temple far away in the mountains. At the back of the temple you could have a button linked to a command block set to /true 37. Then everywhere else in the world (and in other dimensions) you can have buttons linked to /iftrue 37 command blocks to open those doors, but not until the appropriate condition is met.
It's also worth noting that this would also allow wireless redstone between fully automated systems, without requiring any player input. The traditional problem with wireless redstone has been that the receiver isn't necessarily loaded. This solves for that by allowing the "receiver" to check if the appropriate condition is true or false whenever it next becomes loaded.
Also, if its visibility was based on texture pack you could make it visible as whatever you want. For example, you could make it appear like a translucent blue forcefield if you do want players to see it. Or you could even make it look like glass, but immune to breakage.
Supported, and since it's no longer being used, it can use the old beacon block texture when you're in creative.
One option is to simply leave it invisible by default, but let people change their texture pack so they can see it when necessary to build with it. In that case they could look like anything you want them to look like.
That might avoid any coding difficulty of having it appear differently depending on gamemode, which would be nice but isn't necessary.
Also, chunks load when they're still relatively distant from the player. So you don't need to apply updates to all of them at once. You could do them in some kind of sequence that's still fast enough to apply a change to everything before the player gets close.
I like it, but I think the pyramid should still require some valuable block in its construction. Using netherrack or soul sand is flavorful, but both materials are far too common for something this powerful.
Why should people in creative mode have to deal with the hassle of random chance enchanting?
I suggest adding an /enchant # # server command, which would enchant whatever tool or armor you currently have selected in your hotbar. The first number would correspond to a specific enchantment and the second number would indicate the enchantment level. You'd be able to pick the exact enchantment and level you want, and also add enchantments to already enchanted items.
There could also be a /disenchant # # command to remove specific unwanted enchantments from your currently held item, while leaving it untouched otherwise.
These instantaneous updates could work on a percentage system instead of using lots of individual block updates. For example, after X passage of time each wheat block would have a 40% percent chance of being loaded one stage further in growth, a 20% chance of being two stages further in growth, a chance of not having grown at all, etc. So that's just one update per block of wheat, not dozens or hundreds.
It might cause momentary lag for a giant wheat farm with thousands and thousands of plants. But it's a one time brief moment of lag, not like a redstone lag machine that keeps operating. And that lag means that your giant wheat farm can actually function instead of do nothing.
0
I suggested two related suggestions:
Forcefield Block - Basically invisible bedrock, placeable in creative mode
Block X - A design it yourself block, allowing people to create blocks with any properties they want. You could create an invisible lightsource with that if you wanted to. Or disguise a light source as cobblestone or any other material.
I think an invisible light block is universally useful enough it should be added on its own too.
0
It's a 2.5% drop rate. That be a low chance, but I can easily see people spending a couple hours to collect heads to play a prank. Especially if it's more than one griefer working together. Not to mention that I'm sure someone will design a trap to speed up head collection.
0
Griefing in the nether would still be pretty bad. Imagine your complex fast-travel rail system getting messed up because some jerk releases 10 withers in the tunnels.
0
Besides wither skull rarity, what prevents people from spawning the Wither as a griefing tool? What stops people from spawning a few Withers in a crowded area and then running away? Or from letting a Wither chase you through a city so it tears holes in all the buildings?
0
For example, there can be an admin only jeb door they can control by typing /true 10. This temporarily opens the door and also powers a command block set to /false 10 to reset the system.
0
5
I suggest adding three new server commands to the game:
/true #
/false #
/iftrue #
The first two commands would allow you to do is designate any whole number as true or false (by default they would be false).
The iftrue command would only be useable by command blocks. What it would do is cause the command block to become strongly powered for one second, able to power adjacent redstone dust. But it would only become powered if the number it is set to is true.
For example, let's say you have an adventure map where certain doors throughout the world should only open after defeating a bunch of monsters in a temple far away in the mountains. At the back of the temple you could have a button linked to a command block set to /true 37. Then everywhere else in the world (and in other dimensions) you can have buttons linked to /iftrue 37 command blocks to open those doors, but not until the appropriate condition is met.
It's also worth noting that this would also allow wireless redstone between fully automated systems, without requiring any player input. The traditional problem with wireless redstone has been that the receiver isn't necessarily loaded. This solves for that by allowing the "receiver" to check if the appropriate condition is true or false whenever it next becomes loaded.
1
0
I tried to do some similar things in this suggestion, basically to create a poor man's version of your tagging: http://www.minecraftforum.net/topic/1441922-server-command-targeting-helditem-hasitem/
The idea is you could target specific items, instead of naming players, which would allow you to target specific players without knowing their names.
0
One option is to simply leave it invisible by default, but let people change their texture pack so they can see it when necessary to build with it. In that case they could look like anything you want them to look like.
That might avoid any coding difficulty of having it appear differently depending on gamemode, which would be nice but isn't necessary.
0
0
I do think it's unfair to spring surprise penalties on people too. So I also agree the beam of light should be a different color.
0
1
I suggest adding an /enchant # # server command, which would enchant whatever tool or armor you currently have selected in your hotbar. The first number would correspond to a specific enchantment and the second number would indicate the enchantment level. You'd be able to pick the exact enchantment and level you want, and also add enchantments to already enchanted items.
There could also be a /disenchant # # command to remove specific unwanted enchantments from your currently held item, while leaving it untouched otherwise.
1
It might cause momentary lag for a giant wheat farm with thousands and thousands of plants. But it's a one time brief moment of lag, not like a redstone lag machine that keeps operating. And that lag means that your giant wheat farm can actually function instead of do nothing.