Change to MyST parser

docs/source/Howto/Evennia-for-roleplaying-sessions.md

@@ -26,12 +26,12 @@ defaults for our particular use-case. Below we will flesh out these components f
 
 ## Starting out
 
-We will assume you start from scratch. You need Evennia installed, as per the [Setup Quickstart](../Setup/Setup-Quickstart) 
+We will assume you start from scratch. You need Evennia installed, as per the [Setup Quickstart](../Setup/Setup-Quickstart.md) 
 instructions. Initialize a new game directory with `evennia init
 <gamedirname>`. In this tutorial we assume your game dir is simply named `mygame`. You can use the
 default database and keep all other settings to default for now. Familiarize yourself with the
 `mygame` folder before continuing. You might want to browse the 
-[First Steps Coding](Starting/Part1/Starting-Part1) tutorial, just to see roughly where things are modified.
+[First Steps Coding](Starting/Part1/Starting-Part1.md) tutorial, just to see roughly where things are modified.
 
 ## The Game Master role
 
@@ -44,7 +44,7 @@ to show your renewed GM status to the other accounts.
 
 ### The permission hierarchy
 
-Evennia has the following [permission hierarchy](../Concepts/Building-Permissions#assigning-permissions) out of
+Evennia has the following [permission hierarchy](../Concepts/Building-Permissions.md#assigning-permissions) out of
 the box: *Players, Helpers, Builders, Admins* and finally *Developers*. We could change these but
 then we'd need to update our Default commands to use the changes. We want to keep this simple, so
 instead we map our different roles on top of this permission ladder.
@@ -60,7 +60,7 @@ everyone.
 5. `Developers`-level permission are the server administrators, the ones with the ability to
 restart/shutdown the server as well as changing the permission levels.
 
-> The [superuser](../Concepts/Building-Permissions#the-super-user) is not part of the hierarchy and actually
+> The [superuser](../Concepts/Building-Permissions.md#the-super-user) is not part of the hierarchy and actually
 completely bypasses it. We'll assume server admin(s) will "just" be Developers.
 
 ### How to grant permissions
@@ -102,7 +102,7 @@ its name will have the string`(GM)` added to the end.
 #### Character modification
 
 Let's first start by customizing the Character. We recommend you browse the beginning of the
-[Account](../Components/Accounts) page to make sure you know how Evennia differentiates between the OOC "Account
+[Account](../Components/Accounts.md) page to make sure you know how Evennia differentiates between the OOC "Account
 objects" (not to be confused with the `Accounts` permission, which is just a string specifying your
 access) and the IC "Character objects".
 
@@ -141,7 +141,7 @@ Above, we change how the Character's name is displayed: If the account controlli
 a GM, we attach the string `(GM)` to the Character's name so everyone can tell who's the boss. If we
 ourselves are Developers or GM's we will see database ids attached to Characters names, which can
 help if doing database searches against Characters of exactly the same name. We base the "gm-
-ingness" on having an flag (an [Attribute](../Components/Attributes)) named `is_gm`. We'll make sure new GM's
+ingness" on having an flag (an [Attribute](../Components/Attributes.md)) named `is_gm`. We'll make sure new GM's
 actually get this flag below.
 
 > **Extra exercise:** This will only show the `(GM)` text on *Characters* puppeted by a GM account,
@@ -151,7 +151,7 @@ that is, it will show only to those in the same location. If we wanted it to als
 
 #### New @gm/@ungm command
 
-We will describe in some detail how to create and add an Evennia [command](../Components/Commands) here with the
+We will describe in some detail how to create and add an Evennia [command](../Components/Commands.md) here with the
 hope that we don't need to be as detailed when adding commands in the future. We will build on
 Evennia's default "mux-like" commands here.
 
@@ -266,7 +266,7 @@ We will here show two examples using the *EvTable* and *EvForm* utilities.Later
 Commands to edit and display the output from those utilities.
 
 > Note that due to the limitations of the wiki, no color is used in any of the examples. See 
-> [the text tag documentation](../Concepts/TextTags) for how to add color to the tables and forms.
+> [the text tag documentation](../Concepts/TextTags.md) for how to add color to the tables and forms.
 
 #### Making a sheet with EvTable
 
@@ -686,7 +686,7 @@ implemented.
 ## Rooms
 
 Evennia comes with rooms out of the box, so no extra work needed. A GM will automatically have all
-needed building commands available. A fuller go-through is found in the [Building tutorial](Starting/Part1/Building-Quickstart).
+needed building commands available. A fuller go-through is found in the [Building tutorial](Starting/Part1/Building-Quickstart.md).
 Here are some useful highlights:
 
 * `@dig roomname;alias = exit_there;alias, exit_back;alias` - this is the basic command for digging
@@ -704,7 +704,7 @@ access after the fact.
 
 ## Channels
 
-Evennia comes with [Channels](../Components/Communications#Channels) in-built and they are described fully in the
+Evennia comes with [Channels](../Components/Channels.md) in-built and they are described fully in the
 documentation. For brevity, here are the relevant commands for normal use:
 
 * `@ccreate new_channel;alias;alias = short description` - Creates a new channel.