Register
Submit a solution
The challenge is finished.

Challenge Overview

To be eligible for prize money you must complete at least 20 levels, we have $2k in prizes, each member will get prize = member collected points / total points collected by all members.

The goal of the challenge is to invite Topcoder community members to play Paradox 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 paradox.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

    • - Instructions:

      • - Goal: eliminate as many conflicts as possible.

      • - Constraints with at least one matched edge (when the color of variable matches the line that connects it to the constraint) are solved, otherwise they are marked as conflicts.

      • - Left click+drag to paint variables.

      • - Change paintbrushes by selecting a new paintbrush (left click) on the right menu.

      • - +/- keyboard keys zoom in/out.

      • - Arrow keys or right click+drag to pan the level.

      • - Ctrl+Z to undo the last paint action.

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

    • 18 tutorials.

  • - How many levels in the game ?

    • We just put a new batch of 128 levels into the game (and removed the older batch), not counting tutorials.

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

    • They will automatically get the levels (hopefully).

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

    • Any Flash-enabled browser will work.

  • - 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 "Paradox Bugs" Bugs will not be counted if a selection is not made.

Scoring

The Scoring guidelines followed for the contest are given below:

  • - Issues will be classified via points system :

    • - 5 point for completing a level.

    • - 4 points for valid reported functionality/impediment bug

    • - 2 points for valid reported UI bug.

  • - To be eligible for prize money you must complete at least 20 levels, we have $2k in prizes, each member will get prize = member collected points / total points collected by all members. Note that we are limiting higher prize for each member to $400. 

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

ID: 30051469