1 |
And forcing a player to resign because of cpu usage wouldnt work too much either. Have to ask yourself these questions (as resign cannot be undone):
|
1 |
And forcing a player to resign because of cpu usage wouldnt work too much either. Have to ask yourself these questions (as resign cannot be undone):
|
2 |
\n
|
2 |
\n
|
3 |
1.) Can we be absolutely sure this person cant handle the game?
|
3 |
1.) Can we be absolutely sure this person cant handle the game?
|
4 |
2.) Is high cpu usage temporary spike?
|
4 |
2.) Is high cpu usage temporary spike?
|
5 |
3.) Is this person holding up the game severely enough to warrant a forced resign?
|
5 |
3.) Is this person holding up the game severely enough to warrant a forced resign?
|
6 |
4.) Can this be done with a gadget?
|
6 |
4.) Can this be done with a gadget?
|
7 |
5.) What is the tolerable level of slowdown before the gadget forces us to spectate?
|
7 |
5.) What is the tolerable level of slowdown before the gadget forces us to spectate?
|
8 |
\n
|
8 |
\n
|
9 |
Remember:
It
will
be
highly
frustrating
for
those
with
a
false
positive
(
eg:
was
a
temporary
spike
in
useage)
to
be
forced
to
spectate.
Is
this
frustration
of
programing
a
perfect
system
of
slowdown
detection
worth
the
frustration
it
may
cause
for
all
people?
|
9 |
Remember:
It
will
be
highly
frustrating
for
those
with
a
false
positive
(
eg:
was
a
temporary
spike
in
useage)
to
be
forced
to
spectate.
Is
this
worth
the
frustration
it
may
cause
for
all
people?
|