mirror of
https://github.com/MightyPirates/OpenComputers.git
synced 2025-09-16 18:55:03 -04:00
corrected comment on screen power use in config
This commit is contained in:
parent
88475bd4ca
commit
d395db6d7c
@ -407,14 +407,18 @@ opencomputers {
|
||||
# you can't fake sleep by calling `os.sleep(0)`.
|
||||
sleepFactor: 0.1
|
||||
|
||||
# The amount of energy a screen consumes per displayed character per
|
||||
# tick. If a screen cannot consume the defined amount of energy it
|
||||
# will stop rendering the text that should be displayed on it. It will
|
||||
# *not* forget that text, however, so when enough power is available
|
||||
# again it will restore the previously displayed text (with any
|
||||
# changes possibly made in the meantime). Note that for multi-block
|
||||
# screens *each* screen that is part of it will consume this amount of
|
||||
# energy per tick.
|
||||
# The amount of energy a screen consumes per tick. For each lit pixel
|
||||
# (each character that is not blank) this cost increases linearly:
|
||||
# for basic screens, if all pixels are lit the cost per tick will be
|
||||
# twice as high as this value. Higher tier screens can become even
|
||||
# more expensive to run, due to their higher resolution. If a screen
|
||||
# cannot consume the defined amount of energy it will stop rendering
|
||||
# the text that should be displayed on it. It will *not* forget that
|
||||
# text, however, so when enough power is available again it will
|
||||
# restore the previously displayed text (with any changes possibly
|
||||
# made in the meantime). Note that for multi-block screens *each*
|
||||
# screen that is part of it will consume this amount of energy per
|
||||
# tick.
|
||||
screen: 0.1
|
||||
|
||||
# Energy it takes read one kilobyte from a file system. Note that non
|
||||
@ -468,14 +472,14 @@ opencomputers {
|
||||
# consumed. Zero means exhaustion does not require energy, one is a
|
||||
# one to one conversion. For example, breaking a block generates 0.025
|
||||
# exhaustion, attacking an entity generates 0.3 exhaustion.
|
||||
robotExhaustion: 10
|
||||
robotExhaustion: 10.0
|
||||
|
||||
# The amount of energy it costs to send a signal with strength one,
|
||||
# which means the signal reaches one block. This is scaled up
|
||||
# linearly, so for example to send a signal 400 blocks a signal
|
||||
# strength of 400 is required, costing a total of 400 *
|
||||
# `wirelessCostPerRange`. In other words, the higher this value, the
|
||||
# higher the cost of wireless messages.
|
||||
# The amount of energy it costs to send a wireless message with signal
|
||||
# strength one, which means the signal reaches one block. This is
|
||||
# scaled up linearly, so for example to send a signal 400 blocks a
|
||||
# signal strength of 400 is required, costing a total of
|
||||
# 400 * `wirelessCostPerRange`. In other words, the higher this value,
|
||||
# the higher the cost of wireless messages.
|
||||
# See also: `maxWirelessRange`.
|
||||
wirelessStrength: 0.05
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user