<dt>Part 2: <aclass="reference external"href="../Part2/Starting-Part2.html">What we want</a></dt><dd><p>Planning our tutorial game and what to think about when planning your own in the future.</p>
<dt>Part 3: <aclass="reference external"href="../Part3/Starting-Part3.html">How we get there</a></dt><dd><p>Getting down to the meat of extending Evennia to make our game</p>
<dt>Part 4: <aclass="reference external"href="../Part4/Starting-Part4.html">Using what we created</a></dt><dd><p>Building a tech-demo and world content to go with our code</p>
<dt>Part 5: <aclass="reference external"href="../Part5/Starting-Part5.html">Showing the world</a></dt><dd><p>Taking our new game online and let players try it out</p>
<p>In this first part we’ll focus on what we get out of the box in Evennia - we’ll get used to the tools,
and how to find things we are looking for. We will also dive into some of things you’ll
need to know to fully utilize the system, including giving you a brief rundown of Python concepts. If you are
an experienced Python programmer, some sections may feel a bit basic, but you will at least not have seen
these concepts in the context of Evennia before.</p>
</div>
<divclass="section"id="things-you-will-need">
<h2>Things you will need<aclass="headerlink"href="#things-you-will-need"title="Permalink to this headline">¶</a></h2>
<divclass="section"id="a-command-line">
<h3>A Command line<aclass="headerlink"href="#a-command-line"title="Permalink to this headline">¶</a></h3>
<p>First of all, you need to know how to find your Terminal/Console in your OS. The Evennia server can be controlled
from in-game, but you <em>will</em> need to use the command-line to get anywhere. Here are some starters:</p>
<ulclass="simple">
<li><p><aclass="reference external"href="https://tutorial.djangogirls.org/en/intro_to_command_line/">Django-girls’ Intro to the Command line for different OS:es</a></p></li>
</ul>
<blockquote>
<div><p>Note that we only use forward-slashes <codeclass="docutils literal notranslate"><spanclass="pre">/</span></code> to show file system paths in this documentation. Windows users need
to convert this to back-slashes <codeclass="docutils literal notranslate"><spanclass="pre">\</span></code> in their heads.</p>
</div></blockquote>
</div>
<divclass="section"id="a-mud-client">
<h3>A MUD client<aclass="headerlink"href="#a-mud-client"title="Permalink to this headline">¶</a></h3>
<p>You might already have a MUD-client you prefer. Check out the <aclass="reference internal"href="../../../Setup/Client-Support-Grid.html"><spanclass="doc">grid of supported clients</span></a> for aid.
If telnet’s not your thing, you can also just use Evennia’s web client in your browser.</p>
<blockquote>
<div><p>In this documentation we often use ‘MUD’ and ‘MU’ or ‘MU*’ interchangeably
as labels to represent all the historically different forms of text-based multiplayer game-styles,
like MUD, MUX, MUSH, MUCK, MOO and others. Evennia can be used to create all those game-styles
and more.</p>
</div></blockquote>
</div>
<divclass="section"id="an-editor">
<h3>An Editor<aclass="headerlink"href="#an-editor"title="Permalink to this headline">¶</a></h3>
<p>You need a text-editor to edit Python source files. Most everything that can edit and output raw
text works (so not Word).</p>
<ulclass="simple">
<li><p><aclass="reference external"href="https://www.elegantthemes.com/blog/resources/best-code-editors">Here’s a blog post summing up some of the alternatives</a> - these
things don’t change much from year to year. Popular choices for Python are PyCharm, VSCode, Atom, Sublime Text and Notepad++.
Evennia is to a very large degree coded in VIM, but that’s not suitable for beginners.</p></li>
</ul>
<blockquote>
<div><p>Hint: When setting up your editor, make sure that pressing TAB inserts <em>4 spaces</em> rather than a Tab-character. Since
Python is whitespace-aware, this will make your life a lot easier.</p>
<p>Next you should make sure you have <aclass="reference internal"href="../../../Setup/Setup-Quickstart.html"><spanclass="doc">installed Evennia</span></a>. If you followed the instructions
<div><p>If you want to run two parallel servers, that’d be fine too, but one would have to use
different ports from the defaults, or there’d be a clash. We will go into changing settings later.</p>
</div></blockquote>
<ul>
<li><p>Now go to where you want to create your tutorial-game. We will always refer to it as <codeclass="docutils literal notranslate"><spanclass="pre">mygame</span></code> so
<p>Add your superuser name and password at the prompt (email is optional). Make sure you can
go to <codeclass="docutils literal notranslate"><spanclass="pre">localhost:4000</span></code> in your MUD client or to <aclass="reference external"href="http://localhost:4001">http://localhost:4001</a>
in your web browser (Mac users: Try <codeclass="docutils literal notranslate"><spanclass="pre">127.0.0.1</span></code> instead of <codeclass="docutils literal notranslate"><spanclass="pre">localhost</span></code> if you have trouble).</p>
<p>The above <codeclass="docutils literal notranslate"><spanclass="pre">--log</span></code> flag will have Evennia output all its logs to the terminal. This will block
the terminal from other input. To leave the log-view, press <codeclass="docutils literal notranslate"><spanclass="pre">Ctrl-C</span></code> (<codeclass="docutils literal notranslate"><spanclass="pre">Cmd-C</span></code> on Mac). To see
