Challenges system

[GoogleCodeExporter]

Actually, there is no challenge system yet in eBattles.
But this is a feature I am working on adding.
I still need to work on the details before I can implement it.

Here is a list of rules that I sketched for the challenge system.
1. One team/player decides to challenge another team, providing both teams are 
on the same ladder and that the first team is within the correct number of 
ranks/points which allow him to challenge the other, then he may do so by 
clicking the "Challenge!" button on the ladder page.
This brings him to the "Challenge request" page, where he sets a date/time, and 
click on "Post Challenge!" button.
2. Once a challenge is posted, the team challenged is automatically sent an 
email/pm informing him of the challenge.
He then has a certain number of hours or days to accept the challenge request.
If the request is not accepted within that time, it is automatically removed 
from the system.
3. A team can access its challenges in the "Challenges" tab of the team's page.
This page will display a list of accepted challenges, and of pending 
challenges. 
4. The team that has been challenged can click on the pending challenge link.
This page will use the e107 comment system so challenger and challengee can 
discuss the date/time for the match.
The challenger can change the date/time, the challengee can Accept/Decline.
5. Accepted challenges are fully scheduled, and can be shown in calendar.
The accepted challenge has to be reported within a certain amount of time, or 
the challengee will receive an automatic forfeit loss.
If someone does not show up, the other can submit a win.
6. You can decline up to x challenges in a week.

Ladder Admin:
1. The number of ranks/points a team can challenge above themselves and the 
number of hours or days one has to accept a challenge is defined in the admin 
control panel.
It can be changed by an admin at any time.
2. The number of challenges you can decline.

Original issue reported on code.google.com by frederic...@gmail.com on 9 Jul 2010 at 3:44

[GoogleCodeExporter]

Original comment by frederic...@gmail.com on 22 Jul 2010 at 9:50

• Added labels: Milestone-Release1.0, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Version 0.8.5 (r257)
Features:
. Added "Team Challenges system"
  . Now challenge system can be used in team ladders.
  . Any player of a team can challenge another team.
  . Any player of the challenge team can confirm the challenge.

- Version 0.8.4 (r254)
Features:
. Added "Player Challenges system"
  . A player (the challenger) can challenge another player (the challenged) in the same ladder.
  . To request a challenge, 
    - the challenger selects a player in the ladder and clicks on "Challenge player"
    - on the next page, the challenger selects a number of dates/times (now hardcoded to 3) and can leave a comment, then click "Send challenge".
    - A PM is sent to the challenged player.
    - The challenge appears in the challenger/challenged "My profile" page and in the event's page.
  . The challenger can "Withdraw" the challenge
  . The challenged can "Confirm" the challenge by accepting or declining it.
    . He can select one of the dates proposed by the challenger, and click "Accept"
    . He can click "Decline"
  . The confirmed challenge becomes a scheduled match. It can be played, and reported by either players.

  . Limitations (for now):
    . No support for Team challenges yet.
    . Only 1 option: Events admin can enable/disable challenges
  . Plan:
    . Add team challenges support
    . Add more options
      - How many simultaneous challenges allowed
      - Dates options
        - How many dates required
        - Minimum delay between request and challenge date
      - Points removed for declining challenge
      - Challenge expiration
        - Allow challenge to expire
        - Hours to expire after
        - Penalty for not accepting before expiration
        - Bonus for challenger
        ...?

Original comment by frederic...@gmail.com on 30 Mar 2011 at 9:23

• Changed state: Started