The Aleph One wiki has migrated! Please see:
https://github.com/Aleph-One-Marathon/alephone/wiki/Plugins
Beginning with version 0.23, Aleph One supports plugins. These are an easier way to install MML, solo scripts, enhanced HUDs, and themes. To install a plugin, simply copy it into the scenario's Plugins directory. If no Plugins directory exists, create one.
You can create a plugin by creating a folder hierarchy:
and writing a simple Plugin.xml:
<?xml version="1.0"?>
<plugin name="Sample" description="A sample plugin" version="1.0">
<mml file="Sample.mml"/>
</plugin>
All resources will be loaded from the "My Sample Plugin" directory. You can then zip the "My Sample Plugin" folder, and drop it in any Aleph One Plugins folder.
Plugin.xml recognizes the <plugin> tag and its children, the <mml> and <shapes_patch> tags. There can be multiple <mml> and <shapes_patch> tags.</shapes_patch></mml></shapes_patch></mml></plugin>
name="..." - the name of this plugindescription="..." - a short description of the pluginversion="..." - for display purposes onlyminimum_version="..." - the minimum Aleph One date version (e.g. 20091015) required to run this plugin. If the version is not new enough, the plugin will be disabledhud_lua="..." - enhanced HUD Lua script file to runsolo_lua="..." - solo Lua script file to runtheme_dir="..." - directory to load theme fromfile="..." - MML file to loadfile="..." - shapes patch to loadrequires_opengl="true" - shapes patches that require OpenGL will not be loaded when the software renderer is active