<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-NZ link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Good news Bill<o:p></o:p></p><p class=MsoNormal>A well-earned success. I had noticed you were likely to run into name conflicts, so glad you figured that out.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>><span style='font-family:"Courier New"'>Regarding the strange offsets of [0 0 ft] - That is intentional. If I did not do the offset with "above" or "below", then the transparency effects did not work. It was not clear which passage was above or below. They were all mashed together as if they were one layer.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It seems like you may have missed part of the recipe. When defining maps composed of scraps, you need to place the scraps more or less in order of their altitude, with the highest passage at the top of the list. This in itself makes no difference to how they will render, but in the situation where one overlies another, insert a break statement. See page 31 of the current Therion Book under ‘map’.<o:p></o:p></p><p class=MsoNormal>You do not need a break if your map is composed of other maps, because it turns out that Therion inserts an implied break in this situation. But you still need to sort your map definitions with the overlying maps at the top of the list for this to render as you would want it to.<o:p></o:p></p><p class=MsoNormal>An as I think you are aware; you need to turn transparency on and set an appropriate opacity value.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> transparency on # see thru passages<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> #transparent = 0 <= opacity <= 100 = opaque<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> opacity 50 # degree of transparency <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> #00 = transparent, 100 = block out<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> #40 = subtle, 60 - 70 = apparent: overwritten text still visible<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> #80 = good passage definition but overwritten text barely visible <o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>Still, I had not thought of the approach you have taken. Maybe darkening up the underlying scraps locally is an interesting style approach to explore (in conjunction with the above).<span style='font-family:"Courier New"'><o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt;-qt-block-indent:0;-qt-user-state:0'><span style='font-family:"Courier New"'>>Does the naming convention of "name@place" extend to more than one layer? Is something like "name@cave@space" possible? Could I write something like AllieMainPlan@AllieSpringCave@BCRPlanMap"?<br><br><o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;-qt-paragraph-type:empty;-qt-block-indent:0'>Of course, as many levels as you like to set up in your project structure, except the syntax is name@place.cave.mastercaves<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>Only one @, then use dots.<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>One comment I would make, the BigCavernRanch project folder structure is very flat (which is generally a good thing), but now that the Therion data structure is nested (BigCavernRanch includes 4 caves), it might be a good idea to make the folder structure mirror the data structure. This will make the data structure easier to visualise, and in future make it easier to merge with adjacent cave project data (or split out individual cave projects).<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>ie folder structure should mirror the data structure;<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-BigCavernRanch<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'> |-AllieSpring<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'> |-CascadeCaverns<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'> |-MillCreek<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'> |-ShiftyRock<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>And not the current situation in which it is not possible to infer the data structure;<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-AllieSpring<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-BigCavernRanch<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-CascadeCaverns<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-MillCreek<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>-ShiftyRock<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt'>Bruce<o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt;-qt-block-indent:0;-qt-user-state:0'><span style='font-family:"Courier New"'><o:p> </o:p></span></p></div></body></html>