Define groups of light types with a line of text to indicate the group \ name followed by one or more name definitions. End a group with a \ -blank line. All text is case-insensitive. Lines that start with a "-" are \ -considered comments and are ignored. The group name becomes an entry on \ -the token's popup menu under the Light Sources element, and \ -individual light source definitions become sub-entries. Group names are \ -displayed in sorted order, and the sub-entries are alphabetically sorted \ -as well.
\ -Range of personal light. The token will have a light source that only they can see, centered on them, with a radius of this value. You can define multiple personal lights per sight type.
\ -Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.
\ -Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.
\ -Ex: r60#bb0000+120
Group name\ -
\ -----------
\ -name: type shape OPTIONS scale range#rrggbb+x
Define groups of light types with a line of text to indicate the group \ -name followed by one or more name definitions. End a group with a \ blank line. All text is case-insensitive. Lines starting with a "-" are \ considered comments and are ignored. The group name becomes an entry on \ the token's popup menu under the Light Sources element, and \ @@ -902,7 +875,7 @@ their sub-entries are alphabetically sorted.
\An optional shape for the light emanation. Can be circle (default), \ - square, cone, beam, or grid†.
\ + square, cone, beam, or grid†.\Additional fields exist for beams and cones; both have an offset=y field,\ cones also have arc=y and beams have a width=y field.
\Shapes apply from the point they are included in the definition until the end of the \ @@ -910,13 +883,15 @@ their sub-entries are alphabetically sorted.
\ can be created under a single name and turned on or off as a unit.\†For systems like Pathfinder if you want to see exactly which grid cells are\ affected by a Light/Aura.
A distance measured in map units (defined when the map is created). Units are \ - measured from the centerpoint of the grid cell, hence the extra 2 ½ feet \ - added in the below example to make neat squares.
\ -Can have an optional #rrggbb hex color component appended to it as per \ - typical CSS rules.
\ -Can have an optional +x lumens value, with x equaling an integer \ +
A distance in map units as measured from the centerpoint of the grid cell.
\ +Can have additional definitions;\ +
A +x lumens value, with x equaling an integer \ (-x can instead be used to provide a negative lumens value). If not \ provided, the value will default to 100. If set to a negative number, the \ light will instead act as darkness and subtract it's area from the FoW. \ @@ -927,8 +902,9 @@ their sub-entries are alphabetically sorted.
\*Note: Personal Lights defined in Sight have a default lumens \ value of 100. So a typical sight defined for Darkvision will see through \ any lights with a lumens value of -1 through -99. To overcome Darkvision, use \ - lumens values <= -100.
Example:
\\ diff --git a/src/main/resources/net/rptools/maptool/language/i18n_en_au.properties b/src/main/resources/net/rptools/maptool/language/i18n_en_au.properties index 65c5a70006..93a78441a2 100644 --- a/src/main/resources/net/rptools/maptool/language/i18n_en_au.properties +++ b/src/main/resources/net/rptools/maptool/language/i18n_en_au.properties @@ -849,13 +849,13 @@ CampaignPropertiesDialog.label.sight = \
Range of personal light. The token will have a light source centreed on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.
\ -Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.
\ +Range of personal light. The token will have a light source centered on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.
\ +Can have an optional #rrggbb hex colour component appended to it as per typical CSS rules.
\Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.
\Ex: r60#bb0000+120
Define groups of light types with a line of text to indicate the group \ name followed by one or more name definitions. End a group with a \ -blank line. All text is case-insensitive. Lines that start with a "-" are \ -considered comments and are ignored. The group name becomes an entry on \ -the token's popup menu under the Light Sources element, and \ -individual light source definitions become sub-entries. Group names are \ -displayed in sorted order, and the sub-entries are alphabetically sorted \ -as well.
\ -Range of personal light. The token will have a light source that only they can see, centreed on them, with a radius of this value. You can define multiple personal lights per sight type.
\ -Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.
\ -Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.
\ -Ex: r60#bb0000+120
Group name\ -
\ -----------
\ -name: type shape OPTIONS scale range#rrggbb+x
Define groups of light types with a line of text to indicate the group \ -name followed by one or more name definitions. End a group with a \ blank line. All text is case-insensitive. Lines starting with a "-" are \ considered comments and are ignored. The group name becomes an entry on \ the token's popup menu under the Light Sources element, and \ @@ -904,7 +877,7 @@ their sub-entries are alphabetically sorted.
\An optional shape for the light emanation. Can be circle (default), \ - square, cone, beam, or grid†.
\ + square, cone, beam, or grid†.\Additional fields exist for beams and cones; both have an offset=y field,\ cones also have arc=y and beams have a width=y field.
\Shapes apply from the point they are included in the definition until the end of the \ @@ -912,13 +885,15 @@ their sub-entries are alphabetically sorted.
\ can be created under a single name and turned on or off as a unit.\†For systems like Pathfinder if you want to see exactly which grid cells are\ affected by a Light/Aura.
A distance measured in map units (defined when the map is created). Units are \ - measured from the centrepoint of the grid cell, hence the extra 2 ½ feet \ - added in the below example to make neat squares.
\ -Can have an optional #rrggbb hex color component appended to it as per \ - typical CSS rules.
\ -Can have an optional +x lumens value, with x equaling an integer \ +
A distance in map units as measured from the centerpoint of the grid cell.
\ +Can have additional definitions;\ +
A +x lumens value, with x equaling an integer \ (-x can instead be used to provide a negative lumens value). If not \ provided, the value will default to 100. If set to a negative number, the \ light will instead act as darkness and subtract it's area from the FoW. \ @@ -929,8 +904,9 @@ their sub-entries are alphabetically sorted.
\*Note: Personal Lights defined in Sight have a default lumens \ value of 100. So a typical sight defined for Darkvision will see through \ any lights with a lumens value of -1 through -99. To overcome Darkvision, use \ - lumens values <= -100.
Example:
\\ @@ -953,7 +929,7 @@ Darkness - 20 (CL4): circle 22.5-40
\
\Auras:
\To create an aura, put the keyword aura at the beginning of the \ -definition. Auras radiate a colored area and interact with the vision \ +definition. Auras radiate a coloured area and interact with the vision \ blocking layer (i.e. are blocked by VBL), but do not actually cast any \ visible light and do not expose any fog-of-war. GM-only auras are only \ visible by clients logged into the server as GM. They remain visible \ @@ -962,7 +938,7 @@ only visible to the player(s) who owns the token. They are always visible\ to the GM. See examples, below.
\In the following example, the GM-only auras are red, the owner-only \ auras are green, and the player auras are blue. You can of course define \ -your own colors.
\ +your own colours.\\ Sample Auras: 5' grid
\ ----
\ diff --git a/src/main/resources/net/rptools/maptool/language/i18n_en_gb.properties b/src/main/resources/net/rptools/maptool/language/i18n_en_gb.properties index 65c5a70006..93a78441a2 100644 --- a/src/main/resources/net/rptools/maptool/language/i18n_en_gb.properties +++ b/src/main/resources/net/rptools/maptool/language/i18n_en_gb.properties @@ -849,13 +849,13 @@ CampaignPropertiesDialog.label.sight = \
Range of personal light. The token will have a light source centreed on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.
\ -Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.
\ +Range of personal light. The token will have a light source centered on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.
\ +Can have an optional #rrggbb hex colour component appended to it as per typical CSS rules.
\Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.
\Ex: r60#bb0000+120
Define groups of light types with a line of text to indicate the group \ name followed by one or more name definitions. End a group with a \ -blank line. All text is case-insensitive. Lines that start with a "-" are \ -considered comments and are ignored. The group name becomes an entry on \ -the token's popup menu under the Light Sources element, and \ -individual light source definitions become sub-entries. Group names are \ -displayed in sorted order, and the sub-entries are alphabetically sorted \ -as well.
\ -Range of personal light. The token will have a light source that only they can see, centreed on them, with a radius of this value. You can define multiple personal lights per sight type.
\ -Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.
\ -Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.
\ -Ex: r60#bb0000+120
Group name\ -
\ -----------
\ -name: type shape OPTIONS scale range#rrggbb+x
Define groups of light types with a line of text to indicate the group \ -name followed by one or more name definitions. End a group with a \ blank line. All text is case-insensitive. Lines starting with a "-" are \ considered comments and are ignored. The group name becomes an entry on \ the token's popup menu under the Light Sources element, and \ @@ -904,7 +877,7 @@ their sub-entries are alphabetically sorted.
\An optional shape for the light emanation. Can be circle (default), \ - square, cone, beam, or grid†.
\ + square, cone, beam, or grid†.\Additional fields exist for beams and cones; both have an offset=y field,\ cones also have arc=y and beams have a width=y field.
\Shapes apply from the point they are included in the definition until the end of the \ @@ -912,13 +885,15 @@ their sub-entries are alphabetically sorted.
\ can be created under a single name and turned on or off as a unit.\†For systems like Pathfinder if you want to see exactly which grid cells are\ affected by a Light/Aura.
A distance measured in map units (defined when the map is created). Units are \ - measured from the centrepoint of the grid cell, hence the extra 2 ½ feet \ - added in the below example to make neat squares.
\ -Can have an optional #rrggbb hex color component appended to it as per \ - typical CSS rules.
\ -Can have an optional +x lumens value, with x equaling an integer \ +
A distance in map units as measured from the centerpoint of the grid cell.
\ +Can have additional definitions;\ +
A +x lumens value, with x equaling an integer \ (-x can instead be used to provide a negative lumens value). If not \ provided, the value will default to 100. If set to a negative number, the \ light will instead act as darkness and subtract it's area from the FoW. \ @@ -929,8 +904,9 @@ their sub-entries are alphabetically sorted.
\*Note: Personal Lights defined in Sight have a default lumens \ value of 100. So a typical sight defined for Darkvision will see through \ any lights with a lumens value of -1 through -99. To overcome Darkvision, use \ - lumens values <= -100.
Example:
\\ @@ -953,7 +929,7 @@ Darkness - 20 (CL4): circle 22.5-40
\
\Auras:
\To create an aura, put the keyword aura at the beginning of the \ -definition. Auras radiate a colored area and interact with the vision \ +definition. Auras radiate a coloured area and interact with the vision \ blocking layer (i.e. are blocked by VBL), but do not actually cast any \ visible light and do not expose any fog-of-war. GM-only auras are only \ visible by clients logged into the server as GM. They remain visible \ @@ -962,7 +938,7 @@ only visible to the player(s) who owns the token. They are always visible\ to the GM. See examples, below.
\In the following example, the GM-only auras are red, the owner-only \ auras are green, and the player auras are blue. You can of course define \ -your own colors.
\ +your own colours.\\ Sample Auras: 5' grid
\ ----
\