Andreas/tbamud
1
0
Fork 0
mirror of https://github.com/tbamud/tbamud.git synced 2026-04-08 13:24:37 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clean up legacy practice code

Browse source
This commit is contained in:
kinther 2025-12-27 15:28:42 -08:00
parent e5515f4ca5
commit 8eb30084b0
16 changed files with 59 additions and 745 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/building.txt
View file

@ -226,7 +226,7 @@ sell objects to players.
A single zone typically contains up to than 100 rooms, 100 monster definitions
and 100 object definitions, but a large region can be subdivided into several
zones at the author’s discretion. For example, the City of Midgaard is divided
zones at the author’s discretion. For example, a large city can be divided
into two zones, one for the main city and one for the southern residential area.
In addition to this, with the new zone system describing top and bottom rooms
of a zone, zones can contain very few rooms and indeed can overlap with other
@ -242,7 +242,7 @@ independent, so there can be both a room number 3001 and an object number
refers to each entity by its Vnum and never by name. Vnums are normally not
seen by players. Each zone itself also has a Vnum. A common convention is to
number the zone with the Vnums of its component rooms, divided by 100. For
example, Midgaard is zone 30, consisting of rooms 3000 to 3099. Mobile and
example, the main city is zone 30, consisting of rooms 3000 to 3099. Mobile and
object numbering follows the same convention.
The author of the zone can define aspects of each room such as the terrain type,
@ -1311,7 +1311,7 @@ terminated by the literal letter S.
Virtual Number An arbitrary number used to identify the zone. Zone numbers are
traditionally the room numbers of the zone divided by 100; for example,
Midgaard, which consists of rooms 3000 through 3099, is zone 30.
The main city, which consists of rooms 3000 through 3099, is zone 30.
Zone Name A label given to the zone so that it can be identified in system
logs.
@ -1444,7 +1444,7 @@ Zone File Example
A sample zone file annotated with comments follows.
#30 * This is zone number 30
Northern Midgaard Main City~ * The name of the zone
Northern Main City~ * The name of the zone
3099 15 2 * Top of zone is room #3099; it resets every 15 minutes.
* * Resets regardless of people.
*
@ -1823,7 +1823,7 @@ interactions you want it to perform. See the help files in game for details.
8.2 Trigger File Example
#100
Obj Command 100 - portal to Midgaard~
Obj Command 100 - portal to the capital~
1 c 7
en~
if %cmd.mudcommand% == enter && %arg% /= portal

4
doc/coding.txt
View file

@ -1559,7 +1559,7 @@ foreground colors.
Basic special procedures have largely been replaced by trigedit. Thus shifting the
workload from the coder to the builder to add life and creativity into their zones.
While it is easier, and less time consuming, to make triggers than special
procedures they are still used for such functions as banks and guildmasters.
procedures they are still used for such functions as banks.
Using special procedures, your virtual world is not just a bunch of monsters,
objects and rooms, reduced to a number of statistics. Just like good descriptions
@ -1570,7 +1570,7 @@ Several special procedures are provided with stock tbaMUD which you can use to
create your own and get used to the mechanics of special procedures. These special
procedures can be found in castle.c and spec_procs.c. They range from very simple
procedures, like puff (pulsed special procedure) or bank (command-driven special
procedure), to very complex procedures like the guild master.
procedure), to very complex procedures.
In this chapter, FALSE refers to the value 0 and TRUE to any non-zero value.