Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
component:geolyzer [2017/04/13 06:12]
sylphio
component:geolyzer [2019/08/20 05:28] (current)
payonel
Line 8: Line 8:
 - `scan(x:​number,​ z:number[, y:number, w:number, d:number, h:number][, ignoreReplaceable:​boolean|options:​table]):​table`  ​ - `scan(x:​number,​ z:number[, y:number, w:number, d:number, h:number][, ignoreReplaceable:​boolean|options:​table]):​table`  ​
   Analyzes the density of the column at the specified relative coordinates. This will return a list of hardness values for the blocks in the specified range. The coordinates are relative to the location of the geolyzer. Hardness values for blocks further away from the geolyzer are more noisy than those for blocks nearby.   Analyzes the density of the column at the specified relative coordinates. This will return a list of hardness values for the blocks in the specified range. The coordinates are relative to the location of the geolyzer. Hardness values for blocks further away from the geolyzer are more noisy than those for blocks nearby.
 +  ***Note** that the values returned is always 64 values, even if the scan volume is only part of that. If 10 blocks are scanned, the first 10 values in the result represent those blocks scanned. The remaining values in the result should be ignored.
 - `analyze(side:​number[,​ options:​table]):​table`  ​ - `analyze(side:​number[,​ options:​table]):​table`  ​
   Get some information on a directly adjacent block. By default the returned table returns the string ID of the block (e.g. `minecraft:​dirt`,​ metadata, hardness and some more information). Note that a single call to this consumes the same amount of energy a call to `scan` does!  ​   Get some information on a directly adjacent block. By default the returned table returns the string ID of the block (e.g. `minecraft:​dirt`,​ metadata, hardness and some more information). Note that a single call to this consumes the same amount of energy a call to `scan` does!  ​