Copy doc tools from develop

docs/source/Python-basic-tutorial-part-two.md

@@ -1,13 +1,13 @@
 # Python basic tutorial part two
 
-[In the first part](Python-basic-introduction) of this Python-for-Evennia basic tutorial we learned how to run some simple Python code from inside the game. We also made our first new *module* containing a *function* that we called. Now we're going to start exploring the very important subject of *objects*.
+[In the first part](./Python-basic-introduction) of this Python-for-Evennia basic tutorial we learned how to run some simple Python code from inside the game. We also made our first new *module* containing a *function* that we called. Now we're going to start exploring the very important subject of *objects*.
 
 **Contents:**
-- [On the subject of objects](Python-basic-tutorial-part-two#on-the-subject-of-objects)
-- [Exploring the Evennia library](Python-basic-tutorial-part-two#exploring-the-evennia-library)
-- [Tweaking our Character class](Python-basic-tutorial-part-two#tweaking-our-character-class)
-- [The Evennia shell](Python-basic-tutorial-part-two#the-evennia-shell)
-- [Where to go from here](Python-basic-tutorial-part-two#where-to-go-from-here)
+- [On the subject of objects](./Python-basic-tutorial-part-two#on-the-subject-of-objects)
+- [Exploring the Evennia library](./Python-basic-tutorial-part-two#exploring-the-evennia-library)
+- [Tweaking our Character class](./Python-basic-tutorial-part-two#tweaking-our-character-class)
+- [The Evennia shell](./Python-basic-tutorial-part-two#the-evennia-shell)
+- [Where to go from here](./Python-basic-tutorial-part-two#where-to-go-from-here)
 
 ### On the subject of objects
 
@@ -114,7 +114,7 @@ evennia/
    evennia/
    ...
 ```
-There are lots of things in there. There are some docs but most of those have to do with the distribution of Evennia and does not concern us right now. The `evennia` subfolder is what we are looking for. *This* is what you are accessing when you do `from evennia import ...`. It's set up by Evennia as a good place to find modules when the server starts. The exact layout of the Evennia library [is covered by our directory overview](Directory-Overview#evennia-library-layout). You can also explore it [online on github](https://github.com/evennia/evennia/tree/master/evennia).
+There are lots of things in there. There are some docs but most of those have to do with the distribution of Evennia and does not concern us right now. The `evennia` subfolder is what we are looking for. *This* is what you are accessing when you do `from evennia import ...`. It's set up by Evennia as a good place to find modules when the server starts. The exact layout of the Evennia library [is covered by our directory overview](./Directory-Overview#evennia-library-layout). You can also explore it [online on github](https://github.com/evennia/evennia/tree/master/evennia).
 
 The structure of the library directly reflects how you import from it.
 
@@ -123,7 +123,7 @@ The structure of the library directly reflects how you import from it.
 - You could also do `import evennia`. You would then have to enter the full `evennia.utils.utils.justify(...)` every time you use it. Using `from` to only import the things you need is usually easier and more readable.
 - See [this overview](http://effbot.org/zone/import-confusion.htm) about the different ways to import in Python.
 
-Now, remember that our `characters.py` module did `from evennia import DefaultCharacter`. But if we look at the contents of the `evennia` folder, there is no `DefaultCharacter` anywhere! This is because Evennia gives a large number of optional "shortcuts", known as [the "flat" API](Evennia-API). The intention is to make it easier to remember where to find stuff. The flat API is defined in that weirdly named `__init__.py` file. This file just basically imports useful things from all over Evennia so you can more easily find them in one place.
+Now, remember that our `characters.py` module did `from evennia import DefaultCharacter`. But if we look at the contents of the `evennia` folder, there is no `DefaultCharacter` anywhere! This is because Evennia gives a large number of optional "shortcuts", known as [the "flat" API](./Evennia-API). The intention is to make it easier to remember where to find stuff. The flat API is defined in that weirdly named `__init__.py` file. This file just basically imports useful things from all over Evennia so you can more easily find them in one place.
 
 We could [just look at the documenation](github:evennia#typeclasses) to find out where we can look at our `DefaultCharacter` parent. But for practice, let's figure it out. Here is where `DefaultCharacter` [is imported from](https://github.com/evennia/evennia/blob/master/evennia/__init__.py#L188) inside `__init__.py`:
 
@@ -147,7 +147,7 @@ is the same thing, just a little easier to remember.
 
 > To access the shortcuts of the flat API you *must* use `from evennia import
 > ...`. Using something like `import evennia.DefaultCharacter` will not work.
-> See [more about the Flat API here](Evennia-API).
+> See [more about the Flat API here](./Evennia-API).
 
 
 ### Tweaking our Character class
@@ -199,7 +199,7 @@ class DefaultCharacter(DefaultObject):
 
 ... And so on (you can see the full [class online here](https://github.com/evennia/evennia/blob/master/evennia/objects/objects.py#L1915)). Here we have functional code! These methods may not be directly visible in `Character` back in our game dir, but they are still available since `Character` is a child of `DefaultCharacter` above. Here is a brief summary of the methods we find in `DefaultCharacter` (follow in the code to see if you can see roughly where things happen)::
 
-- `basetype_setup` is called by Evennia only once, when a Character is first created. In the `DefaultCharacter` class it sets some particular [Locks](Locks) so that people can't pick up and puppet Characters just like that. It also adds the [Character Cmdset](Command-Sets) so that Characters always can accept command-input (this should usually not be modified - the normal hook to override is `at_object_creation`, which is called after `basetype_setup` (it's in the parent)).
+- `basetype_setup` is called by Evennia only once, when a Character is first created. In the `DefaultCharacter` class it sets some particular [Locks](./Locks) so that people can't pick up and puppet Characters just like that. It also adds the [Character Cmdset](./Command-Sets) so that Characters always can accept command-input (this should usually not be modified - the normal hook to override is `at_object_creation`, which is called after `basetype_setup` (it's in the parent)).
 - `at_after_move` makes it so that every time the Character moves, the `look` command is automatically fired (this would not make sense for just any regular Object).
 - `at_pre_puppet` is called when an Account begins to puppet this Character. When not puppeted, the Character is hidden away to a `None` location. This brings it back to the location it was in before. Without this, "headless" Characters would remain in the game world just standing around.
 - `at_post_puppet` is called when puppeting is complete. It echoes a message to the room that his Character has now connected.
@@ -301,8 +301,7 @@ If you did this call from your game dir you will now be in a Python prompt manag
 
     IPython ...
     ...
-    In [1]:
-
+    In [1]: 
 IPython has some very nice ways to explore what Evennia has to offer.
 
     > import evennia
@@ -324,10 +323,10 @@ This will show us the changed code we just did. Having a window with IPython run
 
 ### Where to go from here
 
-This should give you a running start using Python with Evennia. If you are completely new to programming or Python you might want to look at a more formal Python tutorial. You can find links and resources [on our link page](Links).
+This should give you a running start using Python with Evennia. If you are completely new to programming or Python you might want to look at a more formal Python tutorial. You can find links and resources [on our link page](./Links).
 
 We have touched upon many of the concepts here but to use Evennia and to be able to follow along in the code, you will need basic understanding of Python [modules](http://docs.python.org/2/tutorial/modules.html), [variables](http://www.tutorialspoint.com/python/python_variable_types.htm), [conditional statements](http://docs.python.org/tutorial/controlflow.html#if-statements), [loops](http://docs.python.org/tutorial/controlflow.html#for-statements), [functions](http://docs.python.org/tutorial/controlflow.html#defining-functions), [lists, dictionaries, list comprehensions](http://docs.python.org/tutorial/datastructures.html) and [string formatting](http://docs.python.org/tutorial/introduction.html#strings). You should also have a basic understanding of [object-oriented programming](http://www.tutorialspoint.com/python/python_classes_objects.htm) and what Python [Classes](http://docs.python.org/tutorial/classes.html) are.
 
-Once you have familiarized yourself, or if you prefer to pick Python up as you go, continue to one of the beginning-level [Evennia tutorials](Tutorials) to gradually build up your understanding.
+Once you have familiarized yourself, or if you prefer to pick Python up as you go, continue to one of the beginning-level [Evennia tutorials](./Tutorials) to gradually build up your understanding.
 
 Good luck!