[MC-1775] Hash size breaks redstone

Hash size differs over the world and once a limit is reached of redstone activated at same time redstone breaks by either adding or subtracting a tick to a devise and there is no way to predict any of this it is just completely random to a user in the world.

Related issues

relates to

MC-8328 Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update 'algorithm')

Attachments

Comments

migrated 2012-11-01T22:59:34Z

[media][media]

Treydun 2012-11-18T21:08:55Z

Do you have an example I can use to test this. I have never built a device that complex.

aaron ueckermann 2012-11-18T23:25:11Z

Try a giant piston extender and move it round in your world until you find
a hash size problem shouldn`t take long.

On Sun, Nov 18, 2012 at 9:10 PM, Treydun (JIRA)

lmlb_lmlb 2012-11-24T18:58:40Z

Sethbling has made a video about it: http://www.youtube.com/watch?v=Zt7YEYdx6RE

Tails 2013-01-28T17:03:40Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

kbk 2013-01-30T14:49:32Z

Ok, I just tried to recreate Sethbling's setup from a video. Here are the results of the test I've conducted :

1.4.6

Redstone grid is off - two leftmost switches make the door shut when turned on
Grid is on and not reconnected - same behaviour
Grid is on and reconnected - same behaviour

13w04a

Grid is off - all four switches make the door shut when turned off
Grid is on and not reconnected - same behaviour
Grid is on and reconnected - same behaviour

Either this report is not a concern in the current snapshot or I've just done something wrong (e.g. my build differs slightly from Sethbling's or needs some huge redstone updates from other loaded contraptions) and my test fails. Anyways I think this report could be resolved at least for now.

Tails 2013-01-30T15:58:09Z

I had the same results, so maybe this ticket can be marked as duplicate of MC-8328?

kbk 2013-01-30T16:39:06Z

As for me, in this report we are using the MC-8328 bug as a method to test something bigger that could (at least in previous releases) manifest itself in a number of different ways (eg giant extender). Moreover MC-8328 is still reproducible but this bug seems kinda fixed. So I'd rather keep the relations and mark this report as "could not reproduce" or "fixed".

Tails 2013-01-30T16:40:51Z

Ok, resolving as fixed for now.