UC MUD Code Planning - Revision history

Aurora: /* Action tables */

2011-10-28T19:02:09Z

Action tables

← Older revision		Revision as of 19:02, 28 October 2011
Line 87:		Line 87:
	\|-		\|-
	\| Energy \|\| An energy action changes the value of a energy points of the target, positive or negative \|\| targeted_id, energy_type \|\| Might need a way to put either a number or an algorithm for the amount of change into this field. Also, a single action can have multiple types of energy change (HP/MP/SP) but each one can only go up or down once. So it could increase HP and decrease MP, but not increase MP 10 and decrease MP 5.		\| Energy \|\| An energy action changes the value of a energy points of the target, positive or negative \|\| targeted_id, energy_type \|\| Might need a way to put either a number or an algorithm for the amount of change into this field. Also, a single action can have multiple types of energy change (HP/MP/SP) but each one can only go up or down once. So it could increase HP and decrease MP, but not increase MP 10 and decrease MP 5.
			\|-
			\| Creature actions \|\| Actions that can be taken by a creature \|\| \|\|
			\|-
			\| Character actions \|\| Actions that can be taken by a character \|\| \|\|
	\|}		\|}

Aurora: /* Metadata tables */

2011-10-28T18:59:18Z

Metadata tables

← Older revision		Revision as of 18:59, 28 October 2011
Line 114:		Line 114:
	\| Creator Class \|\| Jobs for creators (stackable) \|\| class_name, permissions		\| Creator Class \|\| Jobs for creators (stackable) \|\| class_name, permissions
	\|-		\|-
	\| ~~Player~~ Races \|\| \|\| ~~race_id~~ (FK to ~~races~~), ~~player race boolean~~, ~~elite player race boolean~~		\| Races \|\| creature groups \|\| racial_group_id (FK to racial groups), player_race (bool), elite_player_race (bool), size_id (FK to size) \|\| stat adjustments covered by racial adjustment table?
	\|-
	~~\| Races \|\| creature groups \|\| racial_group_id~~ (FK to ~~racial groups~~) \|\| stat adjustments covered by racial adjustment table?
	\|-		\|-
	\| Racial group \|\| superclass of races \|\| description		\| Racial group \|\| superclass of races \|\| description
	\|-		\|-
	\| ~~Sizes~~ \|\| different sizes of creatures \|\| size_name, size_order \|\| 1=tiny (bug), 2=small (halfling), 3=medium (elf), 4=large (ogre), 5=huge (dragon)		\| Size \|\| different sizes of creatures \|\| size_name, size_order \|\| 1=tiny (bug), 2=small (halfling), 3=medium (elf), 4=large (ogre), 5=huge (dragon)
	\|-		\|-
	\| Random monster generation parameters \|\| necessary information for generating random monsters \|\|		\| Random monster generation parameters \|\| necessary information for generating random monsters \|\|
Line 128:		Line 126:
	\| Character sort orders \|\| Options for players to sort list of characters \|\| sort column, asc/desc		\| Character sort orders \|\| Options for players to sort list of characters \|\| sort column, asc/desc
	\|-		\|-
	\| Features \|\| Features are options for creatures that can be visible in descriptions of those creatures. These are the things that get set to personalize a character upon character creation, but are also valid for NPC creatures \|\| feature_name, feature_description		\| Features \|\| Features are options for creatures that can be visible in descriptions of those creatures. These are the things that get set to personalize a character upon character creation (and later), but are also valid for NPC creatures \|\| feature_name, feature_description
	\|-		\|-
	\| Languages \|\| \|\| language_name, parent_language \|\| may need more than one parent language to mimic proper language "trees"		\| Languages \|\| \|\| language_name, parent_language \|\| may need more than one parent language to mimic proper language "trees"

Aurora: /* Object tables */

2011-10-28T18:50:53Z

Object tables

