Post: Skype Bomber [Tool]
05-06-2012, 08:41 PM #1
(adsbygoogle = window.adsbygoogle || []).push({});
You must login or register to view this content.


News:
- Version 1.6.5.0 is now out for release.
- Because of the tools simplicity it will be open source once the final version is out. For now if you have any suggestions feel free to comment.


Hello everyone, I have another tool out for release. This tool has the ability to spam Skype chat, but it is currently in a beta stage. I will be updating it and improving on it though. What separates this from a regular spammer is its ability to easily send commands and emoticons, as well as text. So for now enjoy this version and check back soon for updates.


You must login or register to view this content.


Features


  • Text Spamming

  • Emoticon Spamming

  • Invite Spamming

  • NEW! Add and kick user spamming


More features coming soon...

How to use

Step 1: Create what you want to spam using the tool.

Step 2: Press start.

Step 3: Then click on the Skype message box where you would normally type.

Step 4: Watch the message be spammed. Be careful not to open another program and spam it with text.


Downloads

Skype Bomber: 5/7/2012 - 1.6.5.0 You must login or register to view this content.

Virus Scan: You must login or register to view this content.


Update log:

1.6.5.0 - Fixed small bugs, cleaned up the code and added more emoticons.

1.5.1.0 - Fixed another emoticon bug.

1.5.0.0 - Added the kick and add feature.

1.1.5.0 - Added more emoticons and a way to change the speed interval.

1.0.0.1 - Fixed emoticon stacking issue.

1.0.0.0 - Official beta release.

Have fun and remember the risk that come with spamming on any chatting service.


Credits

MagicalMonkey AKA Rage - Developer

Dylan - Beta Tester

Tree - Beta Tester [Found a emoticon bug that called for the release of 1.5.1.0]
Last edited by MagicalMonkey ; 05-11-2012 at 11:06 AM.

The following 4 users say thank you to MagicalMonkey for this useful post:

