Sensors, Why not? These sensors will be great for traps, parkour, and much much (...) more! These Sensors can sense anything from up to 10 blocks straight forward! They sense only entities (Not Paintings or Item Frames)! They can be place on ceilings, walls, floors! They can create a redstone signal through the blocks they are on, activating Pistons, Doors, and much much (Not again ...) more!
For traps affecting a player, use the /testfor command with command blocks.
If a command block is powered (usually it's set to a redstone clock, but it has to be powered in order to check for the players) and has it's command set to something like this:
/testfor @p
It will output a signal when it detects the nearest player reletive to the command block itself. You can center the search radius like so:
/testfor @p[x=0,y=0,z=0]
And the search radius will start from 0,0,0.
/testfor @p[x=0,y=0,z=0,r=1]
Will test only for players within a one block range of 0,0,0.
And so on and so forth with as many variable as you want; score, deaths, health, gamemode, and teams to name a few.
For traps affecting a player, use the /testfor command with command blocks.
If a command block is powered (usually it's set to a redstone clock, but it has to be powered in order to check for the players) and has it's command set to something like this:
/testfor @p
It will output a signal when it detects the nearest player reletive to the command block itself. You can center the search radius like so:
/testfor @p[x=0,y=0,z=0]
And the search radius will start from 0,0,0.
/testfor @p[x=0,y=0,z=0,r=1]
Will test only for players within a one block range of 0,0,0.
And so on and so forth with as many variable as you want; score, deaths, health, gamemode, and teams to name a few.
If you want your suggestion to be taken seriously, you can't just say "I don't care" to a valid counter-argument. Your idea already exists in the form of tripwires, pressure plates, and command blocks.
If you want your suggestion to be taken seriously, you can't just say "I don't care" to a valid counter-argument. Your idea already exists in the form of tripwires, pressure plates, and command blocks.
Support?
Every brony wants to be a pony!.
That is true! 1.5 out in few days part
Every brony wants to be a pony!.
If a command block is powered (usually it's set to a redstone clock, but it has to be powered in order to check for the players) and has it's command set to something like this:
It will output a signal when it detects the nearest player reletive to the command block itself. You can center the search radius like so:
And the search radius will start from 0,0,0.
Will test only for players within a one block range of 0,0,0.
And so on and so forth with as many variable as you want; score, deaths, health, gamemode, and teams to name a few.
For entities, see here. This is what I support.
Anything survival-built can use tripwires and pressure plates.
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
I Don't care
Every brony wants to be a pony!.
If you want your suggestion to be taken seriously, you can't just say "I don't care" to a valid counter-argument. Your idea already exists in the form of tripwires, pressure plates, and command blocks.
True, very true!
Every brony wants to be a pony!.
circuits already:
System is spelt wrong! Just to let anyone know!
Every brony wants to be a pony!.
Ohmygod...damn...you're such a badass...
Let me just warn you...trolls are not very accepted here.
Cheers.