Update 'MagicBox : Magicbane in a Box'

MagicBox-%3A-Magicbane-in-a-Box.md

@@ -126,5 +126,27 @@ The vigilant MagicBox administrator will always pay close attention to console_l
 
 Upon bootstrap MagicBox will first look for a [magicbane.conf](http://repo.magicbane.com/MagicBane/Server/wiki/magicbane.conf) file within the mb.conf host directory we mounted in the run command. If it cannot be found the game will instead use a default copy inside mb.data/ to boot with.  This configuration boots using an internal MySQL server with a fresh database.
 
+The game will inform you on bootstrap the location of the .conf file it is using.
+
+```console
+[mbbox@mta6 ~]$ ./magicbox.sh
+Killing running MagicBox images...
+Starting MagicBox
+[mbbox@mta6 ~]$ Configure using mb.data/magicbane.conf
+```
+
+This shows that MagicBox did not detect a configuration file in mb.conf/ and is therefore booting with the internal config.
+
 >Note that a container is ephemeral.  When the container stops all changes to it are lost.  This includes the internal database.  If you want your world to persist supply a config file that points to an external mysql database instance.  This can be a done via the [MySQL docker image](https://hub.docker.com/r/mysql/mysql-server) in just a few commands.  Details are found on the [MagicBox to Server]() page.
 
+
+At the very least a new MagicBox administrator might wish for to change the world name to suit his fancy.
+
+`MB_WORLD_NAME="MagicBox"`
+
+It is advised that the Magicbox administrator ***not*** edit the following values.
+
+```MB_PUBLIC_ADDR="0.0.0.0"``` <br>
+```MB_BIND_ADDR="0.0.0.0"```
+
+This instructs Magicbane to self-configure the bind address and public facing ip.