← Older revision		Revision as of 18:50, 28 October 2011
Line 64:		Line 64:
	\| Creators \|\| Creators are characters that code the MUD \|\| character_id (FK to characters), creator_class_id (FK to Creator Class), creator_start_date		\| Creators \|\| Creators are characters that code the MUD \|\| character_id (FK to characters), creator_class_id (FK to Creator Class), creator_start_date
	\|-		\|-
	\| Players \|\| Players are the link between characters by the same person. The player is probably not a creature \|\| user_id, password (encrypted?), character_sort_order_id		\| Players \|\| Players are the link between characters by the same person. The player is probably not a creature \|\| user_id, password (encrypted?), character_sort_order_id \|\| Need a method for changing password, recovering password when forgotten. And possibly an encrypted password history table.
	\|-		\|-
	\| Items \|\| Items are non-creature objects\|\| description, obviousness \|\| Unobvious items will not show up in room until searched for. They will show up in player inventories and bags. Depends on capacity of container and weight of object.		\| Items \|\| Items are non-creature objects\|\| description, obviousness \|\| Unobvious items will not show up in room until searched for. They will show up in player inventories and bags. Depends on capacity of container and weight of object.

Aurora: /* Working tables / --> / State tables */

2011-10-28T18:50:13Z

Working tables: --> State tables

← Older revision		Revision as of 18:50, 28 October 2011
Line 179:		Line 179:
	\|}		\|}

	===~~Working~~ tables===		===State tables===
	~~Temp tables to be used while~~ player ~~is logged in~~, ~~dropped after/at reboot~~		Tables that keep the current state of the character/player, to be updated frequently. Chances are anything that can be changed should probably be here
	* Inventory? How to ~~persist, write to more permanent table?~~
	* Status that ~~wears off~~

			* Location - What room is the character in?
			** Inventory - What items is the character holding? Can this be expanded to "what items is the object holding?"--Probably. That way it also covers chests, and in turn, location.
			* Experience/Level
			* Skill Level/% to next level
			* Energy Point Pools
			* Spell List
			* History tables - history of what?
			** Might just use a database with built-in history/records
			* Communication - open issue for privacy.
			** Either everything is logged (and we put up a disclaimer for this) and we have the (restricted) ability to grep through the logs for evidence of real-life crime or inter-player harassment
			** Or we give the player the ability to turn on logging to be sent to us
			** Or should we log all input from a user to be able to recreate bugs?
			** If we do save everything, it has to be seriously restricted and possibly encrypted.

	===Table brainstorming===		===Table brainstorming===

Aurora: /* Interface and code */

2011-10-28T18:27:39Z

Interface and code

@@ Line 25: / Line 25: @@
 #* Web interface a wrapper around all information given, but with traditional telnet interface of many lines coming at you?
 #* Or telnet interface with a text-based browser style? Keep the different windows?
 ==Database(?)==

Aurora: /* Interaction */

2011-10-27T20:39:50Z

Interaction

@@ Line 181: / Line 181: @@
 #* Clearly defined definitions of items and actions. Adding a new item/action must go into one of these groups. Adding a new class rearranges the DB a bit.
 #* Subclasses/Superclasses can be defined to combine/narrow things down. Probably superclasses are more likely, to make things have only one class?
 ==Interaction==

Aurora: /* Metadata tables */

2011-10-27T20:38:51Z

Metadata tables

← Older revision		Revision as of 20:38, 27 October 2011
Line 111:		Line 111:
	\|-		\|-
	\| Features \|\| Features are options for creatures that can be visible in descriptions of those creatures. These are the things that get set to personalize a character upon character creation, but are also valid for NPC creatures \|\| feature_name, feature_description		\| Features \|\| Features are options for creatures that can be visible in descriptions of those creatures. These are the things that get set to personalize a character upon character creation, but are also valid for NPC creatures \|\| feature_name, feature_description
			\|-
			\| Languages \|\| \|\| language_name, parent_language \|\| may need more than one parent language to mimic proper language "trees"
	\|}		\|}

