Copy doc tools from develop

docs/source/Server-Conf.md

@@ -5,7 +5,7 @@ Evennia runs out of the box without any changes to its settings. But there are s
 
 ## Settings file
 
-The "Settings" file referenced throughout the documentation is the file `mygame/server/conf/settings.py`. This is automatically created on the first run of `evennia --init` (see the [Getting Started](Getting-Started) page). 
+The "Settings" file referenced throughout the documentation is the file `mygame/server/conf/settings.py`. This is automatically created on the first run of `evennia --init` (see the [Getting Started](./Getting-Started) page). 
 
 Your new `settings.py` is relatively bare out of the box. Evennia's core settings file is actually [evennia/settings_default.py](https://github.com/evennia/evennia/blob/master/evennia/settings_default.py) and is considerably more extensive (it is also heavily documented so you should refer to this file directly for the available settings). 
 
@@ -38,12 +38,12 @@ Apart from the main `settings.py` file,
 - `at_initial_setup.py` - this allows you to add a custom startup method to be called (only) the very first time Evennia starts (at the same time as user #1 and Limbo is created). It can be made to start your own global scripts or set up other system/world-related things your game needs to have running from the start.
 - `at_server_startstop.py` - this module contains two functions that Evennia will call every time the Server starts and stops respectively - this includes stopping due to reloading and resetting as well as shutting down completely. It's a useful place to put custom startup code for handlers and other things that must run in your game but which has no database persistence.
 - `connection_screens.py` - all global string variables in this module are interpreted by Evennia as a greeting screen to show when an Account first connects. If more than one string variable is present in the module a random one will be picked.
-- `inlinefuncs.py` - this is where you can define custom [Inline functions](TextTags#inlinefuncs).
-- `inputfuncs.py` - this is where you define custom [Input functions](Inputfuncs) to handle data from the client.
-- `lockfuncs.py` - this is one of many possible modules to hold your own "safe" *lock functions* to make available to Evennia's [Locks](Locks).
+- `inlinefuncs.py` - this is where you can define custom [Inline functions](./TextTags#inlinefuncs).
+- `inputfuncs.py` - this is where you define custom [Input functions](./Inputfuncs) to handle data from the client.
+- `lockfuncs.py` - this is one of many possible modules to hold your own "safe" *lock functions* to make available to Evennia's [Locks](./Locks).
 - `mssp.py` - this holds meta information about your game. It is used by MUD search engines (which you often have to register with) in order to display what kind of game you are running along with
     statistics such as number of online accounts and online status.
-- `oobfuncs.py` - in here you can define custom [OOB functions](OOB).
+- `oobfuncs.py` - in here you can define custom [OOB functions](./OOB).
 - `portal_services_plugin.py` - this allows for adding your own custom services/protocols to the Portal. It must define one particular function that will be called by Evennia at startup. There can be any number of service plugin modules, all will be imported and used if defined. More info can be found [here](http://code.google.com/p/evennia/wiki/SessionProtocols#Adding_custom_Protocols).
 - `server_services_plugin.py` - this is equivalent to the previous one, but used for adding new services to the Server instead. More info can be found [here](http://code.google.com/p/evennia/wiki/SessionProtocols#Adding_custom_Protocols).