This topic is locked
Hmm. I could use a wait command.
But this will not answer, why the first nuke didnt start?
Greetings Avatar
Advertisement
NUKE-Script
Rate Topic:
MultiQuote
#12
ghozt (old) 
- Joined: 16-January 04
- Posts: 862
- LocationDelaware, USA
Posted 12 April 2004 - 01:41 AM
FSK405N was workin on a random nuke script on our server.. it was server side though.. maybe it could help u out, find him on irc or kickassctf.com
#13
Sachem (old)
- Joined: 08-February 04
- Posts: 81
- LocationFrance
Posted 12 April 2004 - 01:48 PM
is there a way to nuke by client ID rather than by name? I never heard of one.
#14
HELSEN (old)
- Joined: 18-January 04
- Posts: 122
- LocationGermany
Posted 12 April 2004 - 05:30 PM
I always nuke bei clientID, because names-nuking is a pain in the a**
And it work nice for me
Greetings Avatar
And it work nice for me
Greetings Avatar
Advertisement
#16
tr!ckn0l0gy (old)
- Joined: 19-January 04
- Posts: 1,678
- Locationreal virtuality
Posted 14 April 2004 - 10:05 AM
didn't autoaim.cfg want to rewrite the whole thing? hey iLA send your leader to help out here!
#17
HELSEN (old)
- Joined: 18-January 04
- Posts: 122
- LocationGermany
Posted 14 April 2004 - 10:24 AM
Ok, I get it running, with wait-commands about 75-100.
But with 17 Slots on my server, the last one will get his ca. 20 seconds after the first one.
= useless
But with 17 Slots on my server, the last one will get his ca. 20 seconds after the first one.
= useless
#18 Guest_FSK05N
Posted 22 April 2004 - 05:05 PM
Well, I remember the things you guys have already come across as I wrote this script last October, I think. It uses urtrcon.pl and bash.
#!/bin/bash
#
# random-nuke.sh
#
# DEPS: urtrcon.pl and players.sh
#
# this pulls the player stats urtrcon.pl, strips
# off the crap (i should just re-write urtrcon
# but this works with little cost so wtf..)
###################################################
IP='YOURSERVERIPADDRESS'
PASS='YOURRCONPASS'
# this gets just the CID from quake and correctly sorts them
# to find the 'high' number for our range..
players.sh |gawk '{print $1}' |grep [0-9.] |sort -g >cids.tmp
# random is taken from /dev/srandom i believe
# range comes from the above CID listing..
RANGE=`tail -q -n1 cids.tmp`
sleep 3 #cause urtrcon or quake is choking on it..
number=$RANDOM
let "number %= $RANGE"
urtrcon.pl -s $IP -P $PASS -c "nuke $number"
rm -f cids.tmp
#fin
#!/bin/bash
#
# players.sh
# Who is on the server...
IP='YOURSERVERIP'
PASS='YOURRCONPASS'
urtrcon.pl -s $IP -P $PASS
#fin
############################
The 2nd script is useful by itself as 'players.sh' in ~/bin so while you are at a *nix console, you can see instantly the map and what players are online.
HTH!
Happy Fraggin!
PS - I think the slow sending of commands is the built-in flood control.
#!/bin/bash
#
# random-nuke.sh
#
# DEPS: urtrcon.pl and players.sh
#
# this pulls the player stats urtrcon.pl, strips
# off the crap (i should just re-write urtrcon
# but this works with little cost so wtf..)
###################################################
IP='YOURSERVERIPADDRESS'
PASS='YOURRCONPASS'
# this gets just the CID from quake and correctly sorts them
# to find the 'high' number for our range..
players.sh |gawk '{print $1}' |grep [0-9.] |sort -g >cids.tmp
# random is taken from /dev/srandom i believe
# range comes from the above CID listing..
RANGE=`tail -q -n1 cids.tmp`
sleep 3 #cause urtrcon or quake is choking on it..
number=$RANDOM
let "number %= $RANGE"
urtrcon.pl -s $IP -P $PASS -c "nuke $number"
rm -f cids.tmp
#fin
#!/bin/bash
#
# players.sh
# Who is on the server...
IP='YOURSERVERIP'
PASS='YOURRCONPASS'
urtrcon.pl -s $IP -P $PASS
#fin
############################
The 2nd script is useful by itself as 'players.sh' in ~/bin so while you are at a *nix console, you can see instantly the map and what players are online.
HTH!
Happy Fraggin!
PS - I think the slow sending of commands is the built-in flood control.
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement