WorldBuildingGuide - Revision history

Loki: /* Guildmasters */

2024-06-27T19:13:34Z

Guildmasters

← Older revision		Revision as of 19:13, 27 June 2024
Line 41:		Line 41:

	====Guildmasters====		====Guildmasters====
	*Guildmasters is a term which generally refers to a MOBTeacher who trains one or more classes.		*Guildmasters is a term which generally refers to a [[MOBTeacher]] who trains one or more classes.
			**To ensure full functionality, you may need to also add [[Prop_Trainer]] to the mob.
	*Aside from the capitol cities, Guildmasters should generally know one class only.		*Aside from the capitol cities, Guildmasters should generally know one class only.
	**A guildmaster that has multiple classes will divide his level amongst all classes he can train. So a MOBTeacher(Mage Abjurer Alterer Conjurer) would divide his levels by 4 to determine the maximum level of spells he could train.		**A guildmaster that has multiple classes will divide his level amongst all classes he can train. So a MOBTeacher(Mage Abjurer Alterer Conjurer) would divide his levels by 4 to determine the maximum level of spells he could train.

Loki: /* Shopkeepers */

2024-06-27T16:22:33Z

Shopkeepers

← Older revision		Revision as of 16:22, 27 June 2024
Line 60:		Line 60:
	*It is a good idea to grant your shopkeepers senses to see in the dark if you want them to interact with DROW.		*It is a good idea to grant your shopkeepers senses to see in the dark if you want them to interact with DROW.
	*Shopkeepers should generally have 30 bonus hit points per level, and have half the attack and damage of a normal mob their level. This will effectively draw out their fights so that any local city guards can come to their defense.		*Shopkeepers should generally have 30 bonus hit points per level, and have half the attack and damage of a normal mob their level. This will effectively draw out their fights so that any local city guards can come to their defense.
			*It is generally best if shopkeepers are not affected by [[Inebriation]], as they may hand items and money out to the wrong people mistakenly.

	===Item Design===		===Item Design===

Loki: /* Mob Names */

2024-06-27T15:56:21Z

Mob Names

← Older revision		Revision as of 15:56, 27 June 2024
Line 21:		Line 21:
	*Proper Names of mobs should be capitalized.		*Proper Names of mobs should be capitalized.
	**Mobs without a proper name should have NO capitalization (it may appear capitalized in the CL, but verify it is not capitalized when you enter the name).		**Mobs without a proper name should have NO capitalization (it may appear capitalized in the CL, but verify it is not capitalized when you enter the name).
	**Mobs without a proper name should include an article (the assassin or ~~some~~ butterflies).		**Mobs without a proper name should include an article (the assassin or a kaleidoscope of butterflies).
			**Avoid using a plural name, such as crickets. Instead, consider using the singular of a group of crickets. This will avoid noun-verb mismatches in mudchat and other behaviors.
	**Do not start the name with a number. For example instead of "1st SGT Smith" use "First Sergeant Smith" or "a first sergeant"		**Do not start the name with a number. For example instead of "1st SGT Smith" use "First Sergeant Smith" or "a first sergeant"
	*If you give the name a color code, be sure to properly close off that color code so it doesn't bleed into other text.		*If you give the name a color code, be sure to properly close off that color code so it doesn't bleed into other text.

Loki: /* Item Names */

2024-06-27T15:53:54Z

Item Names

← Older revision		Revision as of 15:53, 27 June 2024
Line 64:		Line 64:
	The name field is the short name of the item. It should fit inside the sentence "You pick up (item name)."		The name field is the short name of the item. It should fit inside the sentence "You pick up (item name)."

	When you name an item, the NAME field should be in lower case, unless it is a proper name.		*When you name an item, the NAME field should be in lower case, unless it is a proper name.
	*Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).		*Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).
	*The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.		*The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.

Loki: /* Item Names */

2024-06-27T15:53:19Z

Item Names

← Older revision		Revision as of 15:53, 27 June 2024
Line 62:		Line 62:
	===Item Design===		===Item Design===
	====Item Names====		====Item Names====
			The name field is the short name of the item. It should fit inside the sentence "You pick up (item name)."

	When you name an item, the NAME field should be in lower case, unless it is a proper name.		When you name an item, the NAME field should be in lower case, unless it is a proper name.
	*Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).		*Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).

