Search results

Jump to navigation Jump to search

Page title matches

  • The block starts with the string "#TRIGGERS" without quotes, followed by This is an example of a triggers block:
    663 bytes (101 words) - 13:44, 5 October 2012
  • The block starts with the string "#RSPECS" without quotes, followed by one This is an example of a rspecs block:
    668 bytes (110 words) - 13:40, 5 October 2012
  • The block start with the string "#SHOPS" without quotes, followed by one This is an example of a shops block:
    1 KB (142 words) - 13:34, 5 October 2012
  • The block start with the string "#ROOMS" without quotes, followed by one This is an example of a rooms block:
    1 KB (211 words) - 13:27, 5 October 2012
  • The block starts with the string "#OBJECTS" without quotes, followed by This is an example of a objects block:
    385 bytes (59 words) - 13:20, 5 October 2012
  • The block start with the string "#RSPECS" without quotes, followed by one This is an example of a rspecs block:
    420 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#TRIGGERS" without quotes, followed by This is an example of a triggers block:
    441 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#SPECIALS" without quotes, followed by This is an example of a specials block:
    441 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#SHOPS" without quotes, followed by one This is an example of a shops block:
    410 bytes (64 words) - 10:35, 2 April 2011
  • The block start with the string "#RESETS" without quotes, followed by one This is an example of a resets block:
    420 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#ROOMS" without quotes, followed by one This is an example of a rooms block:
    428 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#OBJECTS" without quotes, followed by This is an example of a objects block:
    448 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#MOBILES" without quotes, followed by This is an example of a mobiles block:
    429 bytes (66 words) - 19:38, 1 June 2011
  • #REDIRECT [[Trig block heathen]]
    32 bytes (4 words) - 12:04, 27 December 2011
  • trig_block_heathen is a [[Extended Trigger Before Move]] trigger. It blocks non-followers from using the specified exit. This trigger can only be (us Q <room vnum> <door direction> trig_block_heathen <FLI PC number> <success msg or -1> <failure msg or -1> -1 <flags>
    1 KB (207 words) - 15:13, 1 November 2012
  • ...ired success message should '''only''' be specified for the last trig_time_block trigger, so that the correct message is displayed. Q <room vnum> <door direction> trig_time_block <start time (00-23)> <end time (00-23)> <success msg or -1> <fail msg or -1
    2 KB (285 words) - 15:13, 1 November 2012

Page text matches

  • #REDIRECT [[Trig block heathen]]
    32 bytes (4 words) - 12:04, 27 December 2011
  • The block starts with the string "#OBJECTS" without quotes, followed by This is an example of a objects block:
    385 bytes (59 words) - 13:20, 5 October 2012
  • The block start with the string "#RSPECS" without quotes, followed by one This is an example of a rspecs block:
    420 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#TRIGGERS" without quotes, followed by This is an example of a triggers block:
    441 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#SPECIALS" without quotes, followed by This is an example of a specials block:
    441 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#RESETS" without quotes, followed by one This is an example of a resets block:
    420 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#SHOPS" without quotes, followed by one This is an example of a shops block:
    410 bytes (64 words) - 10:35, 2 April 2011
  • The block start with the string "#ROOMS" without quotes, followed by one This is an example of a rooms block:
    428 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#OBJECTS" without quotes, followed by This is an example of a objects block:
    448 bytes (66 words) - 10:35, 2 April 2011
  • The block start with the string "#MOBILES" without quotes, followed by This is an example of a mobiles block:
    429 bytes (66 words) - 19:38, 1 June 2011
  • [[The Helps Block]] [[The Mobiles Block]]
    1 KB (169 words) - 10:29, 2 April 2011
  • ...After the final record in a block, a control marker occurs indicating the block is finished. ...o the area. Or if you have rooms in the file, you MUST have an area header block.
    2 KB (409 words) - 22:00, 4 February 2015
  • The block starts with the string "#TRIGGERS" without quotes, followed by This is an example of a triggers block:
    663 bytes (101 words) - 13:44, 5 October 2012
  • ...The Altar of Nayr is carved from a large block of ebony. The sides of the block are carved with mystical symbols, each of which invoke such distaste in you
    919 bytes (116 words) - 19:47, 30 January 2011
  • The block starts with the string "#RSPECS" without quotes, followed by one This is an example of a rspecs block:
    668 bytes (110 words) - 13:40, 5 October 2012
  • trig_block_heathen is a [[Extended Trigger Before Move]] trigger. It blocks non-followers from using the specified exit. This trigger can only be (us Q <room vnum> <door direction> trig_block_heathen <FLI PC number> <success msg or -1> <failure msg or -1> -1 <flags>
    1 KB (207 words) - 15:13, 1 November 2012
  • ...ired success message should '''only''' be specified for the last trig_time_block trigger, so that the correct message is displayed. Q <room vnum> <door direction> trig_time_block <start time (00-23)> <end time (00-23)> <success msg or -1> <fail msg or -1
    2 KB (285 words) - 15:13, 1 November 2012
  • ...unctions associated with rooms and doors. The are found in the [[Triggers Block|#TRIGGERS]] section of an area file. ...ecfuns, along with the Allow Specfuns, are placed together in the TRIGGERS block.
    1 KB (212 words) - 14:52, 19 November 2012
  • ...ecfuns, along with the Allow Specfuns, are placed together in the TRIGGERS block.
    808 bytes (148 words) - 22:53, 15 February 2017
  • ...unctions associated with rooms and doors. The are found in the [[Triggers Block|#TRIGGERS]] section of an area file. ...funs, along with the Prevent Specfuns, are placed together in the TRIGGERS block.
    1 KB (204 words) - 12:45, 12 July 2011

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)