Tons of sign copy

[mantricore]

When I place 3 reciever to activate pistons, each time I activate the lever on the transciever, it make copies of the reviever as a sign ( item ) and drop it evrywhere. The reciever are not destroyed after this operation.

Both three reciever have the same channel.

P= pistons
B=brick
R=Reviever

B B B
P P P
R R R

T= transciever
L=Lever
R=redstone

T R L

[axelpey]

I see, I will try it on my test server...

[axelpey]

Tested and... I don't see anything it works perfectly...

Do you have a screenshot?

[mantricore]

http://i47.servimg.com/u/f47/16/47/15/39/test1-10.jpg

I am on creative, SMP, bukkit client.

[axelpey]

That's what I tested...
Okay, what plugins do you use?
What's your version of bukkit?
Do you have an error log?

[mantricore]

I use world edit and wireless redstone.

Bukkit version 1.2.3

I do not have any error log.
This error didin't gave me any error in the bukkit pannel.

This may be an isolated case relative to the position in the world, because I did another test ( the same ) in another place and everything worked fine.

And I don't know if this could help but , the writing on the sign were the oposite of the pistons in the first test and in the second , it was faced to the pistons.
I tried to change the position of the first test but it was impossible.

[axelpey]

maybe the direction is the cause, will see this tomorrow.
Thanks

[5John5]

I have this Issue too. Did an Redstone circle with more then 3 receivers. I wanted to destroy one cause it was set up wrong by mistake. Bu i couldnt destroy it, everytime i activated the channel wit an transmiite it appears new and created 4 signs in the near everyrime i activated it^^ At least ia had full inventory with signs but no working circle xD

[axelpey]

Hum... Yeah I know, I didn't close this issue, i will fix it, i promised ^^

[wolfiepawz]

I have the same issue....

Please fix.

[axelpey]

Just made a test... and it works...

I think it's a problem with some plugin... what plugins do you use?

[Bart-0110]

Should be fixed now, otherwise create a new issue