Loki: /* Mob Names */

2024-06-27T15:52:15Z

Mob Names

← Older revision		Revision as of 15:52, 27 June 2024
Line 23:		Line 23:
	**Mobs without a proper name should include an article (the assassin or some butterflies).		**Mobs without a proper name should include an article (the assassin or some butterflies).
	**Do not start the name with a number. For example instead of "1st SGT Smith" use "First Sergeant Smith" or "a first sergeant"		**Do not start the name with a number. For example instead of "1st SGT Smith" use "First Sergeant Smith" or "a first sergeant"
			*If you give the name a color code, be sure to properly close off that color code so it doesn't bleed into other text.
	*Female Barbarians can also be called Amazons.		*Female Barbarians can also be called Amazons.

Loki: /* Item Names */

2024-06-27T15:51:52Z

Item Names

← Older revision		Revision as of 15:51, 27 June 2024
Line 65:		Line 65:
	*The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.		*The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.
	*Do not start the name with a number. Spell out the number if you need to instead of using the digit version...or better yet, start it with an article.		*Do not start the name with a number. Spell out the number if you need to instead of using the digit version...or better yet, start it with an article.
			*If you give the name a color code, be sure to properly close off that color code so it doesn't bleed into other text.

	====Other Item Notes====		====Other Item Notes====

Loki: /* Item Design */

2024-06-27T15:49:20Z

Item Design

← Older revision		Revision as of 15:49, 27 June 2024
Line 60:		Line 60:

	===Item Design===		===Item Design===
	*When you name an item, the NAME field should be in lower case, unless it is a proper name.		====Item Names====
	**Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).		When you name an item, the NAME field should be in lower case, unless it is a proper name.
	**The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.		*Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).
	**Do not start the name with a number. Spell out the number if you need to instead of using the digit version...or better yet, start it with an article.		*The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.
			*Do not start the name with a number. Spell out the number if you need to instead of using the digit version...or better yet, start it with an article.

			====Other Item Notes====
	*The DISPLAY field should start in uppercase, and should be a complete sentence describing how the item is at rest.		*The DISPLAY field should start in uppercase, and should be a complete sentence describing how the item is at rest.
	*The DESCRIPTION field should start in uppercase, and should be complete sentences.		*The DESCRIPTION field should start in uppercase, and should be complete sentences.

Loki: /* Item Design */

2024-06-27T15:45:01Z

Item Design

← Older revision		Revision as of 15:45, 27 June 2024
Line 60:		Line 60:

	===Item Design===		===Item Design===
	*When you name an item, the NAME field should be in lower case, unless it is a proper name. The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.		*When you name an item, the NAME field should be in lower case, unless it is a proper name.
			**Use an article before the name whenever possible (a/an, the, some, etc) so that the language parser has an easier time of identifying sentence tense (a pair of pants, vs pants).
			**The NAME field should be a very brief name. If the NAME field is too long, items will not be properly displayed in shop inventories. Try to keep item NAMEs to under 20 characters in length.
			**Do not start the name with a number. Spell out the number if you need to instead of using the digit version...or better yet, start it with an article.
	*The DISPLAY field should start in uppercase, and should be a complete sentence describing how the item is at rest.		*The DISPLAY field should start in uppercase, and should be a complete sentence describing how the item is at rest.
	*The DESCRIPTION field should start in uppercase, and should be complete sentences.		*The DESCRIPTION field should start in uppercase, and should be complete sentences.

Loki: /* Mob Design */

2024-06-27T15:41:36Z

Mob Design

← Older revision		Revision as of 15:41, 27 June 2024
Line 17:		Line 17:

	===Mob Design===		===Mob Design===

			====Mob Names====
			*Proper Names of mobs should be capitalized.
			**Mobs without a proper name should have NO capitalization (it may appear capitalized in the CL, but verify it is not capitalized when you enter the name).
			**Mobs without a proper name should include an article (the assassin or some butterflies).
			**Do not start the name with a number. For example instead of "1st SGT Smith" use "First Sergeant Smith" or "a first sergeant"
	*Female Barbarians can also be called Amazons.		*Female Barbarians can also be called Amazons.