If that actually works, THAT WOULD BE FREAKING AWESOME.
FINALLY! Someone who noticed me mentioning this idea!
Also interesting: Suppose I pasted a schematic file that included a simple redstone clock and a command block that was programmed to paste that same schematic. They would continue to multiply until they covered the map of their clocks lagged the server to death.
MUHAHAHAHA!!!
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
Hate to burst a couple of bubbles but it affects whoever activated the redstone with the variable @p.
So if I do, say, "/give @p boat", the person who pressed the button would get a boat?
If so, that would be amazing, because I want to be able to have an infinite boat giving machine at the spawn area in my server, since it's near the ocean.
the ability to swap the player's modes would be interesting indeed. Instead of those clumsy signs saying "you cannot break X in this area only" I sometimes see in normally rule free maps, just step on a pressure plate at the entrance and exit that locks you in adventure mode.
Hate to burst a couple of bubbles but it affects whoever activated the redstone with the variable @p.
Alright. So what happens when I hook it to a clock that is activated by a piston flipflop that is flipped by a pressure plate that is triggered by an arrow launched from a dispenser triggered by a tripwire tripped by a mob?
My point is that redstone works by cellular automata where each block responds to adjacent blocks' change of state. There is no way to know at the end of a redstone circuit who did whatever needed to be done to trigger the redstone pulse.
the ability to swap the player's modes would be interesting indeed. Instead of those clumsy signs saying "you cannot break X in this area only" I sometimes see in normally rule free maps, just step on a pressure plate at the entrance and exit that locks you in adventure mode.
I like that.
Because when most people see a sign like that they start breaking every X they see. :L
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
It would be useful to introduce a symbol like @all to run the specified commands for all players. So you can use it for an adventure map.
Example:
Command looks like:
/tp @all 0 60 0
Assuming that Brian and Luke are on the server the server executes this:
/tp Brian 0 60 0
/tp Luke 0 60 0
That makes very good sense, though perhaps it could be expanded a bit more?
@all
@nearest
@5 (where the 5 is an integer defining a radius in which to effect all players in that radius)
@random (where anyone could get nailed, for better or worse. MUHAHAHA!!)
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
Alright. So what happens when I hook it to a clock that is activated by a piston flipflop that is flipped by a pressure plate that is triggered by an arrow launched from a dispenser triggered by a tripwire tripped by a mob?
My point is that redstone works by cellular automata where each block responds to adjacent blocks' change of state. There is no way to know at the end of a redstone circuit who did whatever needed to be done to trigger the redstone pulse.
Well, obviously @p does not work for mobs, because they are not players. But aside from that, Jeb is aware of the issue of not knowing who activated what, but he's going to extend the command syntax of the game. Also, it should be noted he might already have solved our little issue: https://twitter.com/jeb_/status/228849882302132224
Anyways, suffice it to say, now that 1.3 has been done, and they've ironed out most bugs, we can expect a lot more content, command syntax included. By the time the block is released in a snapshot/update, there will be a way to target the player who activated the redstone current.
Well, obviously @p does not work for mobs, because they are not players. But aside from that, Jeb is aware of the issue of not knowing who activated what, but he's going to extend the command syntax of the game. Also, it should be noted he might already have solved our little issue: https://twitter.com/...849882302132224
Anyways, suffice it to say, now that 1.3 has been done, and they've ironed out most bugs, we can expect a lot more content, command syntax included. By the time the block is released in a snapshot/update, there will be a way to target the player who activated the redstone current.
Man do I need to check Twitter more. I'm too busy on these forums. :L
Wait. so the command block won't be in 1.3 at all? Bummer. :/
Do we have a confirmation on that?
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
Well, I can confirm absolutely that it won't be in 1.3, but I can't say for certain that it won't be in 1.3.1 or the like. Jeb and Dinnerbone have said that there will be no new features between 12w30e and 1.3, but neither of them have said anything about the following updates. (Because I would assume there will be 1.3.1 and possible 1.3.2 and so on, simply because it has been done consistently in the past.)
Well, I can confirm absolutely that it won't be in 1.3, but I can't say for certain that it won't be in 1.3.1 or the like. Jeb and Dinnerbone have said that there will be no new features between 12w30e and 1.3, but neither of them have said anything about the following updates. (Because I would assume there will be 1.3.1 and possible 1.3.2 and so on, simply because it has been done consistently in the past.)
I certainly hope not. I'm not fond of the mini-updates.
I rather the mini-updates be used only to patch serious bugs, preferably within a week of the primary release.
If they toss some mostly-finished content into an emergency bug patch, I'm okay with that.
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
Well, I think that a 1.3.1 will be necessary, since there are some large bugs in the current pre-release, such as issues with going to and from the dimensions, as well as some other much more minor issues.
FINALLY! Someone who noticed me mentioning this idea!
Also interesting: Suppose I pasted a schematic file that included a simple redstone clock and a command block that was programmed to paste that same schematic. They would continue to multiply until they covered the map of their clocks lagged the server to death.
MUHAHAHAHA!!!
...but that's just like, my opinion, man.
So if I do, say, "/give @p boat", the person who pressed the button would get a boat?
If so, that would be amazing, because I want to be able to have an infinite boat giving machine at the spawn area in my server, since it's near the ocean.
...but that's just like, my opinion, man.
Alright. So what happens when I hook it to a clock that is activated by a piston flipflop that is flipped by a pressure plate that is triggered by an arrow launched from a dispenser triggered by a tripwire tripped by a mob?
My point is that redstone works by cellular automata where each block responds to adjacent blocks' change of state. There is no way to know at the end of a redstone circuit who did whatever needed to be done to trigger the redstone pulse.
I like that.
Because when most people see a sign like that they start breaking every X they see. :L
That makes very good sense, though perhaps it could be expanded a bit more?
@all
@nearest
@5 (where the 5 is an integer defining a radius in which to effect all players in that radius)
@random (where anyone could get nailed, for better or worse. MUHAHAHA!!)
Well, obviously @p does not work for mobs, because they are not players. But aside from that, Jeb is aware of the issue of not knowing who activated what, but he's going to extend the command syntax of the game. Also, it should be noted he might already have solved our little issue: https://twitter.com/jeb_/status/228849882302132224
Anyways, suffice it to say, now that 1.3 has been done, and they've ironed out most bugs, we can expect a lot more content, command syntax included. By the time the block is released in a snapshot/update, there will be a way to target the player who activated the redstone current.
...but that's just like, my opinion, man.
Man do I need to check Twitter more. I'm too busy on these forums. :L
Wait. so the command block won't be in 1.3 at all? Bummer. :/
Do we have a confirmation on that?
...but that's just like, my opinion, man.
I certainly hope not. I'm not fond of the mini-updates.
I rather the mini-updates be used only to patch serious bugs, preferably within a week of the primary release.
If they toss some mostly-finished content into an emergency bug patch, I'm okay with that.
...but that's just like, my opinion, man.
@r for Random player,
@a for EVERY PLAYER!
Why not do that now with a regular command?
So I can have a house there, and teleport with just a press of a button. (And the button-presser doesn't have to be an op).
Ah. Makes sense, I suppose.
Should I mention now that the Farlands don't exist anymore?
They still exist, its just us mortals can't feel it's knowledge.