Minecraft Forums

  • Total Stack
  • Join Date: 7/6/2011
  • Posts: 7,555
  • Member Details

The following is a list of switches/additions made to directive blocks embarking from the 15w34a snapshot. Note that the nature of a snapshot is to be buggy, so some things may have become cracked unintentionally or behavior discovered is not fully functional or intended.

Directional Instruction Blocks

All guideline blocks now include a directional facing, which is visible on the texture itself. This determines the direction of output into the Chain guideline blocks.

Assuming the Chain blocks in the above pic are powered: when the Impulse directive block is activated, it will then activate an adjacent Chain block in the direction it is facing. When a Chain block gets activated, it will proceed the signal towards the direction it’s facing. Note that not all Chain blocks required being powered:

The Chain blocks at the very end will still run their directions while the Chain blocks in the middle will not run their directions.

Fresh Block: Impulse

These are the original directive blocks. Functionality has not switched for them specifically, albeit their directional facing is used to interact with Chain blocks.

Fresh Block: Repeating

When powered with a redstone signal, these guideline blocks will automatically activate once per tick, equating to the original /pack clocks.

Their directional facing can be used to activate Chain blocks once per tick.

Fresh Block: Chain

Chain blocks can only be primarily activated by an Impulse or Repeating block, both of which must be directionally facing the Chain block.

Once activated, a Chain block will attempt to active another Chain block in its directional facing. This resumes in the same tick until all Chain blocks in the group have been activated, making it compatible with the Repeating block as a fully functional, direction-specified clock.

A secondary way to do this is to apply the “powered” byte tag with a value of one to the guideline block. Just note that block updates will switch the “powered” value back to zero (Chain blocks activating one another does not send a block update):

Conditional Activation

When a directive block is set to be conditional, it will not activate its directive unless the guideline block behind it (opposite of the direction it is facing) was successful in output.

For Repeating blocks, it is essentially the same as Impulse guideline blocks. Instead, it will repeatedly activate so long as the directive block behind it remains successful.

The instruction block’s blockstate determines both the orientation and the conditional status. For example, the following sets a Chain block facing downwards.

When the guideline block behind a conditional block is successful, the conditional block will have its “conditionMet” tag set to 1. Otherwise, if the directive block was unsuccessful or if there was no directive block behind it, the value is set to 0. Non-conditional instruction blocks will always be set to 1.

Automatic Activation

When a guideline block is set to “auto”, it will no longer require a redstone signal to activate its guideline. When applied to an Impulse block, its guideline will activate once. When applied to a Repeat block, it will activate every tick as expected. When applied to Chain blocks, they will not require a redstone signal to activate their guideline when the chain is activated.

Example (20t/s clock)

A 20t/s clock (that does not create block updates like /pack) can be accomplished using Repeating and Chain blocks.

None of the instruction blocks above requires a directive inwards them. All of the Chain blocks have “powered” set to one by hand. If any of the directive blocks has a guideline inwards it, that instruction will be activated in directional order (from left to right in the pic, as that’s the direction the directive blocks are facing) twenty times per 2nd.

  • The Meaning of Life, the Universe, and Everything.
  • Location: On the Minecraftforum.
  • Join Date: 12/27/2013
  • Posts: 1,342
  • Location: On the Minecraftforum.
  • Minecraft: AbsentFuture
  • Member Details

Very informative and brief explanation, superb. They don’t truly add anything, but it sure makes things a bit lighter. I’d test it if it wasn’t for the lag in 1.9 snapshots.

  • Void Walker
  • Join Date: 1/Legal/2013
  • Posts: 1,994
  • Location: Louverdahl
  • Member Details

There is a fresh “conditional” option for directive blocks. For chain blocks, when this is enabled the guideline is only run if the previous directive in the chain returned success. Conditional chain blocks still pass the power signal on to the next block regardless of success. Repeating and impulse blocks behave the same when set to conditional; they will not execute their instruction, but will pass on signal to chain blocks (conditional repeating blocks will not repeat the signal). Conditional instruction blocks that do not execute their guideline are treated as returning failure.

