Okay, heres the skinny on this system.

This allows you to create a library file for your mud, not only is this cool, but it has its benefits.
You can move vital functions to this library, things that don't need to be worked on readily, and by doing so
you move vital functionality out of the code that hits the server.

This system is only useful for people who code offline, and then put their code online. The overall goal
is so that you write your lib offline, and upload it with your code, minus the code that went into your server
application.

Now, you place somwhere outside of your home-directory, a licence file, whatever you want to name it,
you may have to get your site-owner to place the file for you, because you may not have access to it.

That being said, once you do that, the code will look for said licence file, and if it isn't there, the mud will
email the servers root@localhost address, and notify them that X user is using stolen code.

And it will also notify your email address if someone is using your source-code.

Once that is done, the mud will lockup, in a function, i like to call… endless_loop.

The goal is to ensure that if someone is using your mud code without your permission, that they cannot infact
use it unless they replace all the code that went into the library file, so if you put the loading/saving routines
into it, and they don't have the licence, then they = toasted.

This is a great deterant to coders that you've hired to work on your code that edit code online. sure they can
run off with your code, but they can't exactly use it unless they have the licence, or they have the lib source.

Anyways, enjoy, this is a simple tutorial, you'll all have to take it further then it is. But it is fully functional :)