Ideas

[tempest]

Er... isn't it

[SELECT ALL] Code:

/alias cancel [setadmin 1 password; vote 0; setadmin 0]

?

[Ronald_Reagan]

Ya, tempest would be correct. To be save, add a sleep ~10-200 after the setadmin 1 pw.

[Mael]

Along with filtering foul language, block consecutive messages containing the same/excessive remarks. Team chat is where much harassment takes place, likely so the other team cannot hear it, maybe because demos do not store it.

[#M|A#Wolf]

Just like getting a demo from a game, the availability of getting the chat with something like: "/getchat" which also includes team talk. Would be nice instead of getting a 1000 KB demo and taking the screenshot of the chat, to download a 10 KB Notepad file that has the chat.

[Gibstick]

Wolf: Linux and Windows users have the privilege of client logs from the .bat or .sh :>
If you could run AC from terminal in Mac you could get it too.

[tempest]

I bet you can.

[pwned]

im not sure if this was already in AC 1.1 cuz i could not get a chance to test it.
Idea 1: restrict a player from coming back to game after being kicked (for curtain reason). after the game round ends, he may come back
Idea 2:restrict a player from voting kick/ban constantly. maybe set it to 2 minutes. so after your vote has passed, you cant start a vote for 2 minutes

[V-Man]

I thought in 1.1, demos record team talk and display it for both teams.

@pwned: There's a measure in place now that keeps people from calling excessive votes (if those votes fail). Naturally it doesn't stop an admin from banning several people in a row (since those votes don't fail).

Also, I think it's good to let multiple votes to ban pass if there are multiple cheaters or TKers, etc. It would suck to have to endure that in between kick/ban votes.

[pwned]

@V-Man
there are other players in the game that will start the vote.

if there are multiple cheaters

that's where Brahma's anti-cheat system comes in

[Gibstick]

Over-reliance on anti-cheat will lead to crappy matches. Nothing compares to good parental supervision a reliable admin but that doesn't always happen.

[V-Man]

Sorry if I made it sound like cheating is the only reason to ban someone. There are plenty without me needing to list them all.

[Luc@s]

Someone suggested me to post it in the idea thread so :
http://forum.cubers.net/thread-946.html

:)

[DrauL]

Eliminate No votes, allow admins to cancel votes, and abbreviate voting time. There really isn't any reason for No votes, and votes called often last much longer than necessary. When a vote ends 10 Yes - 4 No it just creates confusion for new players who don't understand how voting works.

[SELECT ALL] Code:

/alias cancel [vote 0; setadmin 1 password; setadmin 0]

Then when there's a vote you:

[SELECT ALL] Code:

/cancel

Er... isn't it

[SELECT ALL] Code:

/alias cancel [setadmin 1 password; vote 0; setadmin 0]

?

Ya, tempest would be correct. To be save, add a sleep ~10-200 after the setadmin 1 pw.

Actually RR, you can vote and then claim admin and whatever you voted automatically happens. Pass or Fail

[Gibstick]

No, what if you already voted and you want to change your mind?

[Ronald_Reagan]

To be safe

Yea, whatever DrauL, I like to be safe.
Probably the reason I'm not dead...

[vonunov]

Ya, tempest would be correct. To be save, add a sleep ~10-200 after the setadmin 1 pw.

I don't see what the difference is between voting no, then taking and releasing admin; and taking admin, voting no, and releasing admin. Or why we need a sleep.

[Gibstick]

Because Cubescript is bound to fail and there is lag and computers are shitty.

[Luc@s]

we should be able to use a read only var like "ping" in cubescript :D for example :

[SELECT ALL] Code:

forceteam 0; sleep $ping [forceteam 1]

[vonunov]

How can you have a read-only var that's constantly changing?

[Gibstick]

We already have alive and version and curprimary and...

[Ronald_Reagan]

Tis a read only that could help by saying "Your ping is too high" if your ping hits a number.
Be something like;

[SELECT ALL] Code:

while [(ping) < 400] []
[
  echo "Check your ping!"
]

This is assuming that "while" didn't bomb your client.

[vonunov]

Tis a read only that could help by saying "Your ping is too high" if your ping hits a number.
Be something like;

[SELECT ALL] Code:

while [(ping) > 400] []
[
  echo "Check your ping!";
  sleep 5000;
]

This is assuming that "while" didn't bomb your client.

Fixed your operator ;)
Also we don't want to flood ourselves, maybe once every 5 seconds will do? :p

[Ronald_Reagan]

Hey I was just drafting it up.
Yea, the right operator would help :D
Also, I didn't spend too much time considering that ping isn't even implemented.

[V-Man]

"read-only" refers to the inability of the user to change it as if it were a setting. It is something that constantly monitors the status of a particular aspect of the game and can report it at any moment on command.
And yeah, /ping would be a great command to have.
And don't use "while" to do that. XD

[Ronald_Reagan]

This is assuming that "while" didn't bomb your client.

And don't use "while" to do that. XD

Constant loops is kinda iffy, cuz ping changes a lot. I guess you can do a recursive loop if you want :P

[Luc@s]

[SELECT ALL] Code:

alias checkping [if ( > (ping) $pinglimit) [ echo "U LAG !"]; sleep 5000 [checkping]]

something like that :p

---

Ok in clientgame.cpp :

[SELECT ALL] Code:

// existing part
int isalive() { return player1->state==CS_ALIVE ? 1 : 0; }
COMMANDN(alive, isalive, ARG_IVAL);
// what to add
int ping() { return player1->ping; }
COMMAND(ping, ARG_IVAL);

then compile and it will work :)
Devs can you add it ? :D

[vonunov]

"read-only" refers to the inability of the user to change it as if it were a setting. It is something that constantly monitors the status of a particular aspect of the game and can report it at any moment on command.
And yeah, /ping would be a great command to have.
And don't use "while" to do that. XD

Oh, that read-only. :P

[Ronald_Reagan]

Luc@s, if you were going to do a recursive loop, make it way less than 5 seconds... By five seconds you would've already figured out :P Also, if your computer is too slow to handle a 5 second loop, then lag wouldn't be a new thing. I'd set it around 1-500

[ElCrema]

Some one once on IRC mentioned an idea about a game mode: Efficiency (I think it was Brett, but I'm not so sure). Something like TS but at every new round everyone would spawn with the same type of weapon and teams would be constantly swamping sides, sounds interesting...

[Luc@s]

Luc@s, if you were going to do a recursive loop, make it way less than 5 seconds... By five seconds you would've already figured out :P Also, if your computer is too slow to handle a 5 second loop, then lag wouldn't be a new thing. I'd set it around 1-500

it was just an example lol
The only thing that could be taken is the c++ part