Infoportions - Revision history

VorteX at 11:34, 22 November 2012

2012-11-22T11:34:22Z

2012-07-19T15:45:46Z

2012-07-18T17:23:11Z

2012-07-18T17:22:27Z

2012-07-18T17:21:05Z

2012-07-18T17:20:20Z

2012-07-18T17:19:34Z

2012-07-18T17:19:09Z

2012-07-18T17:18:38Z

2012-07-18T09:16:21Z

← Older revision		Revision as of 15:45, 19 July 2012
Line 7:		Line 7:

	Infoportions could be local or global, can have values attached. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.		Infoportions could be local or global, can have values attached. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.
		+
		+	== Naming conventions ==

	As all infoportions share same name space, some standarts of naming should be followed to avoid collisions.		As all infoportions share same name space, some standarts of naming should be followed to avoid collisions.

@@ Line 44: / Line 44: @@
 Typical usage of infoportions for level design:
-* When having same NPC in two maps (like barkeep in Ziegsturhl tavern), when one is killed, another should be removed too.
+* In some maps, there is two or moreentities representing same NPC (like barkeep in Ziegsturhl tavern), when one is killed, another ones should be removed too.
 * Open doors, activate stuff in another levels.
 * Spawn more enemies when kain kills someone.

@@ Line 43: / Line 43: @@
 * etc.
-Typical usage on infoportions for level design:
+Typical usage of infoportions for level design:
 * When having same NPC in two maps (like barkeep in Ziegsturhl tavern), when one is killed, another should be removed too.
 * Open doors, activate stuff in another levels.

@@ Line 6: / Line 6: @@
   w1m3_crypt1button_p // button 1 was pressed in light crypt
-Infoportions could be local or global. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.
+Infoportions could be local or global, can have values attached. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.
 As all infoportions share same name space, some standarts of naming should be followed to avoid collisions.
@@ Line 14: / Line 14: @@
 * Kain's eventual comments (snow, rain etc.) are prefixed by "comment_".
 * Global infoportions always prefixed by #
 == Usage ==

@@ Line 8: / Line 8: @@
 Infoportions could be local or global. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.
-As all infoportions share same name space, there is some standarts of naming to get rid of collisions.
+As all infoportions share same name space, some standarts of naming should be followed to avoid collisions.
 * Inventory-related infoportions are prefixed by "inv_"

← Older revision		Revision as of 17:19, 18 July 2012
Line 1:		Line 1:
−	Pieces of information (strings) storing player's (or game) progress, achievements and game stats. Used to identify if player ~~was~~ performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.)~~. Infoportions store data across levels~~.	+	Pieces of information (strings) storing player's (or game) progress, achievements and game stats. Used to identify if player performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.).

	Example player infoportions array:		Example player infoportions array:

← Older revision		Revision as of 17:18, 18 July 2012
Line 1:		Line 1:
−	Pieces of information (strings) storing player's (or game) progress. Used to identify if player was performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.). Infoportions store data across levels ~~and also used for game stats and achievements~~.	+	Pieces of information (strings) storing player's (or game) progress, achievements and game stats. Used to identify if player was performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.). Infoportions store data across levels.

	Example player infoportions array:		Example player infoportions array:

← Older revision		Revision as of 09:16, 18 July 2012
Line 1:		Line 1:
−	Pieces of information storing player's (or game) progress. Used to identify if player was performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.). Infoportions store data across levels and also used for game stats and achievements.	+	Pieces of information (strings) storing player's (or game) progress. Used to identify if player was performed some action (touched some trigger, killed monster, activated batmark, checked out monologue mark etc.). Infoportions store data across levels and also used for game stats and achievements.
		+
		+	Example player infoportions array:
		+	comment_sun // sun monologue (in the light of the sun i have no comfort...) was executed
		+	comment_rain // rain monologue was executed
		+	w1m3_crypt1button_p // button 1 was pressed in light crypt

	Infoportions could be local or global. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.		Infoportions could be local or global. Local infoportions belongs to player/npc, while global belongs to game and being active on all players.