<p>This is relevant to you already having code in an older Evennia version. If you are new, or don’t have much code yet, it may be easier to just start fresh with the <aclass="reference internal"href="Installation.html"><spanclass="doc std std-doc">Installation</span></a> instructions and copy over things manually.</p>
<p>Prior to 1.0, all Evennia installs were <aclass="reference internal"href="Installation-Git.html"><spanclass="doc std std-doc">Git-installs</span></a>. These instructions assume that you already have a cloned <codeclass="docutils literal notranslate"><spanclass="pre">evennia</span></code> repo, and use a virtualenv (best practices).</p>
<li><p>Make sure to stop Evennia 0.9.5 entirely with <codeclass="docutils literal notranslate"><spanclass="pre">evennia</span><spanclass="pre">stop</span></code> from your game dir.</p></li>
<li><p>Delete the old virtualenv <codeclass="docutils literal notranslate"><spanclass="pre">evenv</span></code> folder, or rename it (in case you want to keep using 0.9.5 for a while).</p></li>
<li><p><codeclass="docutils literal notranslate"><spanclass="pre">cd</span></code> into your <codeclass="docutils literal notranslate"><spanclass="pre">evennia/</span></code> root folder (you want to be where you see the <codeclass="docutils literal notranslate"><spanclass="pre">docs/</span></code> and <codeclass="docutils literal notranslate"><spanclass="pre">bin/</span></code> directories as well as a nested <codeclass="docutils literal notranslate"><spanclass="pre">evennia/</span></code> folder)</p></li>
<li><p><codeclass="docutils literal notranslate"><spanclass="pre">git</span><spanclass="pre">checkout</span><spanclass="pre">main</span></code> (instead of <codeclass="docutils literal notranslate"><spanclass="pre">master</span></code> which was used for <codeclass="docutils literal notranslate"><spanclass="pre">0.9.5</span></code>)</p></li>
<p>From here on, proceed with the <aclass="reference internal"href="Installation-Git.html"><spanclass="doc std std-doc">Git Installation</span></a>, except skip cloning Evennia (since you already have the repo). Note that you can also follow the normal <aclass="reference internal"href="Installation.html"><spanclass="doc std std-doc">pip install</span></a> if you don’t need or want to use git to track bleeding edge changes nor want to be able to help contribute to Evennia itself.</p>
<p>If you don’t have anything you want to keep in your existing game dir, you can just start a new one using the normal <aclass="reference internal"href="Installation.html"><spanclass="doc std std-doc">install instructions</span></a>. If you want to keep/convert your existing game dir, continue below.</p>
<li><p>First, make a <em>backup</em> of your exising game dir! If you use version control, make sure to commit your current state.</p></li>
<li><p><codeclass="docutils literal notranslate"><spanclass="pre">cd</span></code> to your existing 0.9.5-based game folder (like <codeclass="docutils literal notranslate"><spanclass="pre">mygame</span></code>).</p></li>
<li><p>If you have changed <codeclass="docutils literal notranslate"><spanclass="pre">mygame/web</span></code>, <em>rename</em> the folder to <codeclass="docutils literal notranslate"><spanclass="pre">web_0.9.5</span></code>. If you didn’t change anything (or don’t have anything you want to keep), you can <em>delete</em> it entirely.</p></li>
<li><p>Copy <codeclass="docutils literal notranslate"><spanclass="pre">evennia/evennia/game_template/web</span></code> to <codeclass="docutils literal notranslate"><spanclass="pre">mygame/</span></code> (e.g. using <codeclass="docutils literal notranslate"><spanclass="pre">cp</span><spanclass="pre">-Rf</span></code> or a file manager). This new <codeclass="docutils literal notranslate"><spanclass="pre">web</span></code> folder <em>replaces the old one</em> and has a very different structure.</p></li>
<li><p>It’s possible you need to replace/comment out import and calls to the deprecated <aclass="reference external"href="https://docs.djangoproject.com/en/4.1/ref/urls/#url"><codeclass="docutils literal notranslate"><spanclass="pre">django.conf.urls</span></code></a>. The new way to call it is <aclass="reference external"href="https://docs.djangoproject.com/en/4.0/ref/urls/#django.urls.re_path">available here</a>.</p></li>
<li><p>Run <codeclass="docutils literal notranslate"><spanclass="pre">evennia</span><spanclass="pre">migrate</span></code> - note that it’s normal to see some warnings here, <em>don’t</em> run <codeclass="docutils literal notranslate"><spanclass="pre">makemigrations</span></code> even if the system asks you to.</p></li>
<p>If you made extensive work in your game dir, you may well find that you need to do some (hopefully minor) changes to your code before it will start with Evennia 1.0. Some important points:</p>
<li><p>The <codeclass="docutils literal notranslate"><spanclass="pre">evennia/contrib/</span></code> folder changed structure - there are now categorized sub-folders, so you have to update your imports.</p></li>
<li><p>Any <codeclass="docutils literal notranslate"><spanclass="pre">web</span></code> changes need to be moved back from your backup into the new structure of <codeclass="docutils literal notranslate"><spanclass="pre">web/</span></code> manually.</p></li>
<li><p>See the <aclass="reference internal"href="../Coding/Changelog.html"><spanclass="doc std std-doc">Evennia 1.0 Changelog</span></a> for all changes.</p></li>
