 ------------------------------------------------------
><><><><><><><><><><><><><><><><><><><><><><><><><><><><
 ------------------------------------------------------
     DeusEx Log output catcher
     
	Version: 1.0
	--------------
	Released: 11th February 2007
	--------------
	Author: ~[A]Nobody~
	--------------
	URL: www.dxalpha.com

	 
	--------------
	Copyright Notes: 
	
This mod was not made and is not supported by Ion Storm and Eidos Interactive.
You may distribute this mod, as long as it is free of charge and includes no
changes and modifications.
You may use this mod without the Author's permission.
The author doesn't bear responsibility for any damage that was caused by this patch.

 ------------------------------------------------------
><><><><><><><><><><><><><><><><><><><><><><><><><><><><
 ------------------------------------------------------

Description:
  This mod is capable of catching the log output, that is sent to the server console.
  It's no standalone mod, but modders can use it to extend their mods with the supplied feature.

Installation:

 Extract the files
	LogCatcher.u
	LogCatcher.dll
	LogCatcher.ini
 into your DeusEx\System folder.

 Open your DeusEx.ini and goto the section [Editor.EditorEngine]
 Find the line, where you added your mod to the EditPackages, insert right about that line
 a new line and add the following to that line: EditPackages=LogCatcher

 Now in your mod create a new class basing on LogCatcher.
 For example:     class MyLogCatcher extends LogCatcher;

 In that new class add the event function LogMesageReceived(String Message,name Type)
 Now this should look like

 //=================================================
 // MyLogCatcher
 //=================================================
 class MyLogCatcher extends LogCatcher;

 event LogMesageReceived(String Message,name Type)
 {
     //place your code here!
 }

 IMPORTANT: Since LogMesageReceived is always called, when some object calls the log function,
            it is NOT recommended to call the log function inside the LogMesageReceived event
            or in any other function, which has a direct or indirect relation to this event.

 Possibly i'm able to fix that recursion problem in later releases, but for now,
 you need to consider this.


The config file:
 The LogCatcher has a config file, which is called LogCatcher.ini
 It contains the property maxRecursiveCalls. That property has the following sense.
 As I explicitly mentioned, it's not recommended to call the log function inside of that event.
 If that property didn't exist and some coder still got the idea to do this, the server would crash due to
 infinite script recursion on the native level.
 So, this property defines, now many recursive calls are allowed, until the execution is aborded
 to avert a server crash.