Loading...
  OR  Zero-K Name:    Password:   

Rage post - Everyone's admin

31 posts, 2202 views
Post comment
Filter:    Player:  
Page of 2 (31 records)
sort
Duno why, dunno how, but ATM everyone has admin rights. That mean every one can change map, kick anyone, exit game forcestart etc without votes. Nice screenshot from lobby here: (ban swappan! lol)

+2 / -0

11 years ago
Very fun. I demand permanent admin rights. :)
+0 / -0
Skasi
11 years ago
That's not "being an admin". Being an admin means you got a silly blue uniform on your little icon when others view you via ZKL. My guess is rights needed are messed up. Check out !helpall. It's probably either that, or a Springie bug.
+0 / -0
11 years ago
When doing !helpall it lists commands up to lvl 4.
+0 / -0
11 years ago
Lol right now everyone can kick everyone without vote
there is a kick fight between sfireman and hower :D
+0 / -0
11 years ago
Seems servers restarted itselves/were restarted, and bug is fixed.
+0 / -0
11 years ago
But now using '"!kick'' does nothing, it just says u dont have rights to execute !kick. U have to do !votekick instead. Works with everythin, needs !votemap , !voteresign etc.
+0 / -0


11 years ago
Silly dev noobs, someone must stay without commit rights!
+0 / -3
I don't like it. The shorter orders where better and they also worked for admins. So why change to long orders now? (A question for KingRaptor if he read this)
+1 / -0
DErankMagman, the dev always accidentally kick or exit game because all user use exactly same command that dev use: !kick and !exit

So, all user will now use !votekick and !voteexit to prevent more incident, while !kick and !exit became force-kick/exit command. I think if you are the room boss you will have !kick and !exit too.
+2 / -1
Yeah its much better if adminoobs don't risk kicking or exiting a game because they just imitate some random player.

Choosing to keep the short !kick command for the user/vote kick and having !forcekick (or !adminkick or whatever) would have been far more logical than having !kick remain the admin-only version of the command, because it would have definitely removed the potential of admin mistake, but hey... in a few month we can hope admins will have learned that they have to use !voteexit, no user will continue to issue !exit commands, so we can hope admins imitating players after a failed vote will no longer be a source of problem. Only a few remnants of old reflexes will occasionally spoil a game... I guess asking for more is too much.
+5 / -0


11 years ago
Has the game and lobby been updated to take this change into consideration for buttons that send springie commands? I haven't had a chance to check yet.
+0 / -0
//Edit

Lol I just read BRrank[V]sheep post. Didnt notice he had same idea as me :D
______________________________________________________________________________

Whats the point of disallowing USERS to use !kick command? Those are the admins who made mistakes. Admins still can acicdenatly kick someone by using !kick, jsut becasue they are used to this command.
I think better soulluion would be making !kick command work as VOTE only, and changing !votekick to !forcekick. OFC !forcekick would be only for admins, and kick instantly.

Same with !map, !resign, !exit etc.

+0 / -0


11 years ago
A "force" prefix would have ambiguous semantics, see already existing forcestart and voteforcestart commands. Would they become forcestart (instead of voteforcestart) and forceforcestart then? :P

Better just rebrand it into force lightning, then.
+5 / -1
11 years ago
I second Anarchid's idea.

I also submit: We need lightsabers.
+0 / -0
Use ''admin'' prefix then. That would be !adminkick. And !adminfrocestart. Or simply add ''a'' before commands, which stands for ''admin'' too. (!akick ; !aforcestart; !aexit etc).

There are many capabilities. Forcing players to use !vote[something] was the worst option devs could chose.
+2 / -0


11 years ago
Get an account and cast your vote! http://code.google.com/p/zero-k/source/detail?r=11751
+1 / -0
Anarchid's point that using force prefix would be ambiguous is a good point.



Just let me point a few things, to demonstrate that confusion is probably a design goal, or that its just the result of lack of design leading to absence of consistency and thus confusion.

quote:

public void ComForce(TasSayEventArgs e, string[] words)
{
if (spring.IsRunning)
{
SayBattle("forcing game start by " + e.UserName);
spring.ForceStart();
}
else Respond(e, "cannot force, game not started");
}


And:

quote:

public void ComForceStart(TasSayEventArgs e, string[] words)
{
...
tas.StartGame();
...
}



If you didn't understand the code, it means:
- force is a command that does a forcestart
- forcestart is a command that does start the game

So yes, adding various "force" prefixed commands is probably adding more confusion if nothing else is changed. Or, now is a good time to actually make things logical...

(sorry for the bad code formatting, this Forum Done Right (TM) is missing a few features. But we have avatars, so who cares about code formatting?)
+0 / -0


11 years ago
quote:
- force is a command that does a forcestart
- forcestart is a command that does start the game

Actually:
- force forcibly finishes the place-your-markers period
- forcestart initiates a game

Maybe force should be renamed to begin or something, to make clearer what is being forced. With forcestart it's pretty clear that it's just a forced !start.
+0 / -0

11 years ago
The code for spring.ForceStart() is :

quote:

public void ForceStart() {
if (IsRunning) talker.SendText("/forcestart");
}


So, there is a spring command that is named forcestart. I fail to see how redefining "forcestart" in the zk/springie world is actually helping anyone.
+2 / -0
Page of 2 (31 records)