Stoner
Joined: Aug 02, 2003
|
  Posted:
Apr 07, 2004 - 17:05 |
|
In the tournament I created with a bunch of friends, one of the coaches witdrew his team from the group to make a new one.
This causes problems with the current replacement implementation. As there is no team in the tournament for his new team to replace, I'm unable to add his new team back into the tournament.
Would it be possible to implement the replacement feature to where you replace the tournament slot instead of an actual team, so I could for example replace slot F with a new team?
If this is not the place for this, please point me in the right direction.
Thanks! |
|
|
Twahn
Joined: Aug 02, 2003
|
  Posted:
Apr 08, 2004 - 00:10 |
|
If you add your friend's new team to the Group where your tournament is located, you can then exchange his teams freely. If your friend has already removed his team from the Group the nhe's stuffed your tournament, which is what sounds like has happened.
The answer is simply for his to replace his team before leaving the tournament... |
_________________ Founder of the Southern Wastes League
DonTwahn's Dungeon = Cheap Miniatures! Check it out... |
|
Stoner
Joined: Aug 02, 2003
|
  Posted:
Apr 08, 2004 - 04:37 |
|
I'm aware that this is a bad situation. I just believe that it is one that could possibly be programmaticly fixed. |
|
|
Twahn
Joined: Aug 02, 2003
|
  Posted:
Apr 08, 2004 - 05:00 |
|
It's so easy to avoid the problem though, that it would hardly be worth the effort in fixing surely... |
_________________ Founder of the Southern Wastes League
DonTwahn's Dungeon = Cheap Miniatures! Check it out... |
|
Stoner
Joined: Aug 02, 2003
|
  Posted:
Apr 08, 2004 - 14:38 |
|
It should always be assumed that we(the users) can and will do anything. With a simple tweak to the code, the issue can be prevented. I'm now aware of the problem, but what about other people that haven't run a tournament.
I'm not saying it's a huge problem, just that it is probably fairly easy to fix, and in the interest of tournament integrity and user friendliness, it probably shoud be fixed. |
|
|