MAT Automaton - Script Development Terms

MAT Automaton
Script Development Terms
Effective: 07/06/2011

I have decided to clear things up regarding derivative works of MAT Automaton. I have no problem with people releasing derivative works of my software, provided they follow the terms I will detail in this thread.

Before I discuss the terms for script developers I will start by addressing a common misconception. MAT Automaton consists of two independent components.

The first component is the core, the MAT Automaton framework itself (MAT Automaton.exe). The majority of the code and development time was spent developing the core. The core includes, but is not limited to, a console, a menu, a runtime linker for Unreal Engine imports, the Python interpreter, Pyreal (Python Unreal Engine bindings), GUI bindings, offset engine bindings, and a circumvention system for anticheat.

The second component is everything you see in the two scripts directories: \MAT Automaton\Scripts and %AppData%\MAT Automaton\Scripts. The scripts while containing all of the aiming and rendering code is actually the minority of the work in the project.

Licensing Terms

• All derivative works MAY NOT include the core executable MAT Automaton.exe. You must instruct users to download and install it from the official release thread (e.g. http://www.mpgh.net/forum/324-missio...06-2011-a.html)
• You must include MAT Automaton in the title of any cheat that relies on the MAT Automaton framework.
• You must credit the author of MAT Automaton, dB, in a clear and legible fashion in any cheat that relies on the MAT Automaton framework.
• If your scripts are based on the provided scripts you must include this fact in your credits.
• Without warning the terms may be changed and you will be retroactively subject to the changes.