Aurora: /* Object tables */

2011-10-27T20:09:24Z

Object tables

← Older revision		Revision as of 20:09, 27 October 2011
Line 48:		Line 48:
	\| Players \|\| Players are the link between characters by the same person. The player is probably not a creature \|\| user_id, password (encrypted?), character_sort_order_id		\| Players \|\| Players are the link between characters by the same person. The player is probably not a creature \|\| user_id, password (encrypted?), character_sort_order_id
	\|-		\|-
	\| Items \|\| Items are non-creature objects\|\| description, obviousness \|\| Unobvious items will not show up in room until searched for. They will show up in player inventories and bags. Depends on capacity of container.		\| Items \|\| Items are non-creature objects\|\| description, obviousness \|\| Unobvious items will not show up in room until searched for. They will show up in player inventories and bags. Depends on capacity of container and weight of object.
	\|-		\|-
	\| Weapons \|\| Weapons are items that have item_class "wieldable" \|\| item_id, number of hands(limbs) needed, attack power, skill used		\| Weapons \|\| Weapons are items that have item_class "wieldable" \|\| item_id, number of hands(limbs) needed, attack power, skill used

Aurora: /* Metadata tables */

2011-10-27T19:50:54Z

Metadata tables

← Older revision		Revision as of 19:50, 27 October 2011
Line 86:		Line 86:
	\| Item personalization \|\| Items that are different from standard according to the player \|\| item_id (FK to items), character_id (FK to characters), new field name, description		\| Item personalization \|\| Items that are different from standard according to the player \|\| item_id (FK to items), character_id (FK to characters), new field name, description
	\|-		\|-
	\| Item class \|\| Different kinds of items \|\| item_class_name, item_class_description \|\| see [[~~UC_MUD_World_Planning#Items~~\|Items]] for list		\| Item class \|\| Different kinds of items \|\| item_class_name, item_class_description \|\| see [[UC_MUD_Items\|Items]] for list
	\|-		\|-
	\| Guilds \|\| In-game guild list \|\| guild_name, guild_chat_id		\| Guilds \|\| In-game guild list \|\| guild_name, guild_chat_id

Aurora: /* Metadata tables */

2011-10-27T19:50:27Z

Metadata tables

← Older revision		Revision as of 19:50, 27 October 2011
Line 75:		Line 75:
	{\| border=1		{\| border=1
	! Table !! Description !! Columns !! Notes		! Table !! Description !! Columns !! Notes
			\|-
			\| Metadata \|\| Table information \|\| table name, column name, PK_flag, FK_flag, FK_link (FK to metadata_id, self-referential) \|\| Can we have this auto-generate? Based on system tables?
	\|-		\|-
	\| General Rooms \|\| Single source of room description \|\| description columns		\| General Rooms \|\| Single source of room description \|\| description columns
	\|-		\|-
	\| ~~Metadata~~ \|\| ~~Table information~~ \|\| ~~table name~~, ~~column name, PK_flag, FK_flag, FK_link (FK to metadata_id, self-referential) \|\| Can we have this auto-generate? Based on system tables?~~		\| Energy Points \|\| \|\| energy_point_name, description
	\|-		\|-
	\| Status adjustments \|\| Creature adjustments, temporary or permanent \|\| metadata_id, modificatio		\| Status adjustments \|\| Creature adjustments, temporary or permanent \|\| metadata_id, modificatio

UC MUD Code Planning - Revision history

Aurora: /* Action tables */

Aurora: /* Metadata tables */

Aurora: /* Object tables */

Aurora: /* Working tables */ --> /* State tables */

Aurora: /* Interface and code */

Aurora: /* Interaction */

Aurora: /* Metadata tables */

Aurora: /* Object tables */

Aurora: /* Metadata tables */

Aurora: /* Metadata tables */

Aurora: /* Working tables / --> / State tables */