Skip to content

Commit

Permalink
Merge pull request #4517 from bubblobill/LineLight
Browse files Browse the repository at this point in the history
i18n language files updated for new beam light type
  • Loading branch information
cwisniew authored Dec 7, 2023
2 parents dd01594 + 04fd49a commit bffb47d
Show file tree
Hide file tree
Showing 3 changed files with 126 additions and 198 deletions.
104 changes: 40 additions & 64 deletions src/main/resources/net/rptools/maptool/language/i18n.properties
Original file line number Diff line number Diff line change
Expand Up @@ -846,75 +846,52 @@ CampaignPropertiesDialog.label.sight = <html>\
<p><b> Options:</b></p>\
<dl>\
<dt>shape</dt><dd>shape may be circle, square, hex, grid, cone or beam</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center</dd>\
<dt>arc=y</dt><dd><p>When used with the cone shape, it signifies how wide a field of vision the token has. Can be an integer value. e,g, arc=120</p>\
<p>When used with the beam shape, it determines how wide the beam will be. Can be an integer value from 0 to 180, e.g. arc=4</p></dd>\
<dt>offset=y</dt><dd>When used with the cone or beam shape, it signifies how many degrees off centre the shape begins. Can be an integer value. e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view the token has. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>r#</dt><dd><p>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.</p>\
<p>Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.</p>\
<p>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.</p>\
<p>Ex: r60#bb0000+120</p></dd>\
</dl>\
</html>

CampaignPropertiesDialog.label.light = <html>\
<b>Format:</b> \
<pre>Group name<br>\
----------<br>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> definitions. End a group with a \
blank line. All text is case-insensitive. Lines that start with a "-" are \
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 <b>Light Sources</b> 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.</p>\
individual light source definitions become sub-entries. Group names and \
their sub-entries are alphabetically sorted.</p>\
<dl>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd>shape may be circle, square, hex, grid, cone or beam</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center</dd>\
<dt>arc=y</dt><dd><p>When used with the cone shape, it signifies how large a field of vision the token has. Can be an integer value. e,g, arc=120</p>\
<p>When used with the beam shape, it determines how wide the beam will be. Can be an integer value from 0 to 180, e.g. arc=4</p></dd>\
<dt>offset=y</dt><dd>When used with the cone or beam shape, it signifies how many degrees off centre the shape begins. Can be an integer value. e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>r#</dt><dd><p>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.</p>\
<p>Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.</p>\
<p>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.</p>\
<p>Ex: r60#bb0000+120</p></dd>\
</dl>\
<b>Format:</b> \
<pre>Group name<br>\
----------<br>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> 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 <b>Light Sources</b> 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.</p>\
<dl>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd>An optional shape for the light emanation. Can be <b>circle</b> (default), \
<b>square</b>, <b>cone</b>, <b>beam</b> (beams and cones also have <b>arc=<i>angle</i></b> and \
<b>offset=<i>y</i></b> fields) or <b>grid</b> (for systems like Pathfinder if \
you want to see exactly which grid cells are affected by a Light/Aura). Shapes \
apply from the point they are included in the definition until the end of the \
<dt>shape</dt><dd><p>An optional shape for the light emanation. Can be <b>circle</b> (default), \
<b>square</b>, <b>cone</b>, <b>beam</b>, or <b>grid</b>&dagger;.</p>\
<p>Additional fields exist for beams and cones; both have an <b>offset=<i>y</i></b> field,\
cones also have <b>arc=<i>y</i></b> and beams have a <b>width=<i>y</i></b> field.</p>\
<p>Shapes apply from the point they are included in the definition until the end of the \
definition or until another shape is specified. This means multiple light shapes \
can be created under a single name and turned on or off as a unit.</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the range so the light/aura starts at token's edge vs the token's center.</dd>\
<dt>range</dt><dd><p>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 &#189; feet \
added in the below example to make neat squares.</p>\
<p>Can have an optional <i>#rrggbb</i> hex color component appended to it as per \
typical CSS rules.</p>\
<p>Can have an optional <i>+x</i> lumens value, with x equaling an integer \
can be created under a single name and turned on or off as a unit.</p>\
<p>&dagger;<i>For systems like Pathfinder if you want to see exactly which grid cells are\
affected by a Light/Aura.</i></p></dd>\
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view covered by the light. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>range</dt><dd><p>A distance in map units as measured from the centerpoint of the grid cell.</p>\
<p>Can have additional definitions;\
<ul><li>A <i>#rrggbb</i> hex color component appended to determine color.</li>\
<li><p>A <i>+x</i> lumens value, with x equaling an integer \
(<i>-x</i> 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. \
Expand All @@ -925,8 +902,9 @@ as well.</p>\
<p><i>*Note:</i> Personal Lights defined in <i>Sight</i> 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 &lt;= -100.</p></dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
lumens values &lt;= -100.</p>\
</li>\
</ul></dd>\
</dl>\
<p><b>Example:</b></p>\
<pre>\
Expand Down Expand Up @@ -979,24 +957,22 @@ five and six are visible to all players and are in blue.</p>\
New Interesting Auras: 5' grid<br>\
----<br>\
Side Fields - 12.5: aura cone arc=90 12.5#6666ff offset=90 12.5#aadd00 offset=-90 12.5#aadd00 offset=180 12.5#bb00aa<br>\
Doughnut Hole - 40: aura circle 20 40#ffff00<br>\
Doughnut Cone - 20: aura cone arc=30 10 20#ffff00<br>\
Donut Hole - 40: aura circle 20 40#ffff00<br>\
Donut Cone - 20: aura cone arc=30 10 20#ffff00<br>\
Range Circles 30/60/90: aura circle 30.5 30.9#000000 60.5 60.9#000000 90.5 90.9#000000<br>\
Range Arcs 30/60/90: aura cone arc=135 30.5 30.9#000000 60.5 60.9#000000 90.5 90.9#000000<br>\
Beam - 50: aura beam arc=4 150#ffff00<br>\
Beam - 150: aura beam width=0.4 150#ffff00<br>\
</pre>\
<dl>\
<dt>Side fields</dt><dd>4 cones with an arc of 90 degrees and range of 12.5.\
Each one offset to cover a different region.</dd>\
<dt>Doughnut Hole</dt><dd>This one hides a secret. If you have a range with\
no colour it becomes the range the light source begins. In this case the light\
begins at 20 and ends at 40.</dd>\
<dt>Doughnut Cone</dt><dd>The same trick done with a cone.</dd>\
<dt>Range Circles</dt><dd>A series of circles starting every\
30 ft and ending 0.4 ft later.</dd>\
Each one offset to cover a different region.</dd>\
<dt>Dounut Hole</dt><dd>This one hides a secret. If you have a range with\
no colour it becomes the range the light source begins. In this case the light\
begins at 20 and ends at 40.</dd>\
<dt>Donut Cone</dt><dd>The same trick done with a cone.</dd>\
<dt>Range Circles</dt><dd>A series of circles starting every 30 ft and ending 0.4 ft later.</dd>\
<dt>Range Arcs</dt><dd>Another repeat, this one using cones.</dd>\
<dt>Beam</dt><dd>A beam 150 ft long. The arc determines its width\
and is 4 degrees. At 180 degrees it would be as wide as the token.</dd>\
<dt>Beam</dt><dd>A beam 150 ft long with a width of 0.4 map units</dd>\
</html>
CampaignPropertiesDialog.label.title = Campaign Properties
CampaignPropertiesDialog.label.group = Group:
Expand Down
Loading

0 comments on commit bffb47d

Please sign in to comment.