Key Information

Register
Submit
The challenge is finished.

Challenge Overview

$2000 prize will be distributed among top 10 players, each player will get = earned points / total points by top 10 players.

The goal of the challenge is to invite Topcoder community members to play Dynamakr game in Verigames gaming community website.

Read more about Verigames in this page https://www.verigames.org/about-us

Challenge Task Overview

The goal of this challenge is to play the game and report any issues in the game that affect game playing.

Get Started

  1. - Register new account http://verigames.com/

  2. - Start playing http://dynamakr.verigames.com

  3. - Try to complete as many levels as you can!

Playing The Game FAQ

  • - How to get started : Is there an instruction ? Videos ? FAQ ? that we can share with competitors

  • - What's number of tutorials in the game ?

    • - The tutorial system is integrated with the game, and presents most of it's material within the first few game plays

  • - How many levels in the game ?

    • - Dynamakr doesn't have a "level" system. The player is working with multiple game-levels worth of data on the screen at one time.

  • - Do you have specific scenarios you want to share with competitors when playing the game ?

    • -  A Dynamakr player has a goal to generate X amount of energy (this number is shown in the 'energy' panel at the top of the screen). When the player has generated this much energy, the 'Start Dynamo' button appears. When they press that, the game scores the user's work and awards Energy points. It is this energy score that shows how much work a player has done over time. Behind the scenes, a score of 100 energy points is equivalent to adding 100 new arcs to our connected graph about the program under analysis.

    • - For any player, their current goal is to produce enough energy to fill the "energy" bar at the top of the screen. Once they do, they can move onto the Dynamo portion of the game. For new players, the energy threshold - the amount needed to fill the energy bar - is low, but the more they play, the larger the amount of energy they need to generate in order to fill the bar. So the game becomes more challenging as time goes by for a given player. Because the nature of the data isn't certain, it is possible that one user is able to fill the energy bar faster than another player, even if they are both at the same experience level. This is due to the fact that some game instances happen to contribute more arcs to our hidden directed-graph, than other game instances.  So for a beginner player, it could take less than a minute to fill the energy bar, whereas  for a more experienced player it can take several minutes to fill the bar.

  • - What browsers does the game support ? We will instruct competitors to use specific browsers for testing.

    • - Players can use Internet Explorer and Firefox, both of which will require the players to install the Unity Plugin. Other browsers that support the Unity Plugin will also work.

    • - Dynamakr is also available for Google Chrome, but this version of the game does not use the Unity Plugin (it uses Javascript/WebGL), BUT is prone to Memory problems. We created this version using a relatively new publish-option in Unity, so it can be unstable. We recommend using other browsers instead of Chrome.

  • - Where can I see my progress in the game ?

Contest Guidelines

The guidelines for this contest are given below:

  • - We want you to play as many levels as possible.

  • - We want you to capture screenshots of impediments to your continued play.  A bug is an obvious impediment, but seeing something that really doesn't make sense, or is really confusing, etc, is another type of impediment and we want to know about it.

  • - As issues are identified they need to be logged in JIRA.

  • - Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.

  • - Screenshots should be included when reporting any impediment or bug.

  • - First competitor to find an issue gets credit, duplicates will not be counted.

  • - Reviewer will accept, reject or mark the issues as duplicate.

Important Notice

You must also be the first person to report the issue and submit it while submission phase is open.  JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.

Bug Report Format

For each report of a limitation or bug, we need the following information:

  • - Title

  • - Body of the JIRA should contain the following :

    • - URL

    • - Steps to reproduce, including any needed information

    • - Screen shots (if applicable)

    • - Current results

    • - Suggested fix (if applicable)

    • - OS/Browser version

Important Notice

  • - If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.

  • - If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates and you will lose 1 point for each duplicate reported bug.

Ticket Logging

You will log your tickets here: https://apps.topcoder.com/bugs/browse/CSFV and when creating a bug you MUST select the "Dynamakr Bug Hunt" Bugs will not be counted if a selection is not made.

Scoring

The Scoring guidelines followed for the contest are given below:

  • - Your score in the scoring leaderboard in this page during the challenge submission phase dates.

  • - Issues will be classified via points system :

    • - 200 points for valid reported functionality/impediment bug

    • - 100 points for valid reported UI bug.

  • - Your final score is your : leaderboard score + issues points

  • - $2000 prize will be distributed among top 10 players, each player will get = earned points / total points by top 10 players.

Important Notice

If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not.

 


 



Final Submission Guidelines

Submission Deliverables

You will submit the following :

  • - Text file contains your verigames.com username.

  • - You don’t need to submit what bugs you reported, we will use your topcoder handle to find the issues you reported.

Final Submission

  • - For each member, the final submission should be uploaded to the Online Review Tool.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30051485