DikuMUD Wiki - User contributions [en]

Manual:DIL Manual/reset race()

2025-12-04T22:39:51Z

Nove: XML import

'''Function:''' reset_race( u : unitptr ) ;

 '''u'''
 player your resetting

Reset a characters race, weight, height, age, lifespan, and costs for training.
As if you first log on the character. Great for reroll along with 'reset_level' and 'reset_vlevel'.
'''Example: '''reset_race (u);
'''See Also'''

[[#bpresetlevel|reset a players level]] and
[[#bpresetvlevel|reset a players virtual level]]

---~---~---~---~---~---~---~---~---


'''Function:''' reset_race( u : unitptr ) ;

 '''u'''
 player your resetting

Reset a characters race, weight, height, age, lifespan, and costs for training.
As if you first log on the character. Great for reroll along with 'reset_level' and 'reset_vlevel'.
'''Example: '''reset_race (u);
'''See Also'''

[[#bpresetlevel|reset a players level]] and
[[#bpresetvlevel|reset a players virtual level]]

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/unequip()

2025-12-04T22:39:48Z

Nove: XML import

unequip ( u : unitptr )
u : Unit to unequip.
result: Unequipes unit presumed to be in equipment of PC/NPC.

unequip ( u : unitptr )
u : Unit to unequip.
result: Unequipes unit presumed to be in equipment of PC/NPC.

Manual:DIL Manual/visible()

2025-12-04T22:39:37Z

Nove: XML import

integer visible(u1 : unitptr, u2 : unitptr)
u1: The character who is looking at u2
u2: The unit which the character u1 is trying to see.
return: TRUE if u1 can see u2, FALSE otherwise.
Example: if (visible(self, victim)) ...

---~---~---~---~---~---~---~---~---

integer visible(u1 : unitptr, u2 : unitptr)
u1: The character who is looking at u2
u2: The unit which the character u1 is trying to see.
return: TRUE if u1 can see u2, FALSE otherwise.
Example: if (visible(self, victim)) ...

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/beginedit()

2025-12-04T22:39:33Z

Nove: XML import

'''Function:''' beginedit ( u : unitptr);

 '''u'''
 the PC unit doing the editing
 '''return'''
 When done editing it returns SFB_EDIT and activator is set to PC

The 'BEGINEDIT' function sets a PC into editing mode. while in edit mode
the PC field 'editing is set to true. Once the PC is done editing a 'SFB_EDIT'
message is sent to the unit editing to continue on with the DIL.
If for some reason the PC needs to break
out of the editor before it is done editing then the Dil needs to call
the 'killedit' function
[[#sect-beginedit|interrupt editing before done]]

'''example:'''

---~---~---~---~---~---~---~---~---

dilbegin edextra ();
var
temp:string;
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL is an example of how you could make a command to set the
general extra which is the characters description when you do 'look player'

---~---~---~---~---~---~---~---~---


'''Function:''' beginedit ( u : unitptr);

 '''u'''
 the PC unit doing the editing
 '''return'''
 When done editing it returns SFB_EDIT and activator is set to PC

The 'BEGINEDIT' function sets a PC into editing mode. while in edit mode
the PC field 'editing is set to true. Once the PC is done editing a 'SFB_EDIT'
message is sent to the unit editing to continue on with the DIL.
If for some reason the PC needs to break
out of the editor before it is done editing then the Dil needs to call
the 'killedit' function
[[#sect-beginedit|interrupt editing before done]]

'''example:'''

---~---~---~---~---~---~---~---~---

dilbegin edextra ();
var
temp:string;
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL is an example of how you could make a command to set the
general extra which is the characters description when you do 'look player'

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/purse()

2025-12-04T22:39:29Z

Nove: XML import

integer purse(u : unitptr, coinage : integer)
u : The unit to check
coinage: The money type (e.g. gold, silver), one of IRON_PIECE, etc.
Returns: The number of such units found.
Example: if (purse(self, PLATINUM_PIECE) > 10)
exec("say I am loaded with platinum!", self);

---~---~---~---~---~---~---~---~---

integer purse(u : unitptr, coinage : integer)
u : The unit to check
coinage: The money type (e.g. gold, silver), one of IRON_PIECE, etc.
Returns: The number of such units found.
Example: if (purse(self, PLATINUM_PIECE) > 10)
exec("say I am loaded with platinum!", self);

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/findrndunit()

2025-12-04T22:39:28Z

Nove: XML import

unitptr findrndunit( u : unitptr, sv : integer, uf : integer)
Returns: A pointer to a random unit, or null
u : The unit pointer which the search is relative to.
sv : The search-location, a value (not bit vector) of FIND_UNIT_XXX
uf : Bit vector. The unit flags which can match of UNIT_ST_XXX

Example: u := findrndunit(self, FIND_UNIT_ZONE, UNIT_ST_PC|UNIT_ST_NPC);

This routine returns a random unit. Notice how the 'uf' lets you
specify exactly what unit types to look for. The 'sv' is not a
bit vector, although FIND_UNIT_XXX is usually used as such. If
you need to search multiple environments, then call the routine
once for each.

Using FIND_UNIT_PAY or FIND_UNIT_NOPAY in this function will
pick a random player which in addition to being in the search
environment also is registered as valid payer (or not). Asking
for a room would yield a random room registered to be accessible
for paying players only (or not). Asking for objects would
return no unit (null).

unitptr findrndunit( u : unitptr, sv : integer, uf : integer)
Returns: A pointer to a random unit, or null
u : The unit pointer which the search is relative to.
sv : The search-location, a value (not bit vector) of FIND_UNIT_XXX
uf : Bit vector. The unit flags which can match of UNIT_ST_XXX

Example: u := findrndunit(self, FIND_UNIT_ZONE, UNIT_ST_PC|UNIT_ST_NPC);

This routine returns a random unit. Notice how the 'uf' lets you
specify exactly what unit types to look for. The 'sv' is not a
bit vector, although FIND_UNIT_XXX is usually used as such. If
you need to search multiple environments, then call the routine
once for each.

Using FIND_UNIT_PAY or FIND_UNIT_NOPAY in this function will
pick a random player which in addition to being in the search
environment also is registered as valid payer (or not). Asking
for a room would yield a random room registered to be accessible
for paying players only (or not). Asking for objects would
return no unit (null).

Manual:DIL Manual/gamestate()

2025-12-04T22:39:25Z

Nove: XML import

'''Function: ''' gamestate( u : unitptr, gs : integer ); 
Change the gamestate of a unitptr, uses the GS_ defines from the
'''vme.h'''. This is used on the log on menu of the VME 2.0 release. Which is
shown here as an example but it can also be used in a command. When used it
removes the char from playing so be aware that players could use this to hide
if you run a player killing style mud.
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin informer();
var
tgt : unitptr;
code
dilend

dilbegin aware on_connect();
external
informer();
login_modify(tgt : unitptr);

var
wizlvl : integer;
i:integer;
err : integer;
motd : string;
welcome : string;
goodbye : string;
code
dilend

---~---~---~---~---~---~---~---~---


Look in '''vme.h''' for the possible values you can send to the menu
function.

---~---~---~---~---~---~---~---~---


'''Function: ''' gamestate( u : unitptr, gs : integer ); 
Change the gamestate of a unitptr, uses the GS_ defines from the
'''vme.h'''. This is used on the log on menu of the VME 2.0 release. Which is
shown here as an example but it can also be used in a command. When used it
removes the char from playing so be aware that players could use this to hide
if you run a player killing style mud.
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin informer();
var
tgt : unitptr;
code
dilend

dilbegin aware on_connect();
external
informer();
login_modify(tgt : unitptr);

var
wizlvl : integer;
i:integer;
err : integer;
motd : string;
welcome : string;
goodbye : string;
code
dilend

---~---~---~---~---~---~---~---~---


Look in '''vme.h''' for the possible values you can send to the menu
function.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/clear()

2025-12-04T22:39:18Z

Nove: XML import

clear( i : integer )

Clears the interrupt number "i". If i is invalid, this will either
clear an wrong interrupt or do nothing.

---~---~---~---~---~---~---~---~---

clear( i : integer )

Clears the interrupt number "i". If i is invalid, this will either
clear an wrong interrupt or do nothing.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/findroom()

2025-12-04T22:39:01Z

Nove: XML import

unitptr findroom ( s : string )
s : Symbolic name of room.
return: A pointer to the room, or null
Example: findroom("inn@udgaard")

---~---~---~---~---~---~---~---~---

unitptr findroom ( s : string )
s : Symbolic name of room.
return: A pointer to the room, or null
Example: findroom("inn@udgaard")

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/realtime

2025-12-04T22:38:57Z

Nove: XML import

'realtime'
This variable returns the number of seconds passed since 1970 something.
For C buffs this is equivalent to time(NULL).

---~---~---~---~---~---~---~---~---

'realtime'
This variable returns the number of seconds passed since 1970 something.
For C buffs this is equivalent to time(NULL).

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/continue

2025-12-04T22:38:57Z

Nove: XML import

'''continue:'''
The continue statement makes you jump to the top
of any loop you're currently in.

'''Example:'''

<nowiki>

dilbegin foo();
code
dilend</nowiki>

---~---~---~---~---~---~---~---~---

'''continue:'''
The continue statement makes you jump to the top
of any loop you're currently in.

'''Example:'''

<nowiki>

dilbegin foo();
code
dilend</nowiki>

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/getcolor()

2025-12-04T22:38:53Z

Nove: XML import

'''Function: ''' string getcolor (ch : unitptr, ks : string) ;

 '''ch'''
 character you are deleting the color from
 '''ks'''
 key string for the color
 '''returns'''
 returns the color in a string

This function returns what color a player has for a key in the players list.
'''Function: '''string := getcolor(pc, "clan_who");


'''Function: ''' string getcolor (ch : unitptr, ks : string) ;

 '''ch'''
 character you are deleting the color from
 '''ks'''
 key string for the color
 '''returns'''
 returns the color in a string

This function returns what color a player has for a key in the players list.
'''Function: '''string := getcolor(pc, "clan_who");

Manual:DIL Manual/wait()

2025-12-04T22:38:49Z

Nove: XML import

wait ( i : integer , dilexp )
i : Message class to accept, see SFB_* in values.h and/or vme.h
dilexp : Expression that has to be TRUE or not null to accept message.
result: Waits for a command, matching the flagset, and satisfies the
expression. When using the 'wait()' command, the first argument
is an integer, that tells what classes of messages to wait for.
Each message class is represented by a bit named as described in
the chapter on messages.
'''Example:'''

wait (SFB_TICK|SFB_MSG, TRUE)
/* Will accept a message, either from another DIL program or a
timer message. As the second argument is always TRUE, any
such message will reactivate the DIL program.
*/

'''Example:'''

wait (SFB_CMD, command("transmutate"))
/* waits for an command entered named 'transmutate'.
Activates the DIL program, that then can block the command, or
let it pass (and then let the game produce the normal error
message for unknown commands).
*/

wait ( i : integer , dilexp )
i : Message class to accept, see SFB_* in values.h and/or vme.h
dilexp : Expression that has to be TRUE or not null to accept message.
result: Waits for a command, matching the flagset, and satisfies the
expression. When using the 'wait()' command, the first argument
is an integer, that tells what classes of messages to wait for.
Each message class is represented by a bit named as described in
the chapter on messages.
'''Example:'''

wait (SFB_TICK|SFB_MSG, TRUE)
/* Will accept a message, either from another DIL program or a
timer message. As the second argument is always TRUE, any
such message will reactivate the DIL program.
*/

'''Example:'''

wait (SFB_CMD, command("transmutate"))
/* waits for an command entered named 'transmutate'.
Activates the DIL program, that then can block the command, or
let it pass (and then let the game produce the normal error
message for unknown commands).
*/

Manual:DIL Manual/filesize()

2025-12-04T22:38:36Z

Nove: XML import

'''Function:''' integer filesize ( filename :string);

 '''file'''
 The file name you want to check
 '''return'''
 a file size in bites 0 if no file

This function does exactly what it says it does it checks a files size.

'''Example DIL:'''

---~---~---~---~---~---~---~---~---

dilbegin notebook ();
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL example shows how you could use the 'filesize' instruction to
check the size of a player stored notebook.

---~---~---~---~---~---~---~---~---


'''Function:''' integer filesize ( filename :string);

 '''file'''
 The file name you want to check
 '''return'''
 a file size in bites 0 if no file

This function does exactly what it says it does it checks a files size.

'''Example DIL:'''

---~---~---~---~---~---~---~---~---

dilbegin notebook ();
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL example shows how you could use the 'filesize' instruction to
check the size of a player stored notebook.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/target

2025-12-04T22:38:30Z

Nove: XML import

'target'
This variable is a unit pointer to the unit which is the target of the
current operation. For 'done' messages this could for example be the
destination in a give command.
See description of messages for more information.

---~---~---~---~---~---~---~---~---

'target'
This variable is a unit pointer to the unit which is the target of the
current operation. For 'done' messages this could for example be the
destination in a give command.
See description of messages for more information.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/isplayer()

2025-12-04T22:38:28Z

Nove: XML import

'''Function:''' integer isplayer( pcname : string ) ;

 '''pcname'''
 the name of the player being checked
 '''Return'''
 Returns an integer TRUE if pcname is a player FALSE if not

This function is used to find out if a string you pass to it is a player or not.
This can be used and is used to find out if a player is truly a player that an
Administrator is deleting with out having that player on line.
'''Example:'''

---~---~---~---~---~---~---~---~---

if (not isplayer(arg))
---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---


'''Function:''' integer isplayer( pcname : string ) ;

 '''pcname'''
 the name of the player being checked
 '''Return'''
 Returns an integer TRUE if pcname is a player FALSE if not

This function is used to find out if a string you pass to it is a player or not.
This can be used and is used to find out if a player is truly a player that an
Administrator is deleting with out having that player on line.
'''Example:'''

---~---~---~---~---~---~---~---~---

if (not isplayer(arg))
---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---

Manual:DIL Manual/setweight()

2025-12-04T22:38:26Z

Nove: XML import

setweight( u : unitptr, i : integer )
u : the unit on which you wish to alter the weight.
i : the new weight

This is needed on for example drink-containers. I.e. if you wish to
remove or add some liquid, you must also adjust the weight of the
container, or you will mess up things.

---~---~---~---~---~---~---~---~---

setweight( u : unitptr, i : integer )
u : the unit on which you wish to alter the weight.
i : the new weight

This is needed on for example drink-containers. I.e. if you wish to
remove or add some liquid, you must also adjust the weight of the
container, or you will mess up things.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/zoneptr

2025-12-04T22:38:17Z

Nove: XML import

'''Type: '''zoneptr
'''Zone Pointer Fields'''

 '''next'''
 unitptr - pointer to next zoneptr
 '''previous'''
 unitptr - pointer to previous zone
 '''creators'''
 stringlist - list of creators
 '''name'''
 string - zone name (%zone)
 '''title'''
 string - zone title (title "")
 '''rooms'''
 unitptr - pointer to the base room
 '''objs'''
 unitptr - pointer to the base objects of the zone
 '''npcs'''
 unitptr - pointer to base NPCs of the zone
 '''resetmode'''
 integer- reset mode of zone in 'values.h'
 '''resettime'''
 integer - the reset time of the zone
 '''access'''
 integer - the access level of the zone
 '''loadlevel'''
 integer - the loadlevel of the zone
 '''payonly'''
 integer - the paystatus of the zone
 '''roomcount'''
 integer - the number of rooms in a zone
 '''objcount'''
 integer - the numbner of objects in a zone
 '''npccount'''
 integer - the number of npcs/mobiles in a zone
 '''fname'''
 string - the filename of a zone
 '''notes'''
 string - the Zone Notes
 '''help'''
 string - the Zone Help

The 'zoneptr' works like a unitptr. To get the first zoneptr in the global
list of zones you use 'zhead'.
'''Example: '''zoneptr := zhead();
'''Zone list command'''

---~---~---~---~---~---~---~---~---

dilbegin zonelist (arg:string);
var
z:zoneptr;
buf:string;
code
dilend

---~---~---~---~---~---~---~---~---




'''Type: '''zoneptr
'''Zone Pointer Fields'''

 '''next'''
 unitptr - pointer to next zoneptr
 '''previous'''
 unitptr - pointer to previous zone
 '''creators'''
 stringlist - list of creators
 '''name'''
 string - zone name (%zone)
 '''title'''
 string - zone title (title "")
 '''rooms'''
 unitptr - pointer to the base room
 '''objs'''
 unitptr - pointer to the base objects of the zone
 '''npcs'''
 unitptr - pointer to base NPCs of the zone
 '''resetmode'''
 integer- reset mode of zone in 'values.h'
 '''resettime'''
 integer - the reset time of the zone
 '''access'''
 integer - the access level of the zone
 '''loadlevel'''
 integer - the loadlevel of the zone
 '''payonly'''
 integer - the paystatus of the zone
 '''roomcount'''
 integer - the number of rooms in a zone
 '''objcount'''
 integer - the numbner of objects in a zone
 '''npccount'''
 integer - the number of npcs/mobiles in a zone
 '''fname'''
 string - the filename of a zone
 '''notes'''
 string - the Zone Notes
 '''help'''
 string - the Zone Help

The 'zoneptr' works like a unitptr. To get the first zoneptr in the global
list of zones you use 'zhead'.
'''Example: '''zoneptr := zhead();
'''Zone list command'''

---~---~---~---~---~---~---~---~---

dilbegin zonelist (arg:string);
var
z:zoneptr;
buf:string;
code
dilend

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/fits()

2025-12-04T22:38:17Z

Nove: XML import

string fits( char : unitptr, obj : unitptr, pos : integer );
char: Character which we want to test if obj can be fitted upon
obj: The object we want to see if fits char.
pos: -1 or WEAR_XXX
Returns: Empty string if ok, or a textual description of the size problem.

Fits tests if "obj" can be worn by "char" in position "pos". If
pos is -1, then fits automatically figures out the default worn
position for "obj".

Example:

s := fits(self, obj, -1);
if (s != "")
exec("say Don't buy it, its "+s, self);

string fits( char : unitptr, obj : unitptr, pos : integer );
char: Character which we want to test if obj can be fitted upon
obj: The object we want to see if fits char.
pos: -1 or WEAR_XXX
Returns: Empty string if ok, or a textual description of the size problem.

Fits tests if "obj" can be worn by "char" in position "pos". If
pos is -1, then fits automatically figures out the default worn
position for "obj".

Example:

s := fits(self, obj, -1);
if (s != "")
exec("say Don't buy it, its "+s, self);

Manual:DIL Manual/goto

2025-12-04T22:38:16Z

Nove: XML import

'''goto:'''
The goto statement lets you jump about in the code.
Labels in your DIL programs, for 'goto' or interrupts
are defined within ':'. For an example, see the program below.

'''Example:'''

<nowiki>

dilbegin foo();
code
dilend</nowiki>

---~---~---~---~---~---~---~---~---

'''goto:'''
The goto statement lets you jump about in the code.
Labels in your DIL programs, for 'goto' or interrupts
are defined within ':'. For an example, see the program below.

'''Example:'''

<nowiki>

dilbegin foo();
code
dilend</nowiki>

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/delcolor()

2025-12-04T22:38:04Z

Nove: XML import

'''Function: '''delcolor (ch : unitptr, ks : string) ;

 '''ch'''
 character you are deleting the color from
 '''ks'''
 key string for the color

This function is used to delete any colors from a players personal color list.
'''Function: '''delcolor(pc, "clan_who");


'''Function: '''delcolor (ch : unitptr, ks : string) ;

 '''ch'''
 character you are deleting the color from
 '''ks'''
 key string for the color

This function is used to delete any colors from a players personal color list.
'''Function: '''delcolor(pc, "clan_who");

Manual:DIL Manual/pagestring()

2025-12-04T22:38:01Z

Nove: XML import

pathto(buff : string, u : unitptr )
buff : The string that is to be paged to the player.
u : The unitptr the buff is to be paged for.
returns: nothing
example:
pagestring (buff,self);
would format the buff string to the player so the buff text doesn't scroll
off the screen until after the player presses enter.

pathto(buff : string, u : unitptr )
buff : The string that is to be paged to the player.
u : The unitptr the buff is to be paged for.
returns: nothing
example:
pagestring (buff,self);
would format the buff string to the player so the buff text doesn't scroll
off the screen until after the player presses enter.

Manual:DIL Manual/extraptr

2025-12-04T22:37:57Z

Nove: XML import

'''The extraptr has the following fields:'''

extraptr:
'names' :stringlist (RW)
names is a list of strings of names, that the extra description matches on.
'descr' :string (RW)
descr is the contents of the extra description.
'next' :extraptr (RO)
next is the next extra description in a list.
'vals' :intlist (RW)
vals is a list of integer values attached to this extra.

---~---~---~---~---~---~---~---~---

The unitptr is the key structure in the MUD, containing any kind of the
following subtypes:

object : a normal object, a sword, a vail, etc.
room : a room, location or the like.
pc : a playing character.
npc : a non playing character (mobile, monster, etc)

---~---~---~---~---~---~---~---~---

'''Extraptr:'''

Extra descriptions, quests structures, etc can be searched and manipulated
using variables of this type. There is no way to declare static structures of
this type in DIL programs. Lists of extra descriptions are easily searched with
the 'in' operator (See below). Extraptr variables are 'volatile', and thus
cleared whenever there is a possibility that they are rendered unusable.

'''The extraptr has the following fields:'''

extraptr:
'names' :stringlist (RW)
names is a list of strings of names, that the extra description matches on.
'descr' :string (RW)
descr is the contents of the extra description.
'next' :extraptr (RO)
next is the next extra description in a list.
'vals' :intlist (RW)
vals is a list of integer values attached to this extra.

---~---~---~---~---~---~---~---~---

The unitptr is the key structure in the MUD, containing any kind of the
following subtypes:

object : a normal object, a sword, a vail, etc.
room : a room, location or the like.
pc : a playing character.
npc : a non playing character (mobile, monster, etc)

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/mud(day,month,..)

2025-12-04T22:37:56Z

Nove: XML import

'mudday'
'mudhour'
'mudmonth'
'mudyear'
These variables lets your program keep track of the time in the mud.
They all have integer types.

'mudday'
'mudhour'
'mudmonth'
'mudyear'
These variables lets your program keep track of the time in the mud.
They all have integer types.

Manual:DIL Manual/reset level()

2025-12-04T22:37:49Z

Nove: XML import

'''Function:''' reset_level( u : unitptr ) ;

 '''u'''
 player your resetting

This function simply resets a players level. Can be used in functions
like reroll where you set the players back to the way he first logged on.
'''Example: '''reset_level (u);
'''See Also'''

[[#bpresetvlevel|reset a players virtual level]] and
[[#bpresetrace|reset a players race information]]


'''Function:''' reset_level( u : unitptr ) ;

 '''u'''
 player your resetting

This function simply resets a players level. Can be used in functions
like reroll where you set the players back to the way he first logged on.
'''Example: '''reset_level (u);
'''See Also'''

[[#bpresetvlevel|reset a players virtual level]] and
[[#bpresetrace|reset a players race information]]

Manual:DIL Manual/UNIT ST NPC

2025-12-04T22:37:48Z

Nove: XML import

'''if the type is UNIT_ST_NPC '''

'defaultpos' :integer (RW)
The default position of an NPC, see POSITION_* in values.h and/or vme.h
'natural_armour' :integer (RW)
The natural armour of the NPC when naked.
'npcflags' :integer (RW)
Some small options for NPC's see NPC_* in values.h and/or vme.h
'switched' :unitptr (RW)
Character that is switched into this NPC.

'''if the type is UNIT_ST_NPC '''

'defaultpos' :integer (RW)
The default position of an NPC, see POSITION_* in values.h and/or vme.h
'natural_armour' :integer (RW)
The natural armour of the NPC when naked.
'npcflags' :integer (RW)
Some small options for NPC's see NPC_* in values.h and/or vme.h
'switched' :unitptr (RW)
Character that is switched into this NPC.

Manual:DIL Manual/transfermoney()

2025-12-04T22:37:44Z

Nove: XML import

integer transfermoney( f : unitptr, t : unitptr, amount : integer)
f : The char the money is taken from
t : The char the money is given to
amount : How much money.
Returns: TRUE is money was transferred, FALSE if could not afford.

If 'f' is null and 't' isn't, then money is created and given to 't'.
If 'f' isn't null but 't' is, then money is removed from 'f'.

---~---~---~---~---~---~---~---~---

integer transfermoney( f : unitptr, t : unitptr, amount : integer)
f : The char the money is taken from
t : The char the money is given to
amount : How much money.
Returns: TRUE is money was transferred, FALSE if could not afford.

If 'f' is null and 't' isn't, then money is created and given to 't'.
If 'f' isn't null but 't' is, then money is removed from 'f'.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/block

2025-12-04T22:37:40Z

Nove: XML import

block
result: Blocks any command issued by a player or mobile. Blocking a
command prevents the command from being parsed by the
interpreter. This is ideal if you need to make a routine
which intercepts a command, reacts on it in a special way,
and does not need the standard way of reacting.

---~---~---~---~---~---~---~---~---

block
result: Blocks any command issued by a player or mobile. Blocking a
command prevents the command from being parsed by the
interpreter. This is ideal if you need to make a routine
which intercepts a command, reacts on it in a special way,
and does not need the standard way of reacting.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/unitdir()

2025-12-04T22:37:39Z

Nove: XML import

'''Function:''' stringlist unitdir( match : string ) ;

 '''match'''
 The wild card file you want to match or '*' for all.
 '''return'''
 a Stringlist with all the filenames that match the 'match' argument.

The 'match' argument uses the same wild cards as the Linux 'ls' command
so the following will work.

 '''&ast;'''
 Match any character or group of characters
 '''&quest;'''
 Match one of any character
 '''[...]'''
 Match one of a set of characters

'''Example:'''

---~---~---~---~---~---~---~---~---

"corpse*" matches: corpse.10938 corpse.whistler corpseofwhistler ...
"corpse?" matches corpse1 corpses corpse5 ...
"[abc]*" matches ability about cost back ...
"[a-z]*" about zoo man father ...
"start[nm]end" matches startnend startmend

---~---~---~---~---~---~---~---~---


'''Example DIL:'''

---~---~---~---~---~---~---~---~---

dilbegin aware reload_corpse();
var
corpselist:stringlist;
u:unitptr;
ln:integer;
i:integer;
x:extraptr;
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL example is the DIL used in restoring corpses to the game in
case of a crash. For more information you can see how the death DIL'S work
by reading through the file death.zon in the vme2.0/zone.
directory.

---~---~---~---~---~---~---~---~---


'''Function:''' stringlist unitdir( match : string ) ;

 '''match'''
 The wild card file you want to match or '*' for all.
 '''return'''
 a Stringlist with all the filenames that match the 'match' argument.

The 'match' argument uses the same wild cards as the Linux 'ls' command
so the following will work.

 '''&ast;'''
 Match any character or group of characters
 '''&quest;'''
 Match one of any character
 '''[...]'''
 Match one of a set of characters

'''Example:'''

---~---~---~---~---~---~---~---~---

"corpse*" matches: corpse.10938 corpse.whistler corpseofwhistler ...
"corpse?" matches corpse1 corpses corpse5 ...
"[abc]*" matches ability about cost back ...
"[a-z]*" about zoo man father ...
"start[nm]end" matches startnend startmend

---~---~---~---~---~---~---~---~---


'''Example DIL:'''

---~---~---~---~---~---~---~---~---

dilbegin aware reload_corpse();
var
corpselist:stringlist;
u:unitptr;
ln:integer;
i:integer;
x:extraptr;
code
dilend

---~---~---~---~---~---~---~---~---


The previous DIL example is the DIL used in restoring corpses to the game in
case of a crash. For more information you can see how the death DIL'S work
by reading through the file death.zon in the vme2.0/zone.
directory.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/stop fighting()

2025-12-04T22:37:36Z

Nove: XML import

'''Function:''' stop_fighting( ch: unitptr, vict : unitptr ) ;

 '''ch'''
 unitptr - person you are stoping the fighting for
 '''vict'''
 unitptr - person you are removing from the fighting or null for everyone

This function can be used to cancel combat in a room or with two people.
The following example copied to a player will stop any fight the player is in.
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin stop_combat();
code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---


'''Function:''' stop_fighting( ch: unitptr, vict : unitptr ) ;

 '''ch'''
 unitptr - person you are stoping the fighting for
 '''vict'''
 unitptr - person you are removing from the fighting or null for everyone

This function can be used to cancel combat in a room or with two people.
The following example copied to a player will stop any fight the player is in.
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin stop_combat();
code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---

Manual:DIL Manual/excmdstr case

2025-12-04T22:37:32Z

Nove: XML import

'excmdstr_case'
This variable is a string which contains the "first string" which was entered
by a player. The result of adding:

excmdstr_case + " " + argument

is the entire string as entered by the player.
The 'excmdstr' is not changed in anyway from how a player types it.
If a player types 'S' then the 'excmdstr_case' will have 'S' in it.

---~---~---~---~---~---~---~---~---

'excmdstr_case'
This variable is a string which contains the "first string" which was entered
by a player. The result of adding:

excmdstr_case + " " + argument

is the entire string as entered by the player.
The 'excmdstr' is not changed in anyway from how a player types it.
If a player types 'S' then the 'excmdstr_case' will have 'S' in it.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/set fighting()

2025-12-04T22:37:28Z

Nove: XML import

set_fighting( u : unitptr, t : unitptr )
u : the unit on which attacks.
t : the unit being attacked.

This is used to set two characters fighting. If the attacker is
fighting already, the target will simply be inserted into the
opponent list and perhaps killed a little later.

---~---~---~---~---~---~---~---~---

set_fighting( u : unitptr, t : unitptr )
u : the unit on which attacks.
t : the unit being attacked.

This is used to set two characters fighting. If the attacker is
fighting already, the target will simply be inserted into the
opponent list and perhaps killed a little later.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/cancarry()

2025-12-04T22:37:26Z

Nove: XML import

integer can_carry(ch : unitptr, u : unitptr, n : integer)
ch : The character to check
u : The unit to check if he can carry.
n : How many copies of that unit.

Returns: 0 if 'ch' can carry 'n' times 'u'.
1 if 'n' items are too many (his hands are full)
2 if 'n' times 'u' are too heavy

Example:

i := can_carry(activator, item, 1);

if (i == 1)
exec("say Your hands are full!", self);
else if (i == 2)
exec("say You cant carry that much weight.", self);
else
exec("give "+item.name+" to "+activator.name, self);

---~---~---~---~---~---~---~---~---


integer can_carry(ch : unitptr, u : unitptr, n : integer)
ch : The character to check
u : The unit to check if he can carry.
n : How many copies of that unit.

Returns: 0 if 'ch' can carry 'n' times 'u'.
1 if 'n' items are too many (his hands are full)
2 if 'n' times 'u' are too heavy

Example:

i := can_carry(activator, item, 1);

if (i == 1)
exec("say Your hands are full!", self);
else if (i == 2)
exec("say You cant carry that much weight.", self);
else
exec("give "+item.name+" to "+activator.name, self);

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/follow()

2025-12-04T22:37:25Z

Nove: XML import

follow( f : unitptr, m : unitptr )
f : The character to follow
m : The character to be followed

Unconditionally makes 'f' follow 'm', even if 'f' is mortally
wounded, sleeping, fighting or whatever.

follow( f : unitptr, m : unitptr )
f : The character to follow
m : The character to be followed

Unconditionally makes 'f' follow 'm', even if 'f' is mortally
wounded, sleeping, fighting or whatever.

Manual:DIL Manual/atoi()

2025-12-04T22:37:16Z

Nove: XML import

integer atoi ( s : string )
s : A string with a number.
return: The number in the string.
Example: i := atoi("42");

integer atoi ( s : string )
s : A string with a number.
return: The number in the string.
Example: i := atoi("42");

Manual:DIL Manual/weapon name()

2025-12-04T22:37:15Z

Nove: XML import

'''Function:''' string weapon_name( i : integer ) ;

 '''i'''
 Weapon to get the name of ass defined in 'values.h' and 'weapons.def'
 '''returns'''
 The name of the weapon that corresponds with the integer value

'''example:'''

---~---~---~---~---~---~---~---~---

myweap:=weapon_name(5);

---~---~---~---~---~---~---~---~---




'''Function:''' string weapon_name( i : integer ) ;

 '''i'''
 Weapon to get the name of ass defined in 'values.h' and 'weapons.def'
 '''returns'''
 The name of the weapon that corresponds with the integer value

'''example:'''

---~---~---~---~---~---~---~---~---

myweap:=weapon_name(5);

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/link()

2025-12-04T22:37:14Z

Nove: XML import

link ( u : unitptr, t : unitptr )
u : Unit to link.
t : Unit to link into.
result: Link a unit into another unit hierarchy. (Automatically
unequipps if equipped).

link ( u : unitptr, t : unitptr )
u : Unit to link.
t : Unit to link into.
result: Link a unit into another unit hierarchy. (Automatically
unequipps if equipped).

Manual:DIL Manual/argument

2025-12-04T22:37:08Z

Nove: XML import

'argument'
This variable is a string, showing the argument of a command resulting
in the activation of the DIL program. See SFB_CMD for example.

---~---~---~---~---~---~---~---~---

'argument'
This variable is a string, showing the argument of a command resulting
in the activation of the DIL program. See SFB_CMD for example.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/openroll()

2025-12-04T22:37:08Z

Nove: XML import

integer openroll( dice : integer , end : integer )
dice : The size of the dice being rolled.
end : The margin for the open-ended roll.
return: A random integer in approximately +/- 2^31 in worst case.
Example: i := openroll(100,5); The "100" roll continues on values
96 - 100 and on values 1 - 5.

---~---~---~---~---~---~---~---~---

integer openroll( dice : integer , end : integer )
dice : The size of the dice being rolled.
end : The margin for the open-ended roll.
return: A random integer in approximately +/- 2^31 in worst case.
Example: i := openroll(100,5); The "100" roll continues on values
96 - 100 and on values 1 - 5.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/quit

2025-12-04T22:37:06Z

Nove: XML import

quit:
This simple command quits the entire DIL program, even if
called while inside a procedure or function.

---~---~---~---~---~---~---~---~---

quit:
This simple command quits the entire DIL program, even if
called while inside a procedure or function.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/dilfind()

2025-12-04T22:36:58Z

Nove: XML import

integer dilfind( s : string, u : unitptr )
s : name of dil template to find.
u : unit to find program in.
return: Whether a program using a template with same name as in 's'
attached to unit 'u' was found.

---~---~---~---~---~---~---~---~---

integer dilfind( s : string, u : unitptr )
s : name of dil template to find.
u : unit to find program in.
return: Whether a program using a template with same name as in 's'
attached to unit 'u' was found.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/string

2025-12-04T22:36:58Z

Nove: XML import

'''String:'''

A string is some text. They are used for a lot of things such as command
arguments, room descriptions etc. String variables are automatically resized and
allocated when you assign them, so you do not have to worry about the string
length nor allocation in your DIL programs. Strings may be compared either with
'==' (equal to),
'!=' (not equal),
'<=' (less than or equal to),
'>=' (greater than or equal to)
'<' (less than),
'>' (greater than.

Static strings are defined just as in the rest of the zone, within double
quotations. Strings may be searched easily with the 'in' operator. Variables
of type string are saved with DIL programs, if attached to a saved unit.

'''Example:'''

"This is a static string"

Strings may also be added to each other, in an expression.

'''Example:'''

"say "+itoa(42)+" is the answer!"

'''Example:'''

if (self.name == self.names.[1]) ...

Elements of the string can also be accessed by referencing them by their position.

'''Example'''
if (str.[3]==f])
'''Note'''
Currently you can only access the single elements of a string you can not set
them. In the future this will be possible. You can still accomplish this by
copying one string to the other one element at a time and changing any that you
want something like this.

'''Example'''
i:=0;
ln:=length (str);
while (str.[i]<ln)
str:=newstr;

This snip of Dil would replace any 'f' in a string with a 'b' remember dil is
not case sensitive so it will also replace an 'F'.

---~---~---~---~---~---~---~---~---

'''String:'''

A string is some text. They are used for a lot of things such as command
arguments, room descriptions etc. String variables are automatically resized and
allocated when you assign them, so you do not have to worry about the string
length nor allocation in your DIL programs. Strings may be compared either with
'==' (equal to),
'!=' (not equal),
'<=' (less than or equal to),
'>=' (greater than or equal to)
'<' (less than),
'>' (greater than.

Static strings are defined just as in the rest of the zone, within double
quotations. Strings may be searched easily with the 'in' operator. Variables
of type string are saved with DIL programs, if attached to a saved unit.

'''Example:'''

"This is a static string"

Strings may also be added to each other, in an expression.

'''Example:'''

"say "+itoa(42)+" is the answer!"

'''Example:'''

if (self.name == self.names.[1]) ...

Elements of the string can also be accessed by referencing them by their position.

'''Example'''
if (str.[3]==f])
'''Note'''
Currently you can only access the single elements of a string you can not set
them. In the future this will be possible. You can still accomplish this by
copying one string to the other one element at a time and changing any that you
want something like this.

'''Example'''
i:=0;
ln:=length (str);
while (str.[i]<ln)
str:=newstr;

This snip of Dil would replace any 'f' in a string with a 'b' remember dil is
not case sensitive so it will also replace an 'F'.

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/weapon info()

2025-12-04T22:36:57Z

Nove: XML import

'''Function:''' intlist weapon_info( i : integer ) ;

 '''i'''
 Weapon to get the info of ass defined in 'values.h' and 'weapons.def'
 '''returns'''
 Intlist containing 4 values:

 '''0'''
 Number of hands
 '''1'''
 weapon speed
 '''2'''
 weapon type
 '''3'''
 shield block value

This function gives you access to the values in the weapons.def file.
With this things like 'wear' equipment' and 'look' are much easier to
write in Dil.
'''Example'''

---~---~---~---~---~---~---~---~---

dilcopy id_weap (arg:string);
var
i:integer;
il:intlist;
code
dilend

---~---~---~---~---~---~---~---~---




'''Function:''' intlist weapon_info( i : integer ) ;

 '''i'''
 Weapon to get the info of ass defined in 'values.h' and 'weapons.def'
 '''returns'''
 Intlist containing 4 values:

 '''0'''
 Number of hands
 '''1'''
 weapon speed
 '''2'''
 weapon type
 '''3'''
 shield block value

This function gives you access to the values in the weapons.def file.
With this things like 'wear' equipment' and 'look' are much easier to
write in Dil.
'''Example'''

---~---~---~---~---~---~---~---~---

dilcopy id_weap (arg:string);
var
i:integer;
il:intlist;
code
dilend

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/self

2025-12-04T22:36:56Z

Nove: XML import

'self'
This variable is a unitptr to the unit owning the DIL program.
For C++ people, this is like the 'this' pointer.
For example, if Mary has a program, then self.title equals
"Mary the Lumberjack wife"

---~---~---~---~---~---~---~---~---

'self'
This variable is a unitptr to the unit owning the DIL program.
For C++ people, this is like the 'this' pointer.
For example, if Mary has a program, then self.title equals
"Mary the Lumberjack wife"

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/cmdptr

2025-12-04T22:36:54Z

Nove: XML import

'''Type: '''cmdptr
'''cmdptr fields'''

'''name'''
string - command name
'''type'''
integer - command type like social or skill or just command
'''level'''
integer - minimum level to use command
'''loglevel'''
integer - level of character that can see the log 0 for no logs
'''position'''
integer - minimum position to use command
'''next'''
cmdptr - pointer to the next cmdptr
'''previous'''
cmdptr - pointer to the previous cmdptr

The cmdptr can be used to search the command list or display all the commands.
I0t is also now possible to sort the commands by type by defining your own command
types and using the type field to sort on.

In order to get the first command in the list you use the following function:
'''Function: '''chead();
If you want to get a specific command then you use the following function:
'''Function: '''cmdptr := getcommand (s : string );
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin cmdtst(arg : string);
var
cmd : cmdptr;
st : string;

code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---

'''Type: '''cmdptr
'''cmdptr fields'''

'''name'''
string - command name
'''type'''
integer - command type like social or skill or just command
'''level'''
integer - minimum level to use command
'''loglevel'''
integer - level of character that can see the log 0 for no logs
'''position'''
integer - minimum position to use command
'''next'''
cmdptr - pointer to the next cmdptr
'''previous'''
cmdptr - pointer to the previous cmdptr

The cmdptr can be used to search the command list or display all the commands.
I0t is also now possible to sort the commands by type by defining your own command
types and using the type field to sort on.

In order to get the first command in the list you use the following function:
'''Function: '''chead();
If you want to get a specific command then you use the following function:
'''Function: '''cmdptr := getcommand (s : string );
'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin cmdtst(arg : string);
var
cmd : cmdptr;
st : string;

code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---

Manual:DIL Manual/Making a Program

2025-12-04T22:36:54Z

Nove: XML import

<h3>'''Making a program:'''</h3>

You define your DIL programs within your zone file. Each program you make is a
*template*. Such a template must be equipped with a unique name (for that zone).
Templates can either be defined in a new %dil section, just below the %zone
section in the zone file, or directly attached to units defined in your zonefile.

If you define your DIL templates inside a unit definition, that unit is
automatically assigned a program using that template. If you want to use an
already designed template, either in your own, or another zone, you use a
special function named "dilcopy", that takes the name of a template, and any
optional parameters in parenthesis. The parameters of a template called with
'dilcopy' may only be of types integer, strings and stringlists.

'''Example:'''

dilcopy myfunc@myzone("say Hello, my friend!", 1, CMD_SAY,
);

DIL templates can always be reused. In fact, with version 2.0 of DIL, programs
are no longer saved with equipment, but only a symbolic reference is used. That
way, if you make a change in your zone, ALL units using that program are changed.
This however requires you keep the name. Upon loading, if a template is not
found, the program is halted and rendered useless until such a reference can be
found during loading.

Technical note:

When you use several 'dilcopy' in your zonefile, only one instance is present
game-time, thus saving tremendous amounts of memory. It is similar to a shared
library, in which code is shared but variables are not.

You may use your templates to define both procedure and functions for your other
templates to call.

A template is defined by beginning with 'dilbegin' and ending with 'dilend'.
Inside the template your program section is defined, marked by the keyword 'code',
followed by the program itself;

<nowiki>

dilbegin myprogram();
var
i : integer;
j : integer;

code
dilend</nowiki>

This simple template does nothing but making its owner say 'Hello world' once
every 5 seconds. The template is called 'myprogram' and takes no arguments. The
'pause' command waits for the program to receive a timer message, whose interval
is set by the 'inline' variable 'heartbeat'. The 'self' variable is a unitptr
referring to the unit owning the DIL program. Other inline variables will be
explained later.

For a DIL program to work, it must be part of a *unit*: a room, player, non-player
or object. The program uses *messages* to operate. Your program gets activated
when it receives a message that some command is being executed, or a certain amount
of time has passed. You decide yourself in the program, what to wait for, before
the program continues executing.

Supposing you want your program to contain variables, you have to put them in a
section before the 'code' section marked 'var'. The variables are declared by
their type and their name, separated by a ':' and ended by a ';'

For an example, see the program above. Variables of type 'string', 'stringlist'
and 'integer' are saved, if the unit the program is attached to is saved with
player inventory. Variables of type 'unitpr' and 'extraptr' are 'volatile'. This
means that they are cleared whenever there is a chance that their contents may
have been rendered non usable. This ensures that you do not have any 'loose'
pointers. However it is possible to 'secure' the contents of a 'unitptr' type
variable of a unit located in your local environment (the units directly 'visible'
to the unit who owns the DIL program) (see the secure / unsecure functions).


<h3>'''Making a program:'''</h3>

You define your DIL programs within your zone file. Each program you make is a
*template*. Such a template must be equipped with a unique name (for that zone).
Templates can either be defined in a new %dil section, just below the %zone
section in the zone file, or directly attached to units defined in your zonefile.

If you define your DIL templates inside a unit definition, that unit is
automatically assigned a program using that template. If you want to use an
already designed template, either in your own, or another zone, you use a
special function named "dilcopy", that takes the name of a template, and any
optional parameters in parenthesis. The parameters of a template called with
'dilcopy' may only be of types integer, strings and stringlists.

'''Example:'''

dilcopy myfunc@myzone("say Hello, my friend!", 1, CMD_SAY,
);

DIL templates can always be reused. In fact, with version 2.0 of DIL, programs
are no longer saved with equipment, but only a symbolic reference is used. That
way, if you make a change in your zone, ALL units using that program are changed.
This however requires you keep the name. Upon loading, if a template is not
found, the program is halted and rendered useless until such a reference can be
found during loading.

Technical note:

When you use several 'dilcopy' in your zonefile, only one instance is present
game-time, thus saving tremendous amounts of memory. It is similar to a shared
library, in which code is shared but variables are not.

You may use your templates to define both procedure and functions for your other
templates to call.

A template is defined by beginning with 'dilbegin' and ending with 'dilend'.
Inside the template your program section is defined, marked by the keyword 'code',
followed by the program itself;

<nowiki>

dilbegin myprogram();
var
i : integer;
j : integer;

code
dilend</nowiki>

This simple template does nothing but making its owner say 'Hello world' once
every 5 seconds. The template is called 'myprogram' and takes no arguments. The
'pause' command waits for the program to receive a timer message, whose interval
is set by the 'inline' variable 'heartbeat'. The 'self' variable is a unitptr
referring to the unit owning the DIL program. Other inline variables will be
explained later.

For a DIL program to work, it must be part of a *unit*: a room, player, non-player
or object. The program uses *messages* to operate. Your program gets activated
when it receives a message that some command is being executed, or a certain amount
of time has passed. You decide yourself in the program, what to wait for, before
the program continues executing.

Supposing you want your program to contain variables, you have to put them in a
section before the 'code' section marked 'var'. The variables are declared by
their type and their name, separated by a ':' and ended by a ';'

For an example, see the program above. Variables of type 'string', 'stringlist'
and 'integer' are saved, if the unit the program is attached to is saved with
player inventory. Variables of type 'unitpr' and 'extraptr' are 'volatile'. This
means that they are cleared whenever there is a chance that their contents may
have been rendered non usable. This ensures that you do not have any 'loose'
pointers. However it is possible to 'secure' the contents of a 'unitptr' type
variable of a unit located in your local environment (the units directly 'visible'
to the unit who owns the DIL program) (see the secure / unsecure functions).

Manual:DIL Manual/spellindex()

2025-12-04T22:36:46Z

Nove: XML import

integer spellindex(s : string)
s : The abbreviated or full spell name

Returns: -1 if no such spell, otherwise it returns the spell index
for that spell.

Example:
s := "cu li wo"; /* cure light wounds */
i := spellindex(s);

---~---~---~---~---~---~---~---~---

integer spellindex(s : string)
s : The abbreviated or full spell name

Returns: -1 if no such spell, otherwise it returns the spell index
for that spell.

Example:
s := "cu li wo"; /* cure light wounds */
i := spellindex(s);

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/send done()

2025-12-04T22:36:46Z

Nove: XML import

'''Function:'''
send_done( c : string, a :unitptr, m : unitptr, t :unitptr, p : integer, arg : string, o : unitptr);

 '''c'''
 the command string that is sending the message
 '''a'''
 the unitptr (activator) that activated the message
 '''m'''
 the unitptr (medium) that the Dil is acting through
 '''t'''
 the unitptr (target) the Dil is acting on
 '''p'''
 the power of the message
 '''arg'''
 the argument sent with the message
 '''o'''
 the unitptr (other) you also want the message to go to

This sends the 'SFB_DONE' message to any dils that are waiting for it in the
surrounding area and to the other pointer if not null. The following is just
one example you can find many more in '''commands.zon'''

'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin do_read (arg:string);
var
brdname:string;
i:integer;
u:unitptr;
x:extraptr;
ln:integer;
temp:string;
templist:stringlist;
buff:string;
f_name:string;
act_str:string;
code
dilend

---~---~---~---~---~---~---~---~---




'''Function:'''
send_done( c : string, a :unitptr, m : unitptr, t :unitptr, p : integer, arg : string, o : unitptr);

 '''c'''
 the command string that is sending the message
 '''a'''
 the unitptr (activator) that activated the message
 '''m'''
 the unitptr (medium) that the Dil is acting through
 '''t'''
 the unitptr (target) the Dil is acting on
 '''p'''
 the power of the message
 '''arg'''
 the argument sent with the message
 '''o'''
 the unitptr (other) you also want the message to go to

This sends the 'SFB_DONE' message to any dils that are waiting for it in the
surrounding area and to the other pointer if not null. The following is just
one example you can find many more in '''commands.zon'''

'''Example:'''

---~---~---~---~---~---~---~---~---

dilbegin do_read (arg:string);
var
brdname:string;
i:integer;
u:unitptr;
x:extraptr;
ln:integer;
temp:string;
templist:stringlist;
buff:string;
f_name:string;
act_str:string;
code
dilend

---~---~---~---~---~---~---~---~---

Manual:DIL Manual/destroy()

2025-12-04T22:36:45Z

Nove: XML import

'''Function:''' destroy ( u : unitptr );

 '''u'''
 :Unit to remove from game

The destroy function works in two ways depending on the Unit being acted on.
If the Unit being acted on is a PC the player is saved and ejected from the game.
If the Unit being acted on is a NPC, or an Object. the purge function destroys
the Unit. Currently destroy will not destroy rooms.
This is different from the old destroy function in that it removes the player
out of the game instead of leaving the player in the menu.
'''Example'''

---~---~---~---~---~---~---~---~---

dilbegin purge_all_pc();
var
u:unitptr/*Unit used to purge each player*/
n:unitptr;/*used to keep track of next player*/
code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---


'''Function:''' destroy ( u : unitptr );

 '''u'''
 :Unit to remove from game

The destroy function works in two ways depending on the Unit being acted on.
If the Unit being acted on is a PC the player is saved and ejected from the game.
If the Unit being acted on is a NPC, or an Object. the purge function destroys
the Unit. Currently destroy will not destroy rooms.
This is different from the old destroy function in that it removes the player
out of the game instead of leaving the player in the menu.
'''Example'''

---~---~---~---~---~---~---~---~---

dilbegin purge_all_pc();
var
u:unitptr/*Unit used to purge each player*/
n:unitptr;/*used to keep track of next player*/
code
dilend

---~---~---~---~---~---~---~---~---



---~---~---~---~---~---~---~---~---

Manual:DIL Manual/addextra()

2025-12-04T22:36:43Z

Nove: XML import

addextra ( var e : extraptr, l : stringlist , s : string )
e : Extra description list to add element to.
l : Stringlist for the .names field.
s : String for the .descr field.
result: Adds an extra description to a list of extra descriptions.

CAVEAT builder: You cannot use an extraptr variable as the e
argument, but you may continue to use the following form:

...
...
addextra (self.quests, "Bozo's Quest");
...
...

---~---~---~---~---~---~---~---~---

addextra ( var e : extraptr, l : stringlist , s : string )
e : Extra description list to add element to.
l : Stringlist for the .names field.
s : String for the .descr field.
result: Adds an extra description to a list of extra descriptions.

CAVEAT builder: You cannot use an extraptr variable as the e
argument, but you may continue to use the following form:

...
...
addextra (self.quests, "Bozo's Quest");
...
...

---~---~---~---~---~---~---~---~---