Sniper/ass kick

By Phil_FW on Jan 09, 2011

This is just a couple of simple kicks for fun :D right click a nick and go to Kicks

menu nicklist {
  .Kicks
  ..Sniper: .timersn1 1 1 /me pulls out a PSG1 | inc %snipekick | .timersn2 1 3 /me breaths in | .timersn3 1 5 /me breaths out | .timersn4 1 6 /me holds his breath and looks down the infrared scope | .timersn5 1 7 /me focuses | .timersn6 1 9 /me pulls the trigger | .timersn7 1 10 /me watches $1 fall to the ground and die | .timersn8 1 11 /kick $chan $1 4,1H1,8E4,1A1,8D4,1S1,8H4,1O1,8T0,1!! 4,1.:7,1[({9,1I have sniped11,1 %snipekick 9,1pussys7,1})]4,1:. | .timersn9 1 13 msg $chan 7,1Now14,1... 11,1Anybody else? 
  ..Ass Kick: .timeras1 1 1 /me kicks $1 in the ass | inc %asskick | .timeras2 1 2 /kick $chan $1 You just got your ass kicked... 4,1.:7,1[({9,1I have kicked11,1 %asskick 9,1asses7,1})]4,1:.
}

Comments

Sign in to comment.
Phil_FW   -  Jan 31, 2011

thanks :D

 Respond  
chachin   -  Jan 31, 2011

this thing is funny as f$$k

 Respond  
Phil_FW   -  Jan 15, 2011

LOL nice

 Respond  
koolaidman   -  Jan 15, 2011

nice i did it to test it on my king and it kicked him out! LMAO

 Respond  
Jethro   -  Jan 12, 2011

To be frank, I use pipes from time to time myself, but I've never gone overboard to a point where all the bits of my code are followed by a pipe. It's ok to use them, especially for a short strings of codes, but not in a manner of overkill.

 Respond  
Phil_FW   -  Jan 12, 2011

ahh i see... So what WOULD pipes be good for?

 Respond  
Jethro   -  Jan 12, 2011

phil24, using pipes excessively to separate codes is not usually considered the good coding practice or habit, and it can make debug more confusing and error prone if you happen to not leave a space between pipes and the code. Not to mention it gets the code a lot longer sideways, which in turn make the overall code look really ugly. Try to get rid of the pipe use and put each code line by line and you'll see how clean it looks. Here is what I mean:

menu nicklist {
  .Kicks
  ..Sniper:{
    .timersn1 1 1 me pulls out a PSG1
    inc %snipekick 
    .timersn2 1 3 me breaths in 
    .timersn3 1 5 me breaths out 
    .timersn4 1 6 me holds his breath and looks down the infrared scope
    .timersn5 1 7 me focuses 
    .timersn6 1 9 me pulls the trigger 
    .timersn7 1 10 me watches $1 fall to the ground and die 
    .timersn8 1 11 kick $chan $1 4,1H1,8E4,1A1,8D4,1S1,8H4,1O1,8T0,1!! 4,1.:7,1[({9,1I have sniped11,1 %snipekick 9,1pussys7,1})]4,1:.
    .timersn9 1 13 msg $chan 7,1Now14,1... 11,1Anybody else?
  } 
  ..Ass Kick:{ 
    .timeras1 1 1 me kicks $1 in the ass 
    inc %asskick 
    .timeras2 1 2 kick $chan $1 You just got your ass kicked... 4,1.:7,1[({9,1I have kicked11,1 %asskick 9,1asses7,1})]4,1:.
  }
}
 Respond  
Phil_FW   -  Jan 12, 2011

what would be better than the pipes? and on my server, ops flood a lot lol. so it doesnt really bother people much

 Respond  
napa182   -  Jan 12, 2011

the first one is a bit floody.
also you should limit the use of pipes.

 Respond  
Phil_FW   -  Jan 09, 2011

LOL Breanna...thats bcuz i made it as a n00b, i was bored :P and Back2Life, i only use it on channels im oped on. which is what i suggest to anybody using it

 Respond  
Breanna   -  Jan 09, 2011

Looks Like Something a New scripter would make O_O and u been here like 6 months..

 Respond  
Back2Life   -  Jan 09, 2011

This works for what it does, but I think the messages may be a bit too much. If it is not your own channel you may be accused of spamming or flooding, but I don't know.

It works good, and the code looks good to me.

 Respond  
Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.