Tales of Maj'Eyal - User contributions [en]

T4 Modules Howto Guide/Player Descriptors

2014-10-12T05:17:39Z

Soadzombi: /* Guide */

=Who do you want to be today?=

==Important variables==

<table>
<tr>
<th>Variable</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Display name of this option in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>short_name</td>
<td>Identifier of this option. name is used if unset.</td>
</tr>
<tr>
<td>type</td>
<td>Defines which birth stage this descriptor belongs to. REQUIRED.</td>
</tr>
<tr>
<td>descriptor_choices</td>
<td>Selects which later descriptors are allowed or disallowed.</td>
</tr>
<tr>
<td>talents_types</td>
<td>Talent types learned at start of game</td>
</tr>
<tr>
<td>talents</td>
<td>List of starting learned talents.</td>
</tr>
<tr>
<td>desc</td>
<td>String that describes the descriptor. Appears in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>body</td>
<td>Initializes available slots. Requires ActorInventory defineInventory() calls in load.lua beforehand(?) which is NOT done in the example module.</td>
</tr>
<tr>
<td>copy</td>
<td>These variables and values will be copied to the resulting player object. See [[NPCs|NPCs]] for values.</td>
</tr>
<tr>
<td>experience</td>
<td>Experience rate. 1 being normal experience gain.</td>
</tr>
<tr>
<td>stats</td>
<td>Initial stats for character. Is added to default stat values.</td>
</tr>
</table>

Important to note is that these variables do not overwrite, they add every time. If your race adds 2 strength, and your class adds 2 strength again you will end up with 4 strength. The exception to this is the copy variable. All elements in this will overwrite previous copy elements.

<h2 id="toc2">Editing the Example Module for your own use</h2>
At the time of writing, ToME has descriptors for world, race, subrace, sex, class and subclass. However, the example module only has a descriptor for role.

If you want to expand this and introduce your own descriptors for races and classes like ToME, or different descriptors entirely, you need to edit the following line in your /class/Game.lua file:

