CA Program Ideas
Ok guys so i'm out of ideas about what to code for CA. You guys have any ideas?
Spam posts will be deleted.
Spam posts will be deleted.
CA Program Ideas
-an improoved rez tool
-texture remover
-afk bot
-windowed
-kdr calculator (non web-based)
-color trigger bot with 250-0-0 as color value, unchangeable with head mod
-spammer
-snipe magnifition (liek the wps one)
-Cleaner
-DLL Injector
-Memory Editor
-Mini Chams
-Nexon Passport Generator
*all the in one, sexy themed and theme color choice (purple)
and ill post more later on...
-texture remover
-afk bot
-windowed
-kdr calculator (non web-based)
-color trigger bot with 250-0-0 as color value, unchangeable with head mod
-spammer
-snipe magnifition (liek the wps one)
-Cleaner
-DLL Injector
-Memory Editor
-Mini Chams
-Nexon Passport Generator
*all the in one, sexy themed and theme color choice (purple)
and ill post more later on...
Originally Posted by Jarppi
-an improoved rez tool
-texture remover
-afk bot
-windowed
-kdr calculator (non web-based)
-color trigger bot with 250-0-0 as color value, unchangeable with head mod
-spammer
-snipe magnifition (liek the wps one)
and ill post more later on...
-texture remover
-afk bot
-windowed
-kdr calculator (non web-based)
-color trigger bot with 250-0-0 as color value, unchangeable with head mod
-spammer
-snipe magnifition (liek the wps one)
and ill post more later on...
. Windowed mode, ill see if i can code that. Not sure if i can tho , KDR calculator, seems doable. Trigger Bot, maybe ill try it. Spammer - patched unless i find a way around sendkeys Snipe magnification, ill try and find stuff about it.i edited, added more! what about rez tool?
Originally Posted by Jarppi
i edited, added more!
-DLL Injector
-Memory Editor
-Mini Chams
-Nexon Passport Generator
*all the in one, sexy themed and theme color choice (purple)
Dll Injector, i have one out, guess i could update it. Memory Editor, ermm yah that will be difficult haha. Mini-Chams, i think i could do that. Nexon passport generator. I can probably make that
BTW Purple what do u mean by a rez tool?
Originally Posted by Bombsaway707
I see haha
-DLL Injector
-Memory Editor
-Mini Chams
-Nexon Passport Generator
*all the in one, sexy themed and theme color choice (purple)
Dll Injector, i have one out, guess i could update it. Memory Editor, ermm yah that will be difficult haha. Mini-Chams, i think i could do that. Nexon passport generator. I can probably make that
BTW Purple what do u mean by a rez tool?
-DLL Injector
-Memory Editor
-Mini Chams
-Nexon Passport Generator
*all the in one, sexy themed and theme color choice (purple)
Dll Injector, i have one out, guess i could update it. Memory Editor, ermm yah that will be difficult haha. Mini-Chams, i think i could do that. Nexon passport generator. I can probably make that
BTW Purple what do u mean by a rez tool?
your my 100th thx, WOO HOO, PARTY!!!!! Originally Posted by Jarppi
like, wps released a mod-o-matic, like an, injector, xtractor, converter, dtx viewer and when you choose a .dtx or ltb, it auto-find the folder, and much more, you rock, you'll do more
An autoclicker?
(Mine)
Oh yeah, can you improve on it somehow? VB code analysis says it's messy.
Warning 1 CA1060 : Microsoft.Design : Because it is a P/Invoke method, 'Autoclicker.GetAsyncKeyState(Long)' should be defined in a class named NativeMethods, SafeNativeMethods, or UnsafeNativeMethods. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 6 CA1060 : Microsoft.Design : Because it is a P/Invoke method, 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' should be defined in a class named NativeMethods, SafeNativeMethods, or UnsafeNativeMethods. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 13 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'cbuttons' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 14 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'cbuttons' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 15 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwExtraInfo' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 7 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwflags' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 8 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwflags' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 9 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dx' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 10 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dx' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 11 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dy' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 12 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dy' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 2 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'vkey' of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 3 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'vkey' of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 4 CA1901 : Microsoft.Portability : As it is declared in your code, the return type of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 4 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 2 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Integer'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 5 CA1901 : Microsoft.Portability : As it is declared in your code, the return type of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 4 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 2 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Integer'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
(Mine)
Code:
Public Class Autoclicker
Private Declare Function GetAsyncKeyState Lib "user32" (ByVal vkey As Long) As Integer
Private Declare Sub mouse_event Lib "user32" (ByVal dwflags As Long, ByVal dx As Long, ByVal dy As Long, ByVal cbuttons As Long, ByVal dwExtraInfo As Long)
Private Const mouseclickup = 4
Private Const mouseclickdown = 2
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Timer1.Interval = TextBox1.Text
Timer1.Start()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
Timer1.Stop()
End Sub
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Timer1.Tick
mouse_event(mouseclickdown, 0, 0, 0, 0)
mouse_event(mouseclickup, 0, 0, 0, 0)
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
Me.Close()
End Sub
Private Sub Form1_KeyDown(ByVal sender As Object, ByVal e As System.Windows.Forms.KeyEventArgs) Handles MyBase.KeyDown
End Sub
Private Sub Timer2_Tick(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Timer2.Tick
Timer2.Enabled = True
Timer2.Interval = 1
Dim Alt As Boolean
Dim Z As Boolean
Alt = GetAsyncKeyState(Keys.Menu)
Z = GetAsyncKeyState(Keys.Z)
If Alt And Z = True Then
Call Button1_Click(Button1, e)
End If
Dim X As Boolean
Alt = GetAsyncKeyState(Keys.Menu)
X = GetAsyncKeyState(Keys.X)
If Alt And X = True Then
Call Button2_Click(Button2, e)
End If
End Sub
Private Overloads Sub TextBox1_TextChanged(ByVal sender As System.Object, ByVal e As System.Windows.Forms.KeyPressEventArgs) Handles TextBox1.KeyPress
Dim isKey As Boolean = Char.IsDigit(e.KeyChar)
Dim isDecimal As Boolean = e.KeyChar.ToString = "."
If Not isKey And Not isDecimal Then
e.Handled = True
End If
End Sub
End Class
Warning 1 CA1060 : Microsoft.Design : Because it is a P/Invoke method, 'Autoclicker.GetAsyncKeyState(Long)' should be defined in a class named NativeMethods, SafeNativeMethods, or UnsafeNativeMethods. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 6 CA1060 : Microsoft.Design : Because it is a P/Invoke method, 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' should be defined in a class named NativeMethods, SafeNativeMethods, or UnsafeNativeMethods. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 13 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'cbuttons' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 14 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'cbuttons' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 15 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwExtraInfo' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 7 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwflags' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 8 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dwflags' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 9 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dx' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 10 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dx' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 11 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dy' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 12 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'dy' of P/Invoke 'Autoclicker.mouse_event(Long, Long, Long, Long, Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 3 Multitool
Warning 2 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'vkey' of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 8 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 3 CA1901 : Microsoft.Portability : As it is declared in your code, parameter 'vkey' of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 8 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 4 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Long'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 4 CA1901 : Microsoft.Portability : As it is declared in your code, the return type of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 4 bytes wide on 32-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 2 bytes wide on 32-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Integer'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
Warning 5 CA1901 : Microsoft.Portability : As it is declared in your code, the return type of P/Invoke 'Autoclicker.GetAsyncKeyState(Long)' will be 4 bytes wide on 64-bit platforms. This is not correct, as the actual native declaration of this API indicates it should be 2 bytes wide on 64-bit platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of 'Integer'. C:\Users\spy\documents\visual studio 2010\Projects\Multitool\Multitool\Autoclicker.vb 2 Multitool
If you need an autoclicker just use garyshood, back from the ol' runescape days.
I'll upload if you want.
I'll upload if you want.
GAY GAY GAY GAY AND GAY!
VB can't do RezInject.. that was coded in C#.. an AutoClicker is too easy, nametags = R:150, B:0, G:0, HEX: 0x960000...
something like my snipers delight would be good to see tho.. somebody posted one made in VB but it failed, couldn't move the window or even see half of it.
Mod'O'Matic is also too easy, just a file mover for .rez/dtx/ltb.. i need to update that and make it more efficient. File Duplicator might be a little bit of a challenge for you in VB tho.
KDR Calculator would be WAY too easy.. kills divided by deaths.. the math for calculating a desired KDR would be the difficult part.. i got my old script somewhere for it.. i can give you the math if you want to set up a nice GUI with some other options on it.
Windowed mode is only available for .dll hacks.. it has to be programmed directly into the running of the game, you already know about GMOption being patched.
shox asked me about a 360 bot.. which sounds like an awesome idea, but i haven't been able to do it properly. if you mark a variable as the starting position for recording, and one for the stopping position, if stop > start they moved the mouse to the right, if start > stop they moved the mouse left.. however when you complete a 360 to the exact mark your start and stop positions are the same. so you have to record each X coord the mouse crosses over, and do subtraction for > or < to see how far in pixels the mouse was moved, and even if you successfully complete all that bullshit, you still have MOUSE SENSITIVITY TO CALCULATE!!!!!!!!
an idea for you to do thats original however.. NO FUCKING CLUE!! i've made 3 threads like this before and the 360 bot is the only thing i came across that seemed doable and unique.
VB can't do RezInject.. that was coded in C#.. an AutoClicker is too easy, nametags = R:150, B:0, G:0, HEX: 0x960000...
something like my snipers delight would be good to see tho.. somebody posted one made in VB but it failed, couldn't move the window or even see half of it.
Mod'O'Matic is also too easy, just a file mover for .rez/dtx/ltb.. i need to update that and make it more efficient. File Duplicator might be a little bit of a challenge for you in VB tho.
KDR Calculator would be WAY too easy.. kills divided by deaths.. the math for calculating a desired KDR would be the difficult part.. i got my old script somewhere for it.. i can give you the math if you want to set up a nice GUI with some other options on it.
Windowed mode is only available for .dll hacks.. it has to be programmed directly into the running of the game, you already know about GMOption being patched.
shox asked me about a 360 bot.. which sounds like an awesome idea, but i haven't been able to do it properly. if you mark a variable as the starting position for recording, and one for the stopping position, if stop > start they moved the mouse to the right, if start > stop they moved the mouse left.. however when you complete a 360 to the exact mark your start and stop positions are the same. so you have to record each X coord the mouse crosses over, and do subtraction for > or < to see how far in pixels the mouse was moved, and even if you successfully complete all that bullshit, you still have MOUSE SENSITIVITY TO CALCULATE!!!!!!!!
an idea for you to do thats original however.. NO FUCKING CLUE!! i've made 3 threads like this before and the 360 bot is the only thing i came across that seemed doable and unique.
Originally Posted by Grim
GAY GAY GAY GAY AND GAY!
VB can't do RezInject.. that was coded in C#.. an AutoClicker is too easy, nametags = R:150, B:0, G:0, HEX: 0x960000...
something like my snipers delight would be good to see tho.. somebody posted one made in VB but it failed, couldn't move the window or even see half of it.
Mod'O'Matic is also too easy, just a file mover for .rez/dtx/ltb.. i need to update that and make it more efficient. File Duplicator might be a little bit of a challenge for you in VB tho.
KDR Calculator would be WAY too easy.. kills divided by deaths.. the math for calculating a desired KDR would be the difficult part.. i got my old script somewhere for it.. i can give you the math if you want to set up a nice GUI with some other options on it.
Windowed mode is only available for .dll hacks.. it has to be programmed directly into the running of the game, you already know about GMOption being patched.
shox asked me about a 360 bot.. which sounds like an awesome idea, but i haven't been able to do it properly. if you mark a variable as the starting position for recording, and one for the stopping position, if stop > start they moved the mouse to the right, if start > stop they moved the mouse left.. however when you complete a 360 to the exact mark your start and stop positions are the same. so you have to record each X coord the mouse crosses over, and do subtraction for > or < to see how far in pixels the mouse was moved, and even if you successfully complete all that bullshit, you still have MOUSE SENSITIVITY TO CALCULATE!!!!!!!!
an idea for you to do thats original however.. NO FUCKING CLUE!! i've made 3 threads like this before and the 360 bot is the only thing i came across that seemed doable and unique.
VB can't do RezInject.. that was coded in C#.. an AutoClicker is too easy, nametags = R:150, B:0, G:0, HEX: 0x960000...
something like my snipers delight would be good to see tho.. somebody posted one made in VB but it failed, couldn't move the window or even see half of it.
Mod'O'Matic is also too easy, just a file mover for .rez/dtx/ltb.. i need to update that and make it more efficient. File Duplicator might be a little bit of a challenge for you in VB tho.
KDR Calculator would be WAY too easy.. kills divided by deaths.. the math for calculating a desired KDR would be the difficult part.. i got my old script somewhere for it.. i can give you the math if you want to set up a nice GUI with some other options on it.
Windowed mode is only available for .dll hacks.. it has to be programmed directly into the running of the game, you already know about GMOption being patched.
shox asked me about a 360 bot.. which sounds like an awesome idea, but i haven't been able to do it properly. if you mark a variable as the starting position for recording, and one for the stopping position, if stop > start they moved the mouse to the right, if start > stop they moved the mouse left.. however when you complete a 360 to the exact mark your start and stop positions are the same. so you have to record each X coord the mouse crosses over, and do subtraction for > or < to see how far in pixels the mouse was moved, and even if you successfully complete all that bullshit, you still have MOUSE SENSITIVITY TO CALCULATE!!!!!!!!
an idea for you to do thats original however.. NO FUCKING CLUE!! i've made 3 threads like this before and the 360 bot is the only thing i came across that seemed doable and unique.
Originally Posted by Jarppi
whats your point of flamming me??
How about a recoil reducer that moves the mouse down 5-10 pixels every set amount of time when you hold down the mouse button?
An auto clicker that denies Invites...
Originally Posted by Synchromanica
An auto clicker that denies Invites...
This thread is closed for replies.
