CRAFTBOOK-2513 - Reported by pmpmpm

Hello,

After having, err, well, TORTURED the MC3030 by putting two signs on only one block (one on the front and one on the right), and after having "tested" it a bit (it doesn't work very well), I decided to break one of the two signs and keep only the one that I need.

The problem is that, even after having destroyed the sign, replaced it with a MC1000 Repeater (which works well), broken the block, replaced the MC3030, tried to reset it, restarted the server, the output just won't go high. It's obvious that it's because I tortured it (I suppose it's a fair revenge), I just wanted to report it. It's kinda annoying.

Thanks for reading.

Edit: Okay, so it's not because of the torture that the IC is acting strangely. On another circuit (without torture), another MC3030 just doesn't Set itself. You can see it on the screenshot 1.
Edit 2: Okaaaay, now that's really weird. By moving the IC just 2 blocks back (Screenshot 2), it works perfectly.

Any explanation on that? I'm lost.

Comment by me4502

Ok

Comment by pmpmpm

RHAAAAAAAA IT DID IT AGAIN ><

I think it may have something to do with the proximity of a MC1018 and a MC1271... BUT WHY ><
And it's the third time it does it!

Comment by me4502

Hmm? That is incredibly weird.

Comment by pmpmpm

In fact, there was 3 circuits. There are perfectly the same, except that they don't have the same orientation.

On one circuit, I messed with the MC3030, so I thought it was because of that torture. But it did it on the 3 circuits!

Comment by me4502

Err.. So there is nothing similar?

Comment by pmpmpm

The 3 circuits are perfectly the same, oriented differently, if that's what you're asking?

Comment by me4502

I was asking if there was anything similar in the broken ones, that was different to working ones.

Comment by pmpmpm

Nop, strictly nothing but their place relatively to the circuit.

Comment by me4502

Hmm, without further information I can't reall solve this. As nothing is persistent between working and not working.

Comment by me4502

Um.. Did you previously have another IC at this location? There could be a caching bug?

Comment by pmpmpm

Nop, that's what I thought first, but there wasn't anything before.

Comment by me4502

Hmm. Is it on a chunk boundary?

Comment by pmpmpm

Err... Maybe. Actually, the IC bugged on two different blocks, that's why I had to put it back TWO blocks rather than one. So it may be that.

Comment by me4502

Chunk boundaries shouldn't effect redstone. Are you able to find any solid way of reproducing this issue?

Comment by pmpmpm

I'll try.

Comment by pmpmpm

Well, can't reproduce it anywhere else... Seems like we have some haunted area! I adapted the circuit. I'll stay on the look for this kind of bug.