JBModzPS3, Ninja, ProfoundModz
05-07-2012, 11:54 PM #11
Originally posted by Sublimity View Post
Rather than using If statements for:

    
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]0[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]25[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]1[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]50[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]2[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]75[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]3[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]100[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]4[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]125[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]5[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]150[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]6[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]175[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]7[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]200[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]8[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]225[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]9[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]250[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]10[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]275[/COLOR];
}
flag = ([B]this[/B].TrackBar1.Value == [COLOR=#00008b]11[/COLOR]);
[COLOR=#0000ff][B]if[/B][/COLOR] (flag)
{
[B]this[/B].Timer1.Interval = [COLOR=#00008b]300[/COLOR];
}


Why don't you use Switch Case statements. This means you can check for a certain value and if that value is given then it searches for the case and then uses that code.

Say, int tbvalue = TrackBar1.Value();

Switch(tbvalue)
{
case 1: Timer1.Interval = 25; break;
case 2: Timer1.Interval = 50; break;
}

It helps you out so you don't have to write 50 lines of code.


I guessed it seemed easier at the moment. I will use this next time, as long as I can figure out the VB equivalent.

P.S. What de-compiler did you use?
05-08-2012, 12:02 AM #12
Pichu
RIP PICHU.
Originally posted by MagicalMonkey View Post
I guessed it seemed easier at the moment. I will use this next time, as long as I can figure out the VB equivalent.

P.S. What de-compiler did you use?


ILSpy, it's free. It can decompile and convert VB.Net to C# and C# to VB.NET.

The following user thanked Pichu for this useful post:

MagicalMonkey
05-18-2012, 01:30 AM #13
Pichu
RIP PICHU.
Originally posted by MagicalMonkey View Post
And I have. In my post I told him to do it himself or to just wait a minute. I ain't even mad... So please for now on every one stay on topic in this post.


Just noticed something with my post above, when I took out your code, I see you are using boolean to determine true/false of a comparison between two items. Then if (true)

You are having the program read through everything,

this.Timer1.Interval = 25;
}
flag = (this.TrackBar1.Value == 1);
if (flag)
{
this.Timer1.Interval = 50;
}
flag = (this.TrackBar1.Value == 2);
if (flag)
{
this.Timer1.Interval = 75;
}
flag = (this.TrackBar1.Value == 3);

You are having the program check to see if TrackBar.Value == 1 and so if then flag should = true or false. The problem with that is if it is true, it then read through the true statment but then resets the flag with the next line and sets it to false as it wouldn't equal.

Rather than doing this, you could simply type in if(TrackBar1.Value == 1) since if statements are boolean (true/false) ... this means you could write it if(TrackBar1.Value != 1) (== Is Equal To != Is Not Equal To)

This then removes the need for you to use bool as the if statement already takes care of it.

if you were working on a program that asked the user if something was true or false and that true or false decision would be used multiple times elsewhere to develop a certain outcome and you needed to contain that true/false decision, bool would be great but for what is written here, it is not.
05-18-2012, 06:42 AM #14
fill0botto95
You talkin to me?
Originally posted by Sublimity View Post
Just noticed something with my post above, when I took out your code, I see you are using boolean to determine true/false of a comparison between two items. Then if (true)

You are having the program read through everything,

this.Timer1.Interval = 25;
}
flag = (this.TrackBar1.Value == 1);
if (flag)
{
this.Timer1.Interval = 50;
}
flag = (this.TrackBar1.Value == 2);
if (flag)
{
this.Timer1.Interval = 75;
}
flag = (this.TrackBar1.Value == 3);

You are having the program check to see if TrackBar.Value == 1 and so if then flag should = true or false. The problem with that is if it is true, it then read through the true statment but then resets the flag with the next line and sets it to false as it wouldn't equal.

Rather than doing this, you could simply type in if(TrackBar1.Value == 1) since if statements are boolean (true/false) ... this means you could write it if(TrackBar1.Value != 1) (== Is Equal To != Is Not Equal To)

This then removes the need for you to use bool as the if statement already takes care of it.

if you were working on a program that asked the user if something was true or false and that true or false decision would be used multiple times elsewhere to develop a certain outcome and you needed to contain that true/false decision, bool would be great but for what is written here, it is not.


Please use vb language for our friend LOL

== -> =
!= -> <>


You could short your a lot by using a moltiplicator that multiply the trackbar value

Const MULT As Int32 = 30


Timer.Intervals = Trackbar.Value * MULT
Last edited by fill0botto95 ; 05-18-2012 at 06:49 AM.
05-18-2012, 10:48 PM #15
Pichu
RIP PICHU.
Originally posted by fill0botto95 View Post
Please use vb language for our friend LOL

== -> =
!= -> <>


You could short your a lot by using a moltiplicator that multiply the trackbar value

Const MULT As Int32 = 30


Timer.Intervals = Trackbar.Value * MULT


Sorry, I haven't really used VB in a while so I forgot that they were different.
05-19-2012, 11:06 AM #16
fill0botto95
You talkin to me?
Originally posted by Virgin View Post
Sorry, I haven't really used VB in a while so I forgot that they were different.


Don't worry, I were sarcastic

You changed username Sad Awesome
05-19-2012, 04:26 PM #17
Pichu
RIP PICHU.
Originally posted by fill0botto95 View Post
Don't worry, I were sarcastic

You changed username Sad Awesome


Yep, I was surprised when I found out the name Virgin wasn't taken. :P
05-19-2012, 06:11 PM #18
Originally posted by fill0botto95 View Post
Please use vb language for our friend LOL

== -> =
!= -> <>


You could short your a lot by using a moltiplicator that multiply the trackbar value

Const MULT As Int32 = 30


Timer.Intervals = Trackbar.Value * MULT


Originally posted by Virgin View Post
Just noticed something with my post above, when I took out your code, I see you are using boolean to determine true/false of a comparison between two items. Then if (true)

You are having the program read through everything,

this.Timer1.Interval = 25;
}
flag = (this.TrackBar1.Value == 1);
if (flag)
{
this.Timer1.Interval = 50;
}
flag = (this.TrackBar1.Value == 2);
if (flag)
{
this.Timer1.Interval = 75;
}
flag = (this.TrackBar1.Value == 3);

You are having the program check to see if TrackBar.Value == 1 and so if then flag should = true or false. The problem with that is if it is true, it then read through the true statment but then resets the flag with the next line and sets it to false as it wouldn't equal.

Rather than doing this, you could simply type in if(TrackBar1.Value == 1) since if statements are boolean (true/false) ... this means you could write it if(TrackBar1.Value != 1) (== Is Equal To != Is Not Equal To)

This then removes the need for you to use bool as the if statement already takes care of it.

if you were working on a program that asked the user if something was true or false and that true or false decision would be used multiple times elsewhere to develop a certain outcome and you needed to contain that true/false decision, bool would be great but for what is written here, it is not.



Thank-you Fill0 and sub... I mean Virgin. :P
02-22-2014, 03:35 AM #19
Nice :yes: Ill deffinantly be using this

Copyright © 2024, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo