There are many people who have heard of Quake C. Yet it must run in a virtual machine and not on the target device's cpu. This means the back end of the compiler will product machine code. This does have obvious advantages over a virtual machine; mainly it would run much faster than a virtual machine running that is using byte code. There are many languages in production today, yet there are no languages for Scripting Games that translate into machine code.

Although I am not going to go into the internals of the project, I can give some high lights of the project. This is just projected and can change as the project ages through production. First there needs to be a object file, and this file can stream into scripting objects as you load them. The project is layered and relies on a parallel master class that controls grouping of scripts together. The scripts objects interface inherits several layers of interfaces. This allows certain methods to be called to link and create the script during the loading phase of the Scripts Objects life.

The Core Master Parallel Object is responsible for grouping the scripts, and is layered with a Distributor, which is pulled from the designs of Scrut Game Engine. It consists of a layered system with a God Object for the Scripting Engine that can be easly added to your project. This allows for seamless integration of a Scripting Engine that runs on machine code. Currently the back end of the compiler only produces x64 machine code.