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 Both sides next revision
component:geolyzer [2017/04/12 07:15]
sylphio Quick update update geolyzer
component:geolyzer [2017/04/13 08:12]
sylphio
Line 7: Line 7:
  
 - `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. +  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.
-- `scan(x:​number,​ z:number[, ignoreReplaceable:​boolean]):​table` ​  +
-  ​Analyzes the density of the column at the specified relative coordinates. This will return a list of hardness values for the blocks in a vertical [-32, 32) range, relative to the height the geolyzer is located. 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.+
 - `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!  ​