Redstone Output Port - Revision history

Montoyo: /* How to use */

2018-02-14T14:49:12Z

‎How to use

2018-02-14T14:48:21Z

‎How to use

2018-02-14T14:47:07Z

‎Queries

2018-02-13T21:39:33Z

2018-02-13T16:28:44Z

‎Queries

2018-02-13T16:28:32Z

‎JavaScript

2018-02-13T16:26:57Z

‎Limits

2018-02-13T16:26:40Z

‎How to use

2018-02-13T16:25:44Z

‎Limits

2018-02-13T16:25:27Z

‎Limitations

@@ Line 11: / Line 11: @@
 Like any other upgrades, install it by right-clicking on a screen with the upgrade in your main hand. You will need the "Link & upgrade" permission to do that.
-Please note that the emitting status of each blocks is conserved even when the screen is destroyed. You can know if a screen block is in the emitting state by using the <code>IsEmitting</code> and <code>GetEmissionArray</code> queries. You can also reset the emission state of the whole screen by using <code>ClearRedstone</code>. The emitting status is then displayed when hovering the block on the right side.
+Please note that the emitting status of each blocks is conserved even when the screen is destroyed. You can know if a screen block is in the emitting state by using the <code>IsEmitting</code> and <code>GetEmissionArray</code> queries. You can also reset the emission state of the whole screen by using <code>ClearRedstone</code>. The F3 key may also be used to get this information for debugging purposes. The emitting status is then displayed when hovering the block on the right side.
 ===Limits===

@@ Line 11: / Line 11: @@
 Like any other upgrades, install it by right-clicking on a screen with the upgrade in your main hand. You will need the "Link & upgrade" permission to do that.
-Please note that the emitting status of each blocks is conserved even when the screen is destroyed. Thus, a good programmer should use the <code>ClearRedstone</code> query when the page loads to make sure that all blocks are in the passive state. You can know if a screen block is in the emitting state by using the Minecraft F3 key. The emitting status is then displayed when hovering the block on the right side.
+Please note that the emitting status of each blocks is conserved even when the screen is destroyed. You can know if a screen block is in the emitting state by using the <code>IsEmitting</code> and <code>GetEmissionArray</code> queries. You can also reset the emission state of the whole screen by using <code>ClearRedstone</code>. The emitting status is then displayed when hovering the block on the right side.
 ===Limits===

@@ Line 39: / Line 39: @@
 |-
 |SetRedstoneAt||int, int, int||<code>{"status":string}</code>||Enable/disable the emitting state for the block at x, y depending on the value of the 3rd parameter (1 or 0). Rotation is not handled
 |}
 The status returned by each queries is either "ok" or "notOwner".

← Older revision		Revision as of 21:39, 13 February 2018
Line 1:		Line 1:
	The Redstone Output Port is an [[Screen#Upgrade\|upgrade]] which allows web pages to change the redstone state of blocks around the screen.		The Redstone Output Port is an [[Screen#Upgrade\|upgrade]] which allows web pages to change the redstone state of blocks around the screen.
		+
		+	{{#widget:AdSense}}

	==Recipe==		==Recipe==

@@ Line 36: / Line 36: @@
 |ClearRedstone||None||<code>{"status":string}</code>||Sets all blocks in the passive state
 |-
-|SetRedstoneAt||int, int, int||<code>{"status":string}</code>||Enable/disable the emitting state for the block at x, y depending on the value of the 3rd parameter (1 or 0). Rotation is not handled</code>
+|SetRedstoneAt||int, int, int||<code>{"status":string}</code>||Enable/disable the emitting state for the block at x, y depending on the value of the 3rd parameter (1 or 0). Rotation is not handled
 |}
 The status returned by each queries is either "ok" or "notOwner".

@@ Line 18: / Line 18: @@
 * For each non-owner players, the query does nothing
 * For the owner, on the other hand, the query is forwarded to the server
-* The server receives the query from the owner (and only him), and enable or disables the redstone emitting status for the specified block
+* The server receives the query from the owner (and only him), and enables or disables the redstone emitting status for the specified block
 However, if the owner is disconnected or if the owner is too far away, this will of course not work. The <code>IsOwner</code> query can be used to know if the web page is running on the owner's web browser.

@@ Line 12: / Line 12: @@
 ===Limits===
-Every player has its own instance of the web browser, as described [[Screen#Multiplayer synchronization|here]]. When any redstone-output-related query is executed, each client (player) receives it, but <strong>only the screen owner will forward the query to the server.</strong> Thus, using redstone output queries on non-owner web browsers is useless. This shouldn't be a problem in the following scenario:
+Every player has its own instance of web browser, as described [[Screen#Multiplayer synchronization|here]]. When any redstone-output-related query is executed, each client (player) receives it, but <strong>only the screen owner will forward the query to the server.</strong> Thus, using redstone output queries on non-owner web browsers is useless. This shouldn't be a problem in the following scenario:
 * You have a web page that runs a redstone output query when a button is clicked
 * A player clicks on the button