Closed GoogleCodeExporter closed 9 years ago
I think the !end command should be kept as it is. It is after all used when the
admin
of the game needs or will end the game, unless this method is made optional.
Original comment by luc...@live.com
on 7 Nov 2008 at 5:15
Making the !from command usable ingame is easy but as of right now the pings
wouldn't
update if the !ping command was usable ingame because GHost++ stops soliciting
pings
from players once the game has loaded. I will have to check if Warcraft 3
permits
pings once the game has loaded and if so I don't have a problem with making the
!ping
command usable ingame.
I won't be adding pings to specific players because the !ping command already
takes
an argument (the maximum allowed ping - i.e. kick all players with a higher
ping). I
don't intend to add a player specific !from command either.
Most of the battle.net commands that affect the current game should already be
restricted when the game is locked (e.g. the slot modification commands). I
decided
not to restrict the !end and !unhost commands to reduce the possibility of a
lobby or
game being stuck open with nobody able to close them. I also won't be adding a
vote
feature to the !end command.
I won't be adding multiple game owners. You may be able to accomplish some of
what
you want when I rewrite the admin system to included access levels.
Original comment by hogantp
on 7 Nov 2008 at 5:17
[deleted comment]
Is it possible to include the !from and !ping into the output when doing !check
on a player?
Original comment by MentalMu...@gmail.com
on 7 Nov 2008 at 11:32
Sure, that sounds reasonable.
Original comment by hogantp
on 7 Nov 2008 at 4:14
Original comment by hogantp
on 10 Nov 2008 at 5:35
Done (r26). Some of the requested features were not added because I do not
intend to
add them. See my previous comments on this issue for more information.
Original comment by hogantp
on 10 Nov 2008 at 6:34
Original issue reported on code.google.com by
MentalMu...@gmail.com
on 4 Nov 2008 at 3:30