LADY scripts

LADY is LORD's scripting language for events. LORD FP runs LORD 4.06's scripts and LORD 4.07/4.08's.

If LORD.LDY is in the game directory, the forest's random events come from it, as in LORD 4.06: the game runs its quest LORD. LORD 4.06's own LORD.LDY picks one of the events in EVENTS.LDY: the old man, a sack of gold, a Hammer Stone, a gem, the horse seller. File names are matched in any case.

Edit them, or add scripts such as Belgarion's LORD LADY scripts, as LORD 4.06's LADY.DOC describes. The fairies, Olivia, the flower garden, the dungeon and the other big events stay built in. Without LORD.LDY the game uses its own versions of those events.

The extra commands in 4.07's LADY.DOC work:

• +, - and ! in @set; <> and != in @if;
• @saveplayer, @endgame, @changearm, @changewep, @setbit, @openfile and the rest.

And the other hooks:

&rnd<n> gives 1 to n, as 4.07's LADY.DOC says (4.06's said 0 to n; its own scripts work either way).

4.07-style events (with an @#INSTALL quest) are installed with lordcfg's E (LADY events) screen, as with 4.07's LORDCFG. Give it the event's .LDY file and it:

• adds the event and makes LORD.LDY, INN.LDY or BANK.LDY again (each event in a file has the same chance), or
• adds an Other Places entry (@LADY <event> <file> in 3RDPARTY.DAT).

Uninstall runs the event's @#UNINSTALL and shows what it would delete first. Events can also be turned off and on. The list is kept in ladyevnt.dat (LADYEVNT.DAT on DOS).

The first time, the events in the current LORD.LDY, INN.LDY and BANK.LDY are taken over (the originals are kept as LORD.ORG, INN.ORG and BANK.ORG), so a hand-made LORD.LDY keeps working. 4.06-style scripts (no @#INSTALL) are still added by hand, but once lordcfg manages LORD.LDY, add them through it or they will be overwritten.

lord -debug (LORD.EXE <node> /DEBUG on DOS) writes every script line it runs to lady.log in the game directory. In the forest:

• 3 runs LORD.LDY, as in LORD 4.06;
• X runs quest TEST in TEST.LDY, as in 4.07.