Expand tutorial on equipmenthandler

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Adding-Commands.md

@@ -181,7 +181,7 @@ class CmdEcho(Command):
 First we added a docstring. This is always a good thing to do in general, but for a Command class, it will also
 automatically become the in-game help entry! Next we add the `func` method. It has one active line where it
 makes use of some of those variables we found the Command offers to us. If you did the
-[basic Python tutorial](./Python-basic-introduction.md), you will recognize `.msg` - this will send a message
+[basic Python tutorial](./Beginner-Tutorial-Python-basic-introduction.md), you will recognize `.msg` - this will send a message
 to the object it is attached to us - in this case `self.caller`, that is, us. We grab `self.args` and includes
 that in the message.
 

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Building-Quickstart.md

@@ -149,7 +149,7 @@ the raw description of your current room (including color codes), so that you ca
 set its description to something else.
 
 You create new Commands (or modify existing ones) in Python outside the game. We will get to that
-later, in the [Commands tutorial](./Adding-Commands.md).
+later, in the [Commands tutorial](./Beginner-Tutorial-Adding-Commands.md).
 
 ## Get a Personality
 

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Gamedir-Overview.md

@@ -200,7 +200,7 @@ people change and re-structure this in various ways to better fit their ideas.
 
 - [batch_cmds.ev](github:evennia/game_template/world/batch_cmds.ev) - This is an `.ev` file, which is essentially
     just a list of Evennia commands to execute in sequence. This one is empty and ready to expand on. The 
-    [Tutorial World](./Tutorial-World.md) was built with such a batch-file.
+    [Tutorial World](./Beginner-Tutorial-Tutorial-World.md) was built with such a batch-file.
 - [prototypes.py](github:evennia/game_template/world/prototypes.py) - A [prototype](../../../Components/Prototypes.md) is a way
     to easily vary objects without changing their base typeclass. For example, one could use prototypes to 
     tell that Two goblins, while both of the class 'Goblin' (so they follow the same code logic), should have different 

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Learning-Typeclasses.md

@@ -251,7 +251,7 @@ You are specifying exactly which typeclass you want to use to build the Giantess
      desc = You see nothing special. 
     ------------------------------------------------------------------------------- 
 
-We used the `examine` command briefly in the [lesson about building in-game](./Building-Quickstart.md). Now these lines
+We used the `examine` command briefly in the [lesson about building in-game](./Beginner-Tutorial-Building-Quickstart.md). Now these lines
 may be more useful to us:
 - **Name/key** - The name of this thing. The value `(#14)` is probably different for you. This is the 
     unique 'primary key' or _dbref_ for this entity in the database.
@@ -357,7 +357,7 @@ You got a lot longer output this time. You have a lot more going on than a simpl
 - **Session id(s)**: This identifies the _Session_ (that is, the individual connection to a player's game client).
 - **Account** shows, well the `Account` object associated with this Character and Session.
 - **Stored/Merged Cmdsets** and **Commands available** is related to which _Commands_ are stored on you. We will
-    get to them in the [next lesson](./Adding-Commands.md). For now it's enough to know these consitute all the 
+    get to them in the [next lesson](./Beginner-Tutorial-Adding-Commands.md). For now it's enough to know these consitute all the 
     commands available to you at a given moment. 
 - **Non-Persistent attributes** are Attributes that are only stored temporarily and will go away on next reload.
 

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-More-on-Commands.md

@@ -143,8 +143,8 @@ change (no code changed, only stuff in the database).
 ## Adding a Command to an object
 
 The commands of a cmdset attached to an object with `obj.cmdset.add()` will by default be made available to that object
-but _also to those in the same location as that object_. If you did the [Building introduction](./Building-Quickstart.md)
-you've seen an example of this with the "Red Button" object. The [Tutorial world](./Tutorial-World.md)
+but _also to those in the same location as that object_. If you did the [Building introduction](./Beginner-Tutorial-Building-Quickstart.md)
+you've seen an example of this with the "Red Button" object. The [Tutorial world](./Beginner-Tutorial-Tutorial-World.md)
 also has many examples of objects with commands on them.
 
 To show how this could work, let's put our 'hit' Command on our simple `sword` object from the previous section.

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Part1-Intro.md

@@ -30,18 +30,18 @@ these concepts in the context of Evennia before.
 :maxdepth: 1
 :numbered:
 
-Building-Quickstart
-Tutorial-World
-Python-basic-introduction
-Gamedir-Overview
-Python-classes-and-objects
-Evennia-Library-Overview
-Learning-Typeclasses
-Adding-Commands
-More-on-Commands
-Creating-Things
-Searching-Things
-Django-queries
+Beginner-Tutorial-Building-Quickstart
+Beginner-Tutorial-Tutorial-World
+Beginner-Tutorial-Python-basic-introduction
+Beginner-Tutorial-Gamedir-Overview
+Beginner-Tutorial-Python-classes-and-objects
+Beginner-Tutorial-Evennia-Library-Overview
+Beginner-Tutorial-Learning-Typeclasses
+Beginner-Tutorial-Adding-Commands
+Beginner-Tutorial-More-on-Commands
+Beginner-Tutorial-Creating-Things
+Beginner-Tutorial-Searching-Things
+Beginner-Tutorial-Django-queries
 
 ```
 
@@ -50,17 +50,17 @@ Django-queries
 ```{toctree}
 :maxdepth: 2
 
-Building-Quickstart
-Tutorial-World
-Python-basic-introduction
-Gamedir-Overview
-Python-classes-and-objects
-Evennia-Library-Overview
-Learning-Typeclasses
-Adding-Commands
-More-on-Commands
-Creating-Things
-Searching-Things
-Django-queries
+Beginner-Tutorial-Building-Quickstart
+Beginner-Tutorial-Tutorial-World
+Beginner-Tutorial-Python-basic-introduction
+Beginner-Tutorial-Gamedir-Overview
+Beginner-Tutorial-Python-classes-and-objects
+Beginner-Tutorial-Evennia-Library-Overview
+Beginner-Tutorial-Learning-Typeclasses
+Beginner-Tutorial-Adding-Commands
+Beginner-Tutorial-More-on-Commands
+Beginner-Tutorial-Creating-Things
+Beginner-Tutorial-Searching-Things
+Beginner-Tutorial-Django-queries
 
 ```

docs/source/Howtos/Beginner-Tutorial/Part1/Python-classes-and-objects.md

@@ -93,7 +93,7 @@ The form `from ... import ... as ...` renames the import.
 > Avoid renaming unless it's to avoid a name-collistion like above - you want to make things as
 > easy to read as possible, and renaming adds another layer of potential confusion.
 
-In [the basic intro to Python](./Python-basic-introduction.md) we learned how to open the in-game
+In [the basic intro to Python](./Beginner-Tutorial-Python-basic-introduction.md) we learned how to open the in-game
 multi-line interpreter.
 
     > py
@@ -153,7 +153,7 @@ Next we have a `class` named `Object`, which _inherits_ from `DefaultObject`. Th
 actually do anything on its own, its only code (except the docstring) is `pass` which means,
 well, to pass and don't do anything.
 
-We will get back to this module in the [next lesson](./Learning-Typeclasses.md). First we need to do a
+We will get back to this module in the [next lesson](./Beginner-Tutorial-Learning-Typeclasses.md). First we need to do a
 little detour to understand what a 'class', an 'object' or 'instance' is. These are fundamental
 things to understand before you can use Evennia efficiently.
 ```{sidebar} OOP