Building Guide - Revision history

Admin: /* Shopkeepers */

2023-01-17T21:48:52Z

Shopkeepers

← Older revision		Revision as of 14:48, 17 January 2023
Line 188:		Line 188:

	===Shopkeepers===		===Shopkeepers===

			* ''For more information on how shops can be interacted with by a player, see [[Shops]].''

	To make a mobile a shopkeeper, use the syntax "shop assign" while editing the desired mobile. Typing just "shop" while in MEdit will display possible shopkeeper-related commands.		To make a mobile a shopkeeper, use the syntax "shop assign" while editing the desired mobile. Typing just "shop" while in MEdit will display possible shopkeeper-related commands.

	Shopkeepers can have mobprogs like regular mobs with the exception of give progs, always giving an error that the player must sell the item instead.		;shop assign
			:Flags the mobile as a shopkeeper, meaning that players can use the 'buy' command to purchase items out of its inventory. You will need to get items into its inventory using resets or mobprogs or something. By default, a shop will sell things at 100% of their value, be open 24/7, and buy no item types (but have the buy value at 100% anyway).
			;shop remove
			:Un-flags the mobile as a shopkeeper.
			;shop hours (#open) (#close)
			:Shops can be hardcoded to be only available for buying and selling in certain hours of the in-game day. A player attempting to interact with the shop while it is closed will result in the mob saying "Sorry, I am closed. Come back at (time the shop opens)".
			:You will need to use mobprogs if you want a shop restricted in more arbitrary ways, such as days of the week.
			;shop profit (%buying) (%selling)
			:This will set a shop's profit margins, by specifying what percent of an items' value it will pay for something, and what percent of an item's value it will sell things at. The Haggle skill will change these numbers in practice.
			;shop type (#0-4) (item type)
			:Shops can be set to buy up to five types of items, numbered zero through four. It is not currently possible to have a shop that buys more than 5 distinct item types. The Swindle skill can avoid this restriction entirely.

			Shopkeepers can have mobprogs like regular mobs with the exception of give progs, always giving an error that the player must sell the item instead.

	==OEDIT==		==OEDIT==

Pascal: added shopkeeper info to medit section

2021-06-01T01:04:02Z

added shopkeeper info to medit section

← Older revision		Revision as of 18:04, 31 May 2021
Line 186:		Line 186:

	For a list of all applicable mob flags, see [[Flags_Compendium#MOB_FLAGS]], or type '''? (flag name)''' while in medit mode.		For a list of all applicable mob flags, see [[Flags_Compendium#MOB_FLAGS]], or type '''? (flag name)''' while in medit mode.

			===Shopkeepers===

			To make a mobile a shopkeeper, use the syntax "shop assign" while editing the desired mobile. Typing just "shop" while in MEdit will display possible shopkeeper-related commands.

			Shopkeepers can have mobprogs like regular mobs with the exception of give progs, always giving an error that the player must sell the item instead.

	==OEDIT==		==OEDIT==

Admin: /* Description Style Tips */

2020-12-16T16:16:10Z

Description Style Tips

← Older revision		Revision as of 09:16, 16 December 2020
Line 92:		Line 92:
	Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.		Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.

	Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse. That said, sometimes it's more fun to write them subjectively; be		Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse. That said, sometimes it's more fun to write them subjectively; be creative!

	====Extra Descriptions====		====Extra Descriptions====

Admin: /* Names */

2020-12-06T23:03:11Z

Names

← Older revision		Revision as of 16:03, 6 December 2020
Line 37:		Line 37:
	Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.		Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.

	If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior.		A mobile or object's name consists of several words, separated by spaces. Words can also be enclosed in double quotes, if necessary. If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior. If a mobile's name is '"green imp"' with both words enclosed by double quotes, then 'look green' will work while 'look imp' will not, but 'look "green imp"' will!

	If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.		If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.

Pascal: /* Editing Quest Lists */

2019-12-11T02:21:18Z

Editing Quest Lists

← Older revision		Revision as of 19:21, 10 December 2019
Line 344:		Line 344:

	===Editing Quest Lists===		===Editing Quest Lists===
	Each area also has a corresponding quest list to be stored as: '''areaname.are.quests''' (like truce.are.quests). These are basically just text, except you can use the string '''^areaname1''' to show whether that questflag has been obtained or not. See any other quests lists for examples.		Each area also has a corresponding quest list to be stored as: '''areaname.are.quests''' (like truce.are.quests). These are basically just text, except you can use the string '''^areaname1''' to show whether that questflag has been obtained or not. You can also hide quests until they are completed by prefacing them with two ^ i.e. '''^^areaname2'''. These hidden quests will not show up as blank lines but are entirely undetectable. See any other quests lists for examples.

	==SEDIT==		==SEDIT==

Admin: /* SEDIT */

2019-11-29T02:55:13Z

SEDIT

← Older revision		Revision as of 19:55, 28 November 2019
Line 350:		Line 350:

	Avoid making new socials simply for entertainment purposes, as this will add more clutter to the socials list, which is utilized by players to maneuver through rooms, puzzles or quests at times. Existing social commands are for the most part set in stone. Changing existing output can cause quests to fail activation. If a condition arises where the syntax should indeed be changed, an admin should run a find and replace for relevant mprog triggers.		Avoid making new socials simply for entertainment purposes, as this will add more clutter to the socials list, which is utilized by players to maneuver through rooms, puzzles or quests at times. Existing social commands are for the most part set in stone. Changing existing output can cause quests to fail activation. If a condition arises where the syntax should indeed be changed, an admin should run a find and replace for relevant mprog triggers.

			==GEDIT==
			coming soon

			Edits clans: will probably change dramatically in the future as clan code is changed.

Admin: /* Flags */

2019-11-29T02:54:14Z

Flags

← Older revision		Revision as of 19:54, 28 November 2019
Line 306:		Line 306:

	===Flags===		===Flags===
	Areas have two types of flags: area flags, and exflags. Exflags can be set by a builder, and have various practical effects on the area for players. The list is at [[Flags_Compendium#AREA_EXFLAGS]]		Areas have two types of flags: area flags, and exflags. Exflags can be set by a builder by using 'exflags (flag)', and have various practical effects on the area for players. The list is at [[Flags_Compendium#AREA_EXFLAGS]]

	The other kind of Area flags are for temporary weather up/down affects (caused by the Stormy Sky and Clear Sky affects) and other things about the loading/saving of area files:		The other kind of Area flags are for temporary weather up/down affects (caused by the Stormy Sky and Clear Sky affects) and other things about the loading/saving of area files:

Admin: /* AEDIT */ finally documented aedit

2019-11-29T02:53:25Z

AEDIT: finally documented aedit

@@ Line 273: / Line 273: @@
 ==AEDIT==
-coming soon
+Aedit is the mode used to create and modify area files, their vnum ranges, and certain area-wide flags and settings.
 ==HEDIT==

Admin at 10:24, 17 December 2017

2017-12-17T10:24:25Z

← Older revision		Revision as of 03:24, 17 December 2017
Line 33:		Line 33:
	===Saving your Work===		===Saving your Work===
	It is vitally important to save completed work often. If the game crashes or is rebooted without saving, any work done will be lost forever. To save your work, type '''asave changed''' frequently. This works in all edit modes and will save everything that has been changed or created.		It is vitally important to save completed work often. If the game crashes or is rebooted without saving, any work done will be lost forever. To save your work, type '''asave changed''' frequently. This works in all edit modes and will save everything that has been changed or created.

			===Names===
			Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.

			If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior.

			If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.

	===Short Descriptions===		===Short Descriptions===
Line 43:		Line 50:

	Note that long descs are not the same as a mobile's 'description'.		Note that long descs are not the same as a mobile's 'description'.

	~~If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead. For example:~~
	*name: silver sword runes
	*short: a silver sword with runes
	*long: Covered with runes, a silver sword has been left here.
	*extra desc with keyword 'runes': These runes are in a long forgotten language.
	*"look sword"/"look silver": "Covered with runes, a silver sword has been left here."
	*"look runes": "These runes are in a long forgotten language."

	~~===Names===~~
	Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.

	If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior.

	If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.

	==REDIT==		==REDIT==
Line 76:		Line 68:
	Rooms can have two-way and one-way [[exits]].		Rooms can have two-way and one-way [[exits]].

	To create a two-way exit from a room, type '''(direction) link (other room)''', where direction is which way the exit will be in this room. Two-way exits are always linked opposite of each other EG if Room A has a two-way exit West to Room B, then Room B will have an exit East to Room A. A door on one side of a two-way exit will let people on the other side know that it has been opened.		To create a two-way exit from a room, type '''(direction) link (other room)''', where direction is which way the exit will be in this room. Two-way exits are always linked opposite of each other E.G. if Room A has a two-way exit West to Room B, then Room B will have an exit East to Room A. A door on one side of a two-way exit will let people on the other side know that it has been opened.

	To create a one-way exit from a room, type '''(direction) room (other room)'''. One-way exits don't do anything to the room on the other side, so be careful not to create dead-ends when using one-way exits.		To create a one-way exit from a room, type '''(direction) room (other room)'''. One-way exits don't do anything to the room on the other side, so be careful not to create dead-ends when using one-way exits.
Line 100:		Line 92:
	Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.		Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.

	Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse.		Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse. That said, sometimes it's more fun to write them subjectively; be

	====Extra Descriptions====		====Extra Descriptions====
Line 231:		Line 223:
	@		@

			If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead. For example:
			*name: silver sword runes
			*short: a silver sword with runes
			*long: Covered with runes, a silver sword has been left here.
			*extra desc with keyword 'runes': These runes are in a long forgotten language.
			*"look sword"/"look silver": "Covered with runes, a silver sword has been left here."
			*"look runes": "These runes are in a long forgotten language."

	===Stats===		===Stats===

Admin: /* Long Descriptions */

2017-12-17T10:20:19Z

Long Descriptions

← Older revision		Revision as of 03:20, 17 December 2017
Line 44:		Line 44:
	Note that long descs are not the same as a mobile's 'description'.		Note that long descs are not the same as a mobile's 'description'.

	If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead.		If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead. For example:
			*name: silver sword runes
			*short: a silver sword with runes
			*long: Covered with runes, a silver sword has been left here.
			*extra desc with keyword 'runes': These runes are in a long forgotten language.
			*"look sword"/"look silver": "Covered with runes, a silver sword has been left here."
			*"look runes": "These runes are in a long forgotten language."

	===Names===		===Names===