Common Oblivion Engine Framework

Name: Common Oblivion Engine Framework (COEF) Version: v2011. 11. 21 Date: 2011-11-21 Category: Modding Resources Main Author: JRoush Forum Thread: TBA Bug Reports:TBA Documentation for Developers: COEF Wiki Source Repository: Github Description: COEF is an API and utility library for OBSE plugins. It makes plugins simpler and faster to write and more likely to be compatible with other plugins. COEF is not a mod itself, just a resource. It is not an OBSE plugin itself, and OBSE will not load it or even \"see\" it. Only plugins that use COEF will interact with it. Players can uninstall COEF at any time, if they no longer have any plugins that use it. Installation: Download the latest release version from the Files tab, and extract the contents of the archive to your Oblivion\\ folder. To uninstall, find and delete the Oblivion\\Data\\OBSE\\Plugins\\COEF\\ folder. Technical Description (for interested plugin writers): The main feature of COEF is it\'s C++ API for Oblivion and Construction Set. For those familiar with C++ programming, this is basically a set of header (.h) files that define the classes used by the engine. Most plugins simply use the class definitions included with OBSE, so for convenience here are the main ways that COEF differs from the OBSE code:

• []Definition only. No function bodies (implementations), and no classes or methods that do not exist in the Game/CS. []Dynamic Linkage. Projects that use this API link directly to the Game/CS executable as if it were a dll. When a plugin calls an API method, it is directly calling the corresponding code in the Game/CS. []Modularity. Classes are split into their own headers as much as possible, and cross dependencies are minimized. []Readability. Class definitions are formatted as cleanly as possible, so they can be readily browsed. []Completeness. Classes that are fully defined. This means that the name, size, inheritance, and virtual method tables of each class is reproduced exactly, along with as many member functions as possible. Among other things, this means that plugin authors can safely derive from the API classes, use them safely with the dynamic_cast and typeid operators.

This is not meant to imply the OBSE code is bad or poorly written, but it was written mostly for internal use and doesn\'t make a good general-purpose API. It\'s IMPORTANT to note that because COEF and OBSE define many of the same classes, you cannot include headers from both in the same file. This is the main drawback of COEF, especially since there are still classes that haven\'t been