Ladle 19
Moderator: Light
That's why I would advice:owned wrote:Do you seriously want to make it hard for them? If they want, they could just have VcL forfeit and the players in it temporarily join Nw. I'd say to just change the challenge board.
Teams shouldn't be changed at all (except for forfeiting) after the beginning of challenge board creation
*AND* : Players that were signed up for an forfeiting team, will not be allowed to join another team...
EDIT: I'll give another suggestion. ditch the guidelines, make strict rules
Crazy Tron Addict since : October 2002 <--- Beat that 

So, by joining NW, VCL causes them to forfeit too, then KoD plays TR. How about that? Well, not for this ladle, but maybe something like that would work in the future.
I don't know. I don't think it's that big of a deal since we have a lot of teams this time. And as the amount of teams grows, this problem will grow too, but I don't really have any suggestions on how to deal with it.

I don't know. I don't think it's that big of a deal since we have a lot of teams this time. And as the amount of teams grows, this problem will grow too, but I don't really have any suggestions on how to deal with it.

Well as of now, (considering how constructive you guys were in the rules topic) there is no rule against VcL forfeiting, Nw changing its name, or Nw taking in new players. Since there is none, they can do it. If you feel like making those rules after the ladle then fine. But as of now, nope.freako wrote:That's why I would advice:owned wrote:Do you seriously want to make it hard for them? If they want, they could just have VcL forfeit and the players in it temporarily join Nw. I'd say to just change the challenge board.
Teams shouldn't be changed at all (except for forfeiting) after the beginning of challenge board creation
*AND* : Players that were signed up for an forfeiting team, will not be allowed to join another team...
EDIT: I'll give another suggestion. ditch the guidelines, make strict rules
- compguygene
- Adjust Outside Corner Grinder
- Posts: 2346
- Joined: Thu Aug 21, 2008 12:09 pm
- Location: Cleveland, Ohio
- Contact:
We could debate this for the next two years...but before a challenge board is put up for the next ladle, a rule should be decided. Perhaps clans that don't quite have enough fortress players could be advised of this rule, as many don't follow this forum.
Just my 2 cents!
Just my 2 cents!

Armagetron: It's a video game that people should just play and enjoy 
https://bit.ly/2KBGYjvCheck out the simple site about TheServerPharm

https://bit.ly/2KBGYjvCheck out the simple site about TheServerPharm
look closely to the challenge board...Well as of now, (considering how constructive you guys were in the rules topic) there is no rule against VcL forfeiting, Nw changing its name, or Nw taking in new players. Since there is none, they can do it. If you feel like making those rules after the ladle then fine. But as of now, nope.
When I look to it, I see 2 different teams

And not 1 combined team...
Seems that they forgot to add there players

Crazy Tron Addict since : October 2002 <--- Beat that 

That would mean a team would get a bye in the second round and that makes no sense whatsoever to me.sinewav wrote:So, by joining NW, VCL causes them to forfeit too, then KoD plays TR. How about that? Well, not for this ladle, but maybe something like that would work in the future.
winner of: Spoon, 3rd, 6th, 9th, 11th, 18th, 19th, 33rd, 34th and 48th Ladle.
Retired since 07/2012
Retired since 07/2012
Thanks Conc, for walking me through all that whacky wiki-ness to add the ID's
to the square dance on sunday. BTW whoever thought of asking the
question about "what color the bike is" was pure genius. Conc was right
on in guessing that the gold/yellow bike was actually red.

to the square dance on sunday. BTW whoever thought of asking the
question about "what color the bike is" was pure genius. Conc was right
on in guessing that the gold/yellow bike was actually red.


"Day after day, alone on a hill, the man with a foolish grin is keeping perfectly still" --- Billy Shears
- pike
- Round Winner
- Posts: 397
- Joined: Thu Feb 28, 2008 6:53 pm
- Location: where polar bears walk the streets
/me agreesConcord wrote:heh
that wiki captcha question is ridiculous, we should look into a different spot for the challenge board if to add your team you need to know that the bike was red.
When I was signing in, I just typed every color name that came to my mind. It worked, but I guess this is not the best way to find the correct answer

- 2020
- Outside Corner Grinder
- Posts: 1322
- Joined: Thu Dec 29, 2005 9:21 pm
- Location: the present, finally
aha...
yes...
peeps have noticed that players can actually bump around teams throughout the competition...
with current settings
even if we lock a team into a bracket
the actual content of that team is not locked
and i don't see why we have to decide on rules about this
until the software to secure it is made available
that is
we don't have to think about these kinds of rules yet
so
let people bump around
if teams who are present are willing to shift who is playing in their team
let them
+
i know my team won't
yes...
peeps have noticed that players can actually bump around teams throughout the competition...
with current settings
even if we lock a team into a bracket
the actual content of that team is not locked
and i don't see why we have to decide on rules about this
until the software to secure it is made available
that is
we don't have to think about these kinds of rules yet
so
let people bump around
if teams who are present are willing to shift who is playing in their team
let them
+
i know my team won't
hold the line
Recordings, a whole lot of em. Done as usual because 2020 forgot to tell me his camera config, and I forgot to guess it. Sorry. I'll try the editing solution.
final_kod_vs_plus.aarec
semi2_kod_vs_ct.aarec
semi2_x_vs_+.aarec
quarter_ww_vs_plus.aarec
quarter_x_vs_id.aarec
octa1_ds_vs_+.aarec
octa2_ww_vs_manic.aarec
final_kod_vs_plus.aarec
semi2_kod_vs_ct.aarec
semi2_x_vs_+.aarec
quarter_ww_vs_plus.aarec
quarter_x_vs_id.aarec
octa1_ds_vs_+.aarec
octa2_ww_vs_manic.aarec