WStone
WStone
Create WStone
To create a WStone create a sign with [WStone] on the first line.
Transmitter
If you want it to be a transmitter write "T" or "Transmitter" on the second line.
Receiver
To create a receiver put "R" or "Receiver" on the second line.
Please note that the block behind the sign has to be free (air) and, if you're in survival, you have to have redstone dust in your inventory!
Repeater
A repeater has to have "RP" or "Repeater" on the second sign line.
For all types
Networks
The third line is for the network name. If you leave it empty "Main" will be used.
If you put "P" on the fourth line this will be a private network: Only you and people you like will be able to build WStones connected to it.
If you want to connect to a private network not owned by you write "P=<Owner>" on the fourth line, where <Owner> is the name of the player owning the network. Please note that you will get an error if you don't have the permissions from the owner to do so!
Commands
Network Permissions
If you own a private network and want to give somebody permissions simply send the command:
/WStone add <Network> <Player>
to remove a players permissions:
/WStone remove <Network> <Player>
Please note that the permissions system of the networks is a wrapper to permissionsBukkit. It seems that permisionsBukkit don't save that dynamic permissions, so after a server reload all network permissions will be lost!
List networks
You can use the commnand /WStone networks to list WStone networks.
In-game help
Use /WStone help to get help.
Videos
Features
- Send redstrone states wirelessly.
- Transmitting/Receiving exact current (0-16, not LOW or HIGH).
- Multiple networks.
- Multiple transmitters/receivers per network.
- Network states will get saved and reloaded by server stop/start.
- Small transmitters (1 block).
- Small receivers(2 blocks).
- Private networks.
- Repeaters.
- Stargate / Wormhole X-Treme support.
PermissionsBukkit
WStone.build:
description: Build / destroy WStones.
default: op
WStone.admin:
description: Toggle WStone options.
default: op
For Devs
There's a API called WStoneConnect. You get it with wstone.getAPI() (where wstone is the plugins instance). Have a look in the sources for more information (the API is in it's own class) but be aware that it's still in an early state and currently the API tends to break between WStone releases.
Please note that the classfile of the API is distributed under another license: LGPL. You can find more infos about that in the classfile.
Get Sources
The sources are included in the jar file.
@VasVadum I just realized that there's a mistake in the description: The permission nodes are WStone.build and WStone.admin, there's no node called WStone.perm. :(
It works, except for permissions still.
http://ft.trillian.im/vasvadum/676pzkw9K-2SmnH8w9bP.jpg
If it helps out any, you can join the server and see for yourself and I can show you all the info you might need, such as mods and configurations. I'd really like to get this working, 4 users are still waiting for it.
The error doesn't matter if permissions don't work. But I'll get a recording of the issue and show you. But text simple example of it breaking.
T = Transmitter
R = Reciever
P = Piston.
S = Switch
- = broken protected redstone
_ = redstone
S____T
R__-__P
R (powered) - (unpowered) P
Power can't get past the broken protected piece, because I moved the R back by 2 squares for whatever reason was necessary.
Blah, i'm really bad at explaining. And thus, the video.
Video: http://www.youtube.com/watch?v=l_IQngWh0wg
@VasVadum Could you explain "dead spots"? How do they occur? Why do they break WStone?
I also found that this plugin leaves many dead spots all over the server where blocks can't be removed by ANYONE even admins. which breaks wstone if you try to move the sign back a block or 2. Only way to fix is to type /reload.
I even tried WStone.*: true
nothing changed.
I configured it, I just noticed that the post here missed the : but in the config it's there.
Snapshot is better evidence. I don't know what's going on with the plugin and why it's not working for all users.
I use PermissionsBukkit by the way.
@VasVadum Please ask the author of your permissions plugin how to configure it. Maybe (this is just an idea and may be wrong) you miss a : between WStone.perm and true.
groups:
default:
permissions:
WStone.perm true
Users still can't use it. I don't know why, but it's been this way forever.
@Artaex
this plugin is very cool :P its already possible to do that but not by puting the sign on the lamp
put your sign 2 block away :)
i personaly have lots of complicated lamps lol
and a very complex network of wstone :P you wont have any problem doing simple stuff that you will probably do :P
@VasVadum Should work just fine with 1.2.5 and yea, the word "recommended" in "recommended build" has a reason... :)
1.2.5 ready? People are whining for an update to make the cats less annoying. The cats are annoying me to the point of banning cats! >.> They won't stop sitting on my chests. Hundreds of meowing all around.
I just recommend waiting for "recommended" updates from bukkit before you update, no need to update to the latest builds till they become recommended. That way you aren't stuck updating constantly. if people want you to update to a beta build and you don't feel like it then screw them :P That's why bukkit names some recommended to let modders know which ones are stable enough for support with most mods. Blah you probably do this anyway :P I'm just tired and stuff. xD
@Artaex You'e able to to that... Sign -> output power -> redstone lamp... ;)
You should add the ability to put a sign on a redstone lamp, and if you're sending power to the network, the redstone lamp will light up?
1.1 Work great :)
@V10lator
ok i have stop server delete sav file rebuild all sign
but only one problem i got the same bug again still mixed
so the sav file is not in cause with this bug
i have less sign i have not rebuild other station but first station dont work .... example when i put power on a transmiter tra_f3 it trigger the receiver tra_f3 and the receiver tra_fr
and i have nothing sending power to tra_fr
@VasVadum WStone should work just fine with 1.2, but please don't rage about the bukkit devs, they do amazing things... <.<
Anyway, hope your bug got fixed.
I wish these damn bukkit devs would hurry up and release a recomended 1.2 build so I can update my damn server. No one joins because I can't go above 1.1.....
I haven't had the server crash yet so I'll wait on updating the thing.
@jonathall I know this is hard for you, but could you stop the server, delete the save file an re-try it? Cause if the old bug got saved in the file the fix can't do anything... Sorry... :(