<title>Message Base | ENiGMA½ BBS Software</title>
<metaname="generator"content="Jekyll v4.2.1"/>
<metaproperty="og:title"content="Message Base"/>
<metaproperty="og:locale"content="en_US"/>
<metaname="description"content="General Information In ENiGMA½, a message base is divided into two logical grouping components: Message Conferences and Areas. Message conferences are top level containers while areas are for a specific topic. Messages are always stored internally with a area tag."/>
<metaproperty="og:description"content="General Information In ENiGMA½, a message base is divided into two logical grouping components: Message Conferences and Areas. Message conferences are top level containers while areas are for a specific topic. Messages are always stored internally with a area tag."/>
{"description":"General Information In ENiGMA½, a message base is divided into two logical grouping components: Message Conferences and Areas. Message conferences are top level containers while areas are for a specific topic. Messages are always stored internally with a area tag.","url":"/enigma-bbs/messageareas/configuring-a-message-area.html","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"/enigma-bbs/assets/images/enigma-logo.png"}},"@type":"BlogPosting","headline":"Message Base","dateModified":"2022-08-21T21:44:11+00:00","datePublished":"2022-08-21T21:44:11+00:00","mainEntityOfPage":{"@type":"WebPage","@id":"/enigma-bbs/messageareas/configuring-a-message-area.html"},"@context":"https://schema.org"}</script>
<p>In ENiGMA½, a message base is divided into two logical grouping components: <strong>Message Conferences</strong> and <strong>Areas</strong>. Message conferences are top level containers while areas are for a specific topic. Messages are always stored internally with a area tag.</p>
<h2id="conferences">Conferences</h2>
<p>Message Conferences are the top level container for <em>1:n</em> Message <em>Areas</em> via the <codeclass="language-plaintext highlighter-rouge">messageConferences</code> block in <codeclass="language-plaintext highlighter-rouge">config.hjson</code>. A common setup may include a local conference and one or more conferences each dedicated to a particular message network such as fsxNet, ArakNet, etc.</p>
<p>Each conference is represented by a entry under <codeclass="language-plaintext highlighter-rouge">messageConferences</code>. Each entries top level key is it’s <em>conference tag</em>.</p>
<p><imgclass="emoji"title=":bulb:"alt=":bulb:"src="https://github.githubassets.com/images/icons/emoji/unicode/1f4a1.png"height="20"width="20"> It is <strong>highly</strong> recommended to use snake_case style message <em>conference tags</em> and <em>area tags</em>!</p>
<td>Set to a number to override the default alpha-numeric sort order based on the <codeclass="language-plaintext highlighter-rouge">name</code> field.</td>
<td>A standard <ahref="/enigma-bbs/configuration/acs.html">ACS</a> block. See <strong>ACS</strong> below.</td>
</tr>
</tbody>
</table>
<h3id="acs">ACS</h3>
<p>An optional standard <ahref="/enigma-bbs/configuration/acs.html">ACS</a> block can be supplied with the following rules:</p>
<ul>
<li>
<codeclass="language-plaintext highlighter-rouge">read</code>: ACS required to read (see) this conference. Defaults to <codeclass="language-plaintext highlighter-rouge">GM[users]</code>.</li>
<li>
<codeclass="language-plaintext highlighter-rouge">write</code>: ACS required to write (post) to this conference. Defaults to <codeclass="language-plaintext highlighter-rouge">GM[users]</code>.</li>
</ul>
<h3id="example">Example</h3>
<pre><codeclass="language-hjson">{
messageConferences: {
local: { // conference tag
name: Local
desc: Local discussion
sort: 1
default: true
acs: {
read: GM[users] // default
}
}
}
}
</code></pre>
<h2id="message-areas">Message Areas</h2>
<p>Message Areas are topic specific containers for messages that live within a particular conference. The top level key for an area sets it’s <em>area tag</em>. For example, “General Discussion” may live under a Local conference while an fsxNet conference may contain “BBS Discussion”.</p>
<td>Set to a number to override the default alpha-numeric sort order based on the <codeclass="language-plaintext highlighter-rouge">name</code> field.</td>
<td>Set to <codeclass="language-plaintext highlighter-rouge">true</code> to use real names in this area.</td>
</tr>
</tbody>
</table>
<h3id="acs-1">ACS</h3>
<p>An optional standard <ahref="/enigma-bbs/configuration/acs.html">ACS</a> block can be supplied with the following rules:</p>
<ul>
<li>
<codeclass="language-plaintext highlighter-rouge">read</code>: ACS required to read (see) this area. Defaults to <codeclass="language-plaintext highlighter-rouge">GM[users]</code>.</li>
<li>
<codeclass="language-plaintext highlighter-rouge">write</code>: ACS required to write (post) to this area. Defaults to <codeclass="language-plaintext highlighter-rouge">GM[users]</code>.</li>
<p>FidoNet style <codeclass="language-plaintext highlighter-rouge">.na</code> files as well as legacy <codeclass="language-plaintext highlighter-rouge">AREAS.BBS</code> files in common formats can be imported using <codeclass="language-plaintext highlighter-rouge">oputil.js mb import-areas</code>. See <ahref="/enigma-bbs/admin/oputil.html">The oputil CLI</a> for more information and usage.</p>
</div>
<divclass="PageNavigation">
<aclass="btn"style="float:left;margin-right: 20px;"href="/enigma-bbs/filebase/network-mounts-and-symlinks.html">« Network Mounts & Symlinks</a>
