mojira.dev
MC-77409

Inconsistent Time tag for FallingSand

Resolved
Duplicate
1

Relates to:

Is duplicated by/reason for:

I don't really understand how the whole FallingSand Time tag should work, but it is definitely pretty strange. First of all, it is a byte which decreases all possibilities in an extreme way. Maybe that should get fixed.

Special time tags:

  • 0 despawn just after it was spawned, but doesn't drop an item! and replaces block if it has the same block id

  • Any other number will also "replace" the block but leaves a ghost block (MC-72248 or MC-55106)

For whatever reason this happens:

  • -128 is some ticks later -124

  • -1 is some ticks later 3

  • 1 is some ticks later 5

  • 127 is some ticks later -125

I really have no clue to what it is counting down, but you can also not prevent this timer to count down...

Linked issues

duplicates 1

Comments 9

It's not counting down – it's counting up. It's the lifetime of the FallingSand entity. The notes on the wiki are quite informative.

But why does then "127 is some ticks later -125" this happen?

127 is the maximum for a Java Byte variable. Java stores negative numbers in two's complement, and it just wraps around like that when it overflows.

So the next value would be -124?

Right. If you think of two's complement for a single byte as a number line, it goes from 0 to 127, then from -128 to -1. The whole problem is it converting between an int and a byte: MC-35127.

Uh, the next value should be -128, not -124.

I think he meant the next value after -125, not the next value after 127.

Yes Torabi, that was what I meant

So is this report invalid?

Sort of. There is a legitimate issue here, but it's MC-35127.

marcono1234

(Unassigned)

Community Consensus

Minecraft 1.8.2-pre6

Retrieved