<pre>local birth = Birther.new(self.player, {"base", "role" }, function()</pre>

For comparison, ToME has this line:

<pre>local birth = Birther.new(self.player, {"base", "world", "race", "subrace", "sex", "class", "subclass" }, function()</pre>

Now you just need to create your own descriptors in the /data/birth/descriptors.lua file. If you want to organize your descriptors in multiple files for organization such as ToME does, remember to make a load call with your file path, such as the following ToME uses for its elf descriptor file.

<pre>load("/data/birth/races/elf.lua")</pre>

==Leveling up==
Once you gain enough xp to level, the levelup() method on the player gets called. 
Use this method to include specific special code that runs on a new level up, such as gaining hp and stats.

Note that if you make use of NPC level scaling, its important to define a levelup() on the Actor class as well. Since Player inherits from Actor, you can have the Player class call Actor's levelup() method through:

<pre>mod.class.Actor.levelup(self)</pre>

==Guide==
This guide is roughly based on the [[t4modules t3modules module_guide_part_1|te3 player descriptor guide]].

In the default ToME module, you get to choose from a race, a sub-race, gender, a background, a class, and then a subclass. To the T-Engine, these are all the same thing, called 'player descriptors' (Character descriptors would be more accurate, but that's nitpicking), or PDs for short. PDs are what let you alter the player character in all sorts of different ways. Player descriptors typically stack, so any modifications done to one will usually add with any other modifications, rather than replacing them.

There's no definition or distinction between different types of PDs by the engine. They can all have the same functionality, the only place any consistency is found is by the module author. So, if you only want stats to come from races, and skills from classes, you will have to make sure that only races gain stat bonuses and only classes have skill bonuses. The engine will not discriminate against this for you.

All the examples below will be from the ToME module, so you should be able to see pretty easily where everything came from and can easily modify it and see what happens.

Possibly the most important PD is the one that the player will never see, the base descriptor, found in /data/birth/descriptors.lua. This is the one that is loaded for every character, and provides the universal traits that each character will share. This one has been edited slightly for clarity.

<pre>newBirthDescriptor{
type = "base",
name = "base",
desc = {
},
talents = {},
experience = 1.0,
body = { INVEN = 1000, MAINHAND=1, OFFHAND=1, BODY=1, QUIVER=1 },

copy = {
-- Mages are unheard of at first, nobody but them regenerates mana
mana_rating = 6,
mana_regen = 0,

max_level = 50,
money = 10,
resolvers.equip{ id=true,
{type="lite", subtype="lite", name="brass lantern"},
},
resolvers.inventory{ id=true,
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
},
resolvers.generic(function(e)
e.hotkey[9] = {"inventory", "potion of lesser healing"}
end),
},
}</pre>

This defines out the body and inventory slots for each character, the base experience rate and starting gold and the minimum equipment each character will need to have.

The second PD applied by the ToME module is your race, followed by subrace, found appropriate in /data/birth/races/. Races are where ToME typically grants the character their most unique abilities and major stat adjustments. Below is the PD for elves, and then a subrace of elf.

<pre>newBirthDescriptor{
type = "race",
name = "Elf",
desc = {
"Quendi are Elves, the first children of Eru.",
"The first Elves awoke by Cuiviénen, the Water of Awakening in the far east of Middle-earth, long Ages before the Rising of the Sun or Moon.",
"Unlike Men, the Elves are not subject to death by old age.",
},
descriptor_choices =
{
subrace =
{
Nandor = "allow",
Avari = "allow",
__ALL__ = "never",
},
},
talents = {
-- [ActorTalents.T_IMPROVED_MANA_I]=1,
},
copy = {
type = "humanoid", subtype="elf",
default_wilderness = {39, 17},
starting_zone = "tower-amon-sul",
starting_quest = "start-dunadan",
starting_intro = "elf",
},
experience = 1.05,
}

newBirthDescriptor
{
type = "subrace",
name = "Nandor",
desc = {
"Elves who turned aside from the Great Journey in the early days and settled in th east of the Misty Mountains.",
"Both the Wood-Elves of Mirkwood and the Elves of Lórien are Nandor.",
"They posses the Grace of the Eldar talent which allows them a boost of speed every once in a while.",
},
stats = { str=-2, mag=2, wil=3, cun=1, dex=1, con=0 },
experience = 1.3,
talents = { [ActorTalents.T_NANDOR_SPEED]=1 },
copy = {
life_rating = 9,
},
}</pre>

Go back to [[T4 Modules Howto Guide]]

{{Module Guides}}

T4 Modules Howto Guide/Player Descriptors

2014-10-12T05:02:12Z

Soadzombi: /* Guide */

=Who do you want to be today?=

==Important variables==

<table>
<tr>
<th>Variable</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Display name of this option in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>short_name</td>
<td>Identifier of this option. name is used if unset.</td>
</tr>
<tr>
<td>type</td>
<td>Defines which birth stage this descriptor belongs to. REQUIRED.</td>
</tr>
<tr>
<td>descriptor_choices</td>
<td>Selects which later descriptors are allowed or disallowed.</td>
</tr>
<tr>
<td>talents_types</td>
<td>Talent types learned at start of game</td>
</tr>
<tr>
<td>talents</td>
<td>List of starting learned talents.</td>
</tr>
<tr>
<td>desc</td>
<td>String that describes the descriptor. Appears in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>body</td>
<td>Initializes available slots. Requires ActorInventory defineInventory() calls in load.lua beforehand(?) which is NOT done in the example module.</td>
</tr>
<tr>
<td>copy</td>
<td>These variables and values will be copied to the resulting player object. See [[NPCs|NPCs]] for values.</td>
</tr>
<tr>
<td>experience</td>
<td>Experience rate. 1 being normal experience gain.</td>
</tr>
<tr>
<td>stats</td>
<td>Initial stats for character. Is added to default stat values.</td>
</tr>
</table>

Important to note is that these variables do not overwrite, they add every time. If your race adds 2 strength, and your class adds 2 strength again you will end up with 4 strength. The exception to this is the copy variable. All elements in this will overwrite previous copy elements.

<h2 id="toc2">Editing the Example Module for your own use</h2>
At the time of writing, ToME has descriptors for world, race, subrace, sex, class and subclass. However, the example module only has a descriptor for role.

If you want to expand this and introduce your own descriptors for races and classes like ToME, or different descriptors entirely, you need to edit the following line in your /class/Game.lua file:

<pre>local birth = Birther.new(self.player, {"base", "role" }, function()</pre>

For comparison, ToME has this line:

<pre>local birth = Birther.new(self.player, {"base", "world", "race", "subrace", "sex", "class", "subclass" }, function()</pre>

Now you just need to create your own descriptors in the /data/birth/descriptors.lua file. If you want to organize your descriptors in multiple files for organization such as ToME does, remember to make a load call with your file path, such as the following ToME uses for its elf descriptor file.

<pre>load("/data/birth/races/elf.lua")</pre>

==Leveling up==
Once you gain enough xp to level, the levelup() method on the player gets called. 
Use this method to include specific special code that runs on a new level up, such as gaining hp and stats.

Note that if you make use of NPC level scaling, its important to define a levelup() on the Actor class as well. Since Player inherits from Actor, you can have the Player class call Actor's levelup() method through:

<pre>mod.class.Actor.levelup(self)</pre>

==Guide==
This guide is roughly based on the [[t4modules t3modules module_guide_part_1|te3 player descriptor guide]].

In the default ToME module, you get to choose from a race, a sub-race, gender, a background, a class, and then a subclass. To the T-Engine, these are all the same thing, called 'player descriptors' (Character descriptors would be more accurate, but that's nitpicking), or PDs for short. PDs are what let you alter the player character in all sorts of different ways. Player descriptors typically stack, so any modifications done to one will usually add with any other modifications, rather than replacing them.

There's no definition or distinction between different types of PDs by the engine. They can all have the same functionality, the only place any consistency is found is by the module author. So, if you only want stats to come from races, and skills from classes, you will have to make sure that only races gain stat bonuses and only classes have skill bonuses. The engine will not discriminate against this for you.

All the examples below will be from the ToME module, so you should be able to see pretty easily where everything came from and can easily modify it and see what happens.

Possibly the most important PD is the one that the player will never see, the base descriptor, found in /data/birth/descriptors.lua. This is the one that is loaded for every character, and provides the universal traits that each character will share. This one has been edited slightly for clarity.

<pre>newBirthDescriptor{
type = "base",
name = "base",
desc = {
},
talents = {},
experience = 1.0,
body = { INVEN = 1000, MAINHAND=1, OFFHAND=1, BODY=1, QUIVER=1 },

copy = {
-- Mages are unheard of at first, nobody but them regenerates mana
mana_rating = 6,
mana_regen = 0,

max_level = 50,
money = 10,
resolvers.equip{ id=true,
{type="lite", subtype="lite", name="brass lantern"},
},
resolvers.inventory{ id=true,
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
},
resolvers.generic(function(e)
e.hotkey[9] = {"inventory", "potion of lesser healing"}
end),
},
}</pre>

This defines out the body and inventory slots for each character, the base experience rate and starting gold and the minimum equipment each character will need to have.

The second PD applied by the ToME module is your race, followed by subrace, found appropriate in /data/birth/races/. Races are where ToME typically grants the charcter their most unique abilities and major stat adjustments. Below is the PD for elves, and then a subrace of elf.

<pre>newBirthDescriptor{
type = "race",
name = "Elf",
desc = {
"Quendi are Elves, the first children of Eru.",
"The first Elves awoke by Cuiviénen, the Water of Awakening in the far east of Middle-earth, long Ages before the Rising of the Sun or Moon.",
"Unlike Men, the Elves are not subject to death by old age.",
},
descriptor_choices =
{
subrace =
{
Nandor = "allow",
Avari = "allow",
__ALL__ = "never",
},
},
talents = {
-- [ActorTalents.T_IMPROVED_MANA_I]=1,
},
copy = {
type = "humanoid", subtype="elf",
default_wilderness = {39, 17},
starting_zone = "tower-amon-sul",
starting_quest = "start-dunadan",
starting_intro = "elf",
},
experience = 1.05,
}

newBirthDescriptor
{
type = "subrace",
name = "Nandor",
desc = {
"Elves who turned aside from the Great Journey in the early days and settled in th east of the Misty Mountains.",
"Both the Wood-Elves of Mirkwood and the Elves of Lórien are Nandor.",
"They posses the Grace of the Eldar talent which allows them a boost of speed every once in a while.",
},
stats = { str=-2, mag=2, wil=3, cun=1, dex=1, con=0 },
experience = 1.3,
talents = { [ActorTalents.T_NANDOR_SPEED]=1 },
copy = {
life_rating = 9,
},
}</pre>

Go back to [[T4 Modules Howto Guide]]

{{Module Guides}}

T4 Modules Howto Guide/Directory Structure

2014-10-12T04:38:56Z

Soadzombi:

=An Overview=
==Player Profiles==

When you run T-Engine or a module for the first time a player profile will be created. This contains your settings and keybindings, as well as module specific settings and achievements.

On linux this profile can be found in your home directory.

For Windows the profile folder will be called T-Engine. It will be located in the following locations.

Windows 7 - C:\Users\<username>\T-Engine
Windows XP - C:\Documents and Settings\<username>\T-Engine

Future plans involve moving the profile online, making it easier to compare, rank and show off individual accomplishments to friends. (As of April 2011, this appears to have been implemented.)

==T-Engine Root Directory==

In your T-Engine directory, the one where your executable is located, you will find a game directory. This directory contains all the Lua scripts used by the game and all its modules. The script is interpreted at runtime, so no recompilation is needed after modifying a file.

If you are writing a custom module you should avoid editing any file outside your module directory, since you will not be able to distribute those changes along with your module if you do.

This directory is located in your game folder and contains every module currently available to T-Engine. Every module has its own folder and copying a module directory here is sufficient for it to be detected and appear on the list of available modules when starting a new game.

For all of these guides, the convention to refer to a filepath will use the game's module directory as its root. This is the folder that contains your init.lua file.

Note that the structure described here is only a convention used by ToME, but it is advised that third party module writers follow it for consistency. Few of these paths are hardcoded.

Directories and files not in the example module are underlined. Directories are boldface.

ToME uses many more than listed here, this is only intended to be a rough guide for structuring your own modules.

<table>
<tr>
<th>Directory or file</th>
<th>Purpose</th>
</tr>
<tr>
<td>/</td>
<td>Root Module directory</td>
</tr>
<tr>
<td>/init.lua</td>
<td>Description and basic information about the module.</td>
</tr>
<tr>
<td>/load.lua</td>
<td>This file loads all the basic code and definitions needed to run the module.</td>
</tr>
<tr>
<td>/resolvers.lua</td>
<td>Contains additional custom resolvers.</td>
</tr>
<tr>
<td>/ai/</td>
<td>Directory for custom AI definitions.</td>
</tr>
<tr>
<td>/class/</td>
<td>Directory for module custom class files. These usually extend the generic T-Engine classes of the same name and are used instead of them if they exist.</td>
</tr>
<tr>
<td>/class/Actor.lua</td>
<td>Both the player and all NPCs use this class.</td>
</tr>
<tr>
<td>/class/Game.lua</td>
<td>Handles game initialization, lower level code like keybindings and changing levels and displaying to screen.</td>
</tr>
<tr>
<td>/class/Grid.lua</td>
<td>Defines tooltips for grids and methods that handle what terrain blocks movement.</td>
</tr>
<tr>
<td>/class/NPC.lua</td>
<td>Handles non-player actors.</td>
</tr>
<tr>
<td>/class/Object.lua</td>
<td>Handles all objects in the game.</td>
</tr>
<tr>
<td>/class/Player.lua</td>
<td>Handles all player specific code that isn't generic to all Actors.</td>
</tr>
<tr>
<td>/class/PlayerDisplay.lua</td>
<td>Handles displaying the player's stats.</td>
</tr>
<tr>
<td>/class/Store.lua</td>
<td>Handles stores.</td>
</tr>
<tr>
<td>/class/Trap.lua</td>
<td>Handles traps.</td>
</tr>
<tr>
<td>/class/World.lua</td>
<td>Handles saving and Achievements.</td>
</tr>
<tr>
<td>/class/generator/</td>
<td>Directory for custom generators in zones.</td>
</tr>
<tr>
<td>/class/interface/</td>
<td>Directory for custom interfaces. These are inherited by other classes to help segment and seperate code and improve readability for complex classes.</td>
</tr>
<tr>
<td>/class/interface/Combat.lua</td>
<td>Module custom combat code is defined here.</td>
</tr>
<tr>
<td>/data/</td>
<td>Most of T-Engine is data-driven, not code-driven. This directory contains all the module custom definitions loaded to make your game unique.</td>
</tr>
<tr>
<td>/data/damage_types.lua</td>
<td>Defines the default damage projector and all the different damage types used in the module. (fire, water, acid, etc)</td>
</tr>
<tr>
<td>/data/talents.lua</td>
<td>Default talents file loaded by /init.lua. This file often Load()'s other talent files to improve readability.</td>
</tr>
<tr>
<td>/data/timed_effects.lua</td>
<td>Defines various timed effects available to the module.</td>
</tr>
<tr>
<td>/data/achievements/</td>
<td>Stores module achievements.</td>
</tr>
<tr>
<td>/data/birth/</td>
<td>Birth descriptors folder.</td>
</tr>
<tr>
<td>/data/birth/descriptors.lua</td>
<td>Default birth descriptors file. Often Load()'s other descriptor files to improve readability..</td>
</tr>
<tr>
<td>/data/chats/</td>
<td>Stores NPC chats for mobs that can speak.</td>
</tr>
<tr>
<td>/data/general/</td>
<td>Defines entities available to your module. Note that zones may define their own entities, such as bosses or special items, in the zone directories.</td>
</tr>
<tr>
<td>/data/general/grids/</td>
<td>Defines general grids (terrain).</td>
</tr>
<tr>
<td>/data/general/npcs/</td>
<td>Defines general NPCs.</td>
</tr>
<tr>
<td>/data/general/objects/</td>
<td>Defines general objects.</td>
</tr>
<tr>
<td>/data/general/stores/</td>
<td>Defines general stores.</td>
</tr>
<tr>
<td>/data/general/traps/</td>
<td>Defines general traps.</td>
</tr>
<tr>
<td>/data/gfx/</td>
<td>Special module image or particle assets.</td>
</tr>
<tr>
<td>/data/gfx/particles/</td>
<td>Particle script files.</td>
</tr>
<tr>
<td>/data/maps/</td>
<td>Static map definitions.</td>
</tr>
<tr>
<td>/data/music/</td>
<td>Module music.</td>
</tr>
<tr>
<td>/data/quest/</td>
<td>Module quests.</td>
</tr>
<tr>
<td>/data/rooms/</td>
<td>Special generators for rooms.</td>
</tr>
<tr>
<td>/data/sound/</td>
<td>Sound effects directory.</td>
</tr>
<tr>
<td>/data/talents/</td>
<td>Stores talent description files. These are Load()'ed by the /data/talents.lua file.</td>
</tr>
<tr>
<td>/data/texts/</td>
<td>Special non-quest or monster related texts. Used in ToME for introduction messages and new class unlock texts.</td>
</tr>
<tr>
<td>/data/tilesets/</td>
<td>Data folder for the map generator.</td>
</tr>
<tr>
<td>/data/zones/</td>
<td>Zones folder. Each zone has its own directory.</td>
</tr>
<tr>
<td>/data/ZONE/grids.lua</td>
<td>Zone load file for grids.</td>
</tr>
<tr>
<td>/data/ZONE/npcs.lua</td>
<td>Zone load file for npcs.</td>
</tr>
<tr>
<td>/data/ZONE/objects.lua</td>
<td>Zone load file for objects.</td>
</tr>
<tr>
<td>/data/ZONE/traps.lua</td>
<td>Zone load file for traps.</td>
</tr>
<tr>
<td>/data/ZONE/zone.lua</td>
<td>Zone description file.</td>
</tr>
<tr>
<td>/dialogs/</td>
<td>Contains module specific dialogs.</td>
</tr>
<tr>
<td>/dialogs/DeathDialog.lua</td>
<td>Dialog displayed on death.</td>
</tr>
<tr>
<td>/dialogs/Quit.lua</td>
<td>Dialog displayed when a quit is requested.</td>
</tr>
</table>

==Module team files==
The team files are renamed zip files. However, they have a different directory structure. The data folder remains the same and everything else is put in a mod folder.

Go back to [[T4 Modules Howto Guide]]

{{Module Guides}}

T4 Modules Howto Guide/Getting Started

2014-10-12T04:36:59Z

Soadzombi:

In order to start your own module, you need to create a new directory in the /game/modules/ directory, into which you copy the contents of either /game/modules/example/ or /game/modules/example_realtime/, which will give you bare-bones but working base to work off of.

==init.lua==
The first file you need to customize is the init.lua file. This file has a few things you need to edit to make this module your own:

<table class="wikitable">
<tr>
<th>Setting</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>This is the official name of the module as seen in module selection list.</td>
</tr>
<tr>
<td>long_name</td>
<td>This is the long name of the module that appears is descriptions.</td>
</tr>
<tr>
<td>short_name</td>
<td>This is a short name used internal to the module. Preferred to be lower case and should be the same as the folder name.</td>
</tr>
<tr>
<td>author</td>
<td>Your name or pseudonym and email address.</td>
</tr>
<tr>
<td>homepage</td>
<td>Optional homepage of the module.</td>
</tr>
<tr>
<td>version</td>
<td>Module version. Does not automatically update. Change this between releases to differentiate them.</td>
</tr>
<tr>
<td>engine</td>
<td>Expected engine version.</td>
</tr>
<tr>
<td>description</td>
<td>A description of your module. Can be multiple lines and paragraphs.</td>
</tr>
<tr>
<td>starter</td>
<td>Only change if you know what you are doing. And if you have to ask, you don't.</td>
</tr>
<tr>
<td>show_only_on_cheat</td>
<td>If true, prevents this module from appearing in the mods list normally. This is enabled by default on the example module and should be disabled in your module.</td>
</tr>
<tr>
<td>no_get_name</td>
<td>Prevents the new character name dialog from showing up for your module. Use this if you set the character name yourself in your module.</td>
</tr>
<tr>
<td>no_funfacts</td>
<td>Set to true. This stops ToME4 gameplay stats from appearing on the loading screen.</td>
</tr>
<tr>
<td>loading_wait_ticks</td>
<td>The affects the full speed of the loading bar. Set to around 30 for a small game, or tweak to get a speed that feels right to you.</td>
</tr>
<tr>
<td>allow_userchat</td>
<td>Registers 'space' as a key to talk, joins a channel named "module", and inits the chat system. If the game implements a game.logChat(str, ...) method it'll send chat listens to there.</td>
</tr>
<tr>
<td>background_name</td>
<td>A list of filenames (without the extension) of PNG images under the data/gfx/background directory to use as startup screen backgrounds. The game will load a logo file for each background at data/gfx/background/background_name.png if it is there</td>
</tr>
</table>

<h2 id="toc2">Launching your module using command line parameters</h2>
By now you should be able to start t-engine normally and see your module in the list when you select new game. However, when changing features then quickly wanting to see its effects, this process involves a lot of unneeded clicks and wasted time. For this reason t-engine.exe supports various command line parameters.

<table class="wikitable">
<tr>
<th>Parameter</th>
<th>Effect</th>
</tr>
<tr>
<td>-M<Module></td>
<td>Auto-loads the specified module '''(using the module's short_name)'''.</td>
</tr>
<tr>
<td>-u<name></td>
<td>Uses the specified name for the character.</td>
</tr>
<tr>
<td>-n</td>
<td>Forces a new character, overwriting any old saves with the same name.</td>
</tr>
</table>

To take advantage of this in windows, you need to right-click on t-engine.exe and select 'Create Shortcut'. On the created shortcut right-click again and select properties. In the dialog add the following to the Target field:

<code>.../t-engine.exe -MMyModule -udefault -n</code>

Replacing MyModule with your module name and default with whichever character name you desire. Using this shortcut now will launch your module directly, saving you some time while prototyping.

Go back to [[T4 Modules Howto Guide]].

{{Module Guides}}