Page 1 2
Go ![]() | New ![]() | Find ![]() | Notify ![]() | Tools ![]() | Reply ![]() | |
| Peregrine |
Could such a "switch" be abused by people who aren't playing in the head ball match? | |||
|
| Treasurer |
Such a switch, whether physical or console-based, would probably disable itself after activation; to avoid in-game interruptions. | |||
|
Lamur![]() |
I don't think it matters what shape the "switch" takes. (it might be wise hoever to stay true to the command formula in place right now, ie votekick, mute, ban, ect.) i also don't think that you will have a hard time educating the public; votekick is a great example. In about a week of implemintation votekick was known to nearly 90 percent of the lca goers. In two weeks time people got so comfortable with it that they began searching for ways to exploit it. the main task ahead of you, aside from the coding, is determening the circumstances under which "switch" is neccessary and unneccessary. it looks like there are two options: 1. automatic: switch is done automatically to suit the number of people. 2. manual (more "democratic" of the two) n = number of people on server t1 = time elapsed since last activation of switchUp t2 = time elapsed since last activation of switchDown "switchUp = true" if "t1 != 5 mins" & "n-1 = voteyes" "switchDown = true" if "t2 != 5 mins" & "n = voteyes" (this will also ensure that the people that know about the switch will tell others about it) | |||
|
| Peregrine |
I must say Shady, I am impressed. And the command "switch" sounds like a better idea than the physical one, as well as easier to create I assume. | |||
|
| Powered by Social Strata | Page 1 2 |
| Please Wait. Your request is being processed... |
|
© Low Caliber Club 2002-4