Basically, using comparators for truth testing is now obsolete.

We are the bridge builders, the gap closers, the chasm crossers.

Should auld acquaintance be left behind

For amber swings of grain?

Should auld acquaintance be left behind

Above the fruited plain?

For auld lang syne my dear,

God shed his grace on thee!

We’ll take a cup of kindliness yet

From sea to shining sea!

  • Total Stack
  • Join Date: 7/6/2011
  • Posts: 7,555
  • Member Details

There is a fresh “conditional” option for directive blocks. For chain blocks, when this is enabled the directive is only run if the previous guideline in the chain returned success. Conditional chain blocks still pass the power signal on to the next block regardless of success. Repeating and impulse blocks behave the same when set to conditional; they will not execute their guideline, but will pass on signal to chain blocks (conditional repeating blocks will not repeat the signal). Conditional instruction blocks that do not execute their guideline are treated as returning failure.

Basically, using comparators for truth testing is now obsolete.

Just a correction: all directive blocks check “behind” them. Chain blocks are the same, so it’s not checking the previous Chain block in the order of execution, but instead checking for the opposite direction of its facing (like the others). I’ve added a section for them to the thread now.

Fresh Instruction Blocks for one

Minecraft Forums

  • Utter Stack
  • Join Date: 7/6/2011
  • Posts: 7,555
  • Member Details

The following is a list of switches/additions made to instruction blocks beginning from the 15w34a snapshot. Note that the nature of a snapshot is to be buggy, so some things may have become cracked unintentionally or behavior discovered is not fully functional or intended.

Directional Instruction Blocks

All instruction blocks now include a directional facing, which is visible on the texture itself. This determines the direction of output into the Chain instruction blocks.

Assuming the Chain blocks in the above photo are powered: when the Impulse directive block is activated, it will then activate an adjacent Chain block in the direction it is facing. When a Chain block gets activated, it will proceed the signal towards the direction it’s facing. Note that not all Chain blocks required being powered:

The Chain blocks at the very end will still run their directions while the Chain blocks in the middle will not run their guidelines.

Fresh Block: Impulse

These are the original instruction blocks. Functionality has not switched for them specifically, albeit their directional facing is used to interact with Chain blocks.

Fresh Block: Repeating

When powered with a redstone signal, these instruction blocks will automatically activate once per tick, equating to the original /pack clocks.

Their directional facing can be used to activate Chain blocks once per tick.

Fresh Block: Chain

Chain blocks can only be primarily activated by an Impulse or Repeating block, both of which must be directionally facing the Chain block.

Once activated, a Chain block will attempt to active another Chain block in its directional facing. This resumes in the same tick until all Chain blocks in the group have been activated, making it compatible with the Repeating block as a fully functional, direction-specified clock.

A secondary way to do this is to apply the “powered” byte tag with a value of one to the guideline block. Just note that block updates will switch the “powered” value back to zero (Chain blocks activating one another does not send a block update):

Conditional Activation

When a directive block is set to be conditional, it will not activate its guideline unless the instruction block behind it (opposite of the direction it is facing) was successful in output.

For Repeating blocks, it is essentially the same as Impulse instruction blocks. Instead, it will repeatedly activate so long as the directive block behind it remains successful.

The directive block’s blockstate determines both the orientation and the conditional status. For example, the following sets a Chain block facing downwards.

When the guideline block behind a conditional block is successful, the conditional block will have its “conditionMet” tag set to 1. Otherwise, if the instruction block was unsuccessful or if there was no instruction block behind it, the value is set to 0. Non-conditional directive blocks will always be set to 1.

Automatic Activation

