Site Ideas
18 May 08
18 May 08
If a clan challenge isn't accepted, rejected or resent with changes by a certain period of time, then the challenge should automatically default to being accepted and started. The vacation settings and unavailability would protect against getting challenges, but then there wouldn't be lingering challenges that haven't been accepted or rejected. Why should it fall to the challenger to withdraw them if they aren't accepted? Also, the timing could be very bad for old challenges that are on the books. Ratings might have changed, or even membership in the clan might have changed.
19 May 08
Originally posted by coquetteDon't agree. Not at all.
If a clan challenge isn't accepted, rejected or resent with changes by a certain period of time, then the challenge should automatically default to being accepted and started. The vacation settings and unavailability would protect against getting challenges, but then there wouldn't be lingering challenges that haven't been accepted or rejected. Why should i ...[text shortened]... on the books. Ratings might have changed, or even membership in the clan might have changed.
Every challenge must be accepted by both parties in order to be started.
19 May 08
Originally posted by coquetteI should probably stay out of this thread as you've sent me a challenge that I haven't looked at yet, but I also disagree. Reason being that it would be very easy for me to send out thousands of challenges with a 1/0 timeout to all those inactive clans and then start reaping the points.
If a clan challenge isn't accepted, rejected or resent with changes by a certain period of time, then the challenge should automatically default to being accepted and started. The vacation settings and unavailability would protect against getting challenges, but then there wouldn't be lingering challenges that haven't been accepted or rejected. Why should i ...[text shortened]... on the books. Ratings might have changed, or even membership in the clan might have changed.
19 May 08
Originally posted by coquetteI completely disagree with this ideas... (for reasons that Lukerik says 2 posts above)
If a clan challenge isn't accepted, rejected or resent with changes by a certain period of time, then the challenge should automatically default to being accepted and started. The vacation settings and unavailability would protect against getting challenges, but then there wouldn't be lingering challenges that haven't been accepted or rejected. Why should i ...[text shortened]... on the books. Ratings might have changed, or even membership in the clan might have changed.
...actually, I agree with the end bit, and so I propose that unaccepted challenges should instead be automatically rejected after a mandatory period of time. A week?