Community Contest 4: Minigame Script - Revision history

Sunjammer: Adding category

2011-08-31T20:43:19Z

Adding category

Sunjammer: /* Judges' Comments */

2010-11-15T23:08:55Z

‎Judges' Comments

Sunjammer: /* Judges' Comments */

2010-11-15T23:07:08Z

‎Judges' Comments

Sunjammer: /* Judges' Comments */

2010-11-15T22:57:22Z

‎Judges' Comments

Sunjammer: /* Judges' Comments */

2010-11-15T22:41:01Z

‎Judges' Comments

Sunjammer: /* Judges' Comments */

2010-11-15T22:40:16Z

‎Judges' Comments

TimelordDC at 19:46, 15 November 2010

2010-11-15T19:46:43Z

TimelordDC: /* Nug Chase by Bloodsong */

2010-11-15T19:45:33Z

‎Nug Chase by Bloodsong

TimelordDC: /* The Cranky Harem by TimelordDC */

2010-11-15T19:45:19Z

‎The Cranky Harem by TimelordDC

TimelordDC: /* The Doors of Death by Lobo */

2010-11-15T19:45:06Z

‎The Doors of Death by Lobo

← Older revision		Revision as of 20:43, 31 August 2011
Line 1:		Line 1:
		+	[[Category:Community Contest]]
	[[File:Community_Contest_back.jpg\|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg\|link=http://social.bioware.com/group/2535/&v=discussions]]		[[File:Community_Contest_back.jpg\|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg\|link=http://social.bioware.com/group/2535/&v=discussions]]

@@ Line 200: / Line 200: @@
+     }
-[[User:Sunjammer|Sunjammer]]: I didn't judge this competition but I think it is necessary to mention a larger issues which has been overlooked. In both examples, assuming the logic is correct, the majority of the conditional code is superfluous. Specifically since the AND condition can only ever be true in when <code>i == 0</code> testing the condition in all subsequent cases is redundant. Refactored the code should look more like this:
+[[User:Sunjammer|Sunjammer]]: I didn't judge this competition but I think it is necessary to mention a larger issues which has been overlooked. In both examples, assuming the logic is correct, the majority of the conditional code is superfluous. Specifically since the AND condition can only ever be true in when <code>i == 0</code> testing the condition in all subsequent cases is redundant. Refactored, the code should look more like this:
 <dascript>
@@ Line 214: / Line 214: @@
+     }
 </dascript>
-Although the above code appears more verbose it is more efficient and it should be more easily understood (even without the comments) and therefore is easier to maintain. There is however still a question mark over the first flag as it may be unnecessary to set it where <code>bFullReset</code> is false. If this is the case the following variation should be used:
+Although the above code appears more verbose it is more efficient and it should be more easily understood (even without the comments) and therefore is easier to maintain.
 <dascript>

@@ Line 214: / Line 214: @@
+     }
 </dascript>
-Although the above code appears more verbose it is more efficient and it should be more easily understood (even without the comments) and therefore is easier to maintain.
+Although the above code appears more verbose it is more efficient and it should be more easily understood (even without the comments) and therefore is easier to maintain. There is however still a question mark over the first flag as it may be unnecessary to set it where <code>bFullReset</code> is false. If this is the case the following variation should be used:
 == Nug Chase by Bloodsong - Best Newcomer ==

@@ Line 206: / Line 206: @@
      // resetting first flag is conditional: a partial reset does not reset the first flag
-     WR_SetPlotFlag(sPlot, 0, !bFullReset)
+     WR_SetPlotFlag(sPlot, 0, !bFullReset);
      // resetting subsequent flags is unconditional: they are always reset

@@ Line 200: / Line 200: @@
+     }
-[[User:Sunjammer|Sunjammer]]: I didn't judge this competition but I think it is necessary to mention a larger issues which has been overlooked. In both examples, assuming the logic is correct, the majority of the conditional is superfluous. Specifically since the AND condition can only ever be true in when <code>i == 0</code> testing the condition in all subsequent cases is redundant. Refactored the code should look more like this:
+[[User:Sunjammer|Sunjammer]]: I didn't judge this competition but I think it is necessary to mention a larger issues which has been overlooked. In both examples, assuming the logic is correct, the majority of the conditional code is superfluous. Specifically since the AND condition can only ever be true in when <code>i == 0</code> testing the condition in all subsequent cases is redundant. Refactored the code should look more like this:
 <dascript>

@@ Line 199: / Line 199: @@
          WR_SetPlotFlag(sPlot, i, bResetPlot);
+     }
 == Nug Chase by Bloodsong - Best Newcomer ==

@@ Line 101: / Line 101: @@
 + Came with an expansive ReadMe file.
-* '''[http://www.dragonagenexus.com/downloads/file.php?id=1859 Nug Chase on Dragon Age Nexus]'''
+== The Cranky Harem by TimelordDC - 2nd Place==
-A simple action-oriented mini-game for players of any level.  Granny Rockbottom's prize Racing Nug has escaped his pen, and you need to catch him.  To do this, you need to click on the nug and get close enough to initate a conversation.  If you are successful, you catch the pesky nug.  If not, hilarity ensues.  :X
+* '''[http://www.dragonagenexus.com/downloads/file.php?id=1869 Dragon Age Nexus Project Page]'''
-Includes a custom Nug Wallows area/level, and a convoluted conversation tree with the NPC.  Rewards are small gifts, some XP, and possibly a small amount of cash.  Documentation for customizing also included.
+This module offers a customizable way of creating a single-area puzzle and is based on 2 classic chess problems - the 8-queen problem where you have to place 8 queen on a chess board so they don't attack each other and the queen-domination problem where you have to place the minimum number of queens in order to attack all squares (the minimum number has been relaxed for this game but you can change it)
-[[File:NugChase1.jpg|400px|Nug Chase Promo]]
+There are also 5 different board sizes - 4 through 8, resulting in a total of 25 possible games.
-Please report any file/installation problems here:
+Some sample scenarios to present the game in a non-chess fashion:
-* '''[http://social.bioware.com/project/3512/discussion/2597/20416/#post_20416 Nug Chase Project]'''
+# The Cranky Harem as released on DANexus
 === Judges' Comments ===
@@ Line 118: / Line 129: @@
 Helekanalaith
-- Was unable to review the code because the B2B file was empty?
+- An empty SWITCH-structure encased in an empty ELSE-structure's brackets serves no purpose. Probably code left behind while performing a clean-up?
 + Came with an expansive ReadMe file.
-Most fun to play and was the only module that featured voice acting. Nice level design as well
 == The Doors of Death by Lobo - 3rd Place==
@@ Line 169: / Line 189: @@
              WR_SetPlotFlag(sPlot, i, FALSE);
+         }
          i++;
+     }
@@ Line 180: / Line 199: @@
          WR_SetPlotFlag(sPlot, i, bResetPlot);
+     }
 == Assembly by mikemike37 ==
@@ Line 218: / Line 261: @@
 Creating separate libraries for your constants and functions is always handy. You never know if you ever plan on expanding your scripts in the future.

@@ Line 124: / Line 124: @@
 Most fun to play and was the only module that featured voice acting. Nice level design as well
-== The Doors of Death by Lobo ==
+== The Doors of Death by Lobo - 3rd Place==
 * '''[http://www.dragonagenexus.com/downloads/file.php?id=1860 The Doors of Death on Dragon Age Nexus]'''