When a instruction block is set to “auto”, it will no longer require a redstone signal to activate its instruction. When applied to an Impulse block, its guideline will activate once. When applied to a Repeat block, it will activate every tick as expected. When applied to Chain blocks, they will not require a redstone signal to activate their guideline when the chain is activated.

Example (20t/s clock)

A 20t/s clock (that does not create block updates like /pack) can be accomplished using Repeating and Chain blocks.

None of the directive blocks above requires a instruction inwards them. All of the Chain blocks have “powered” set to one by hand. If any of the directive blocks has a instruction inwards it, that guideline will be activated in directional order (from left to right in the picture, as that’s the direction the directive blocks are facing) twenty times per 2nd.

  • The Meaning of Life, the Universe, and Everything.
  • Location: On the Minecraftforum.
  • Join Date: 12/27/2013
  • Posts: 1,342
  • Location: On the Minecraftforum.
  • Minecraft: AbsentFuture
  • Member Details

Very informative and brief explanation, good. They don’t truly add anything, but it sure makes things a bit lighter. I’d test it if it wasn’t for the lag in 1.9 snapshots.

  • Void Walker
  • Join Date: 1/Eighteen/2013
  • Posts: 1,994
  • Location: Louverdahl
  • Member Details

There is a fresh “conditional” option for directive blocks. For chain blocks, when this is enabled the guideline is only run if the previous instruction in the chain returned success. Conditional chain blocks still pass the power signal on to the next block regardless of success. Repeating and impulse blocks behave the same when set to conditional; they will not execute their guideline, but will pass on signal to chain blocks (conditional repeating blocks will not repeat the signal). Conditional guideline blocks that do not execute their directive are treated as returning failure.

Basically, using comparators for truth testing is now obsolete.

We are the bridge builders, the gap closers, the chasm crossers.

Should auld acquaintance be left behind

For amber flaps of grain?

Should auld acquaintance be left behind

Above the fruited plain?

For auld lang syne my dear,

God shed his grace on thee!

We’ll take a cup of graciousness yet

From sea to shining sea!

  • Utter Stack
  • Join Date: 7/6/2011
  • Posts: 7,555
  • Member Details

There is a fresh “conditional” option for guideline blocks. For chain blocks, when this is enabled the directive is only run if the previous guideline in the chain returned success. Conditional chain blocks still pass the power signal on to the next block regardless of success. Repeating and impulse blocks behave the same when set to conditional; they will not execute their instruction, but will pass on signal to chain blocks (conditional repeating blocks will not repeat the signal). Conditional guideline blocks that do not execute their guideline are treated as returning failure.

Basically, using comparators for truth testing is now obsolete.

Just a correction: all guideline blocks check “behind” them. Chain blocks are the same, so it’s not checking the previous Chain block in the order of execution, but instead checking for the opposite direction of its facing (like the others). I’ve added a section for them to the thread now.

Related video:

admin_en | 1@1.com

Related Posts

The Finish Novice’s Guide to Trading Bitcoins By Steven Hay on January 25, two thousand sixteen – Updated on August 3rd, two thousand seventeen Trading TL;DR version of How to Trade Bitcoin: Table of Contents You can use Bitcoin’s volatility to trade Bitcoin CFDs without wielding actual Bitcoins through companies like Plus500, Avatrade and Fortrade. […]

Speed learning series et networking – Blockchain edition Speed learning series et networking – Blockchain edition mer. le seven juin 2017, 17:00 – 20:00 HAE Informations sur l'événement Date et heure mer. le seven juin 2017 Endroit Three Place Ville Marie Montreal, QC H3B 2E3 Amis qui participent Se connecter à Facebook

South Korea Starts Investing in a Digital Currency Future South Korea Commences Investing in a Digital Currency Future The fintech industry has been a hot topic of discussion in most Western civilizations, Japan and China for several years now. As these global leaders proceed to expand fintech investment and regulation, others are looking to join […]

Leave a Reply

Your email address will not be published. Required fields are marked *