Warframe rapidfire's

[filippe999]

Hello fellow scripters.

Due to a recent data wipe on my hard drive i had been unable to recover my previous gaming scripts i had made. But thankfully once you do something once the second time is much easier.

As a means of safe storage and sharing my code i will post my warframe helper script here.
For those concerned with the rules, in short, DE only bans players who use script to execute compound actions, say slide-jump-roll-repeat is ban worthy, a script to jump while holding down the key, is not.

Features:

• Rapid fire on hold melee key: for those of us who like having our middle finger operational after 40m survival sessions with melee only, All it does is send the command every 100 seconds to the game as you hold down the key, let it go and it stops;
• Ability spammer: F1, F2, F3, F4, will send to the game respectively 1, 2, 3, 4, at a set delay, the delay between keys is adjustable while it's running, by default the time is 500 milliseconds. I have not tested to send more than one key at once this way, so use only for single ability or have a hand at improving it yourself(Please share);

Keys;

• Numpad Sub = Suspend script;
• E = trigger for melee rapid-fire;
• F1, F2, F3, F4 = spam 1, 2, 3, 4 respectively;
• Numpad Multiply = Double the time between keystrokes on the ability spammer(500>1000>2000>4000...);
• Numpad Divide = Lower the time between keystrokes on the ability spammer by half(500>250>125>62.5>31.25...);
• Numpad Add = Set the time between Keystrokes on the ability spammer to 500;

Code: Select all

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
#MaxThreadsPerHotkey 2

delay:=500
toggle:=false

NumpadSub::Suspend

$E::
	loop
	{
		if GetKeyState("e", "p")=0
		{
			break
		}
		send {e down}
		sleep 100
		send {e up}
		sleep 100
	}
return

$F1::
	toggle:=!toggle
	while(toggle=1)
	{
		send 1
		sleep delay
	}
return

$F2::
	toggle:=!toggle
	while(toggle=1)
	{
		send 2
		sleep delay
	}
return

$F3::
	toggle:=!toggle
	while(toggle=1)
	{
		send 3
		sleep delay
	}
return

$F4::
	toggle:=!toggle
	while(toggle=1)
	{
		send 4
		sleep delay
	}
return

~NumpadMult::
	delay:=delay*2
return

~NumpadDiv::
	delay:=delay/2
return

~NumpadAdd::
	delay:=500
return

[Rangerbot]

Code: Select all

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
#MaxThreadsPerHotkey 2

increment := 100
delay := increment*5
toggle := false

$E::
	loop
	{
		if GetKeyState("e", "p")=0
		{
			break
		}
		send {e down}
		sleep 100
		send {e up}
		sleep 100
	}
return

$F1::
	toggle:=!toggle
	while(toggle=1)
	{
		send 1
		sleep %delay%
	}
return

$F2::
	toggle:=!toggle
	while(toggle=1)
	{
		send 2
		sleep delay
	}
return

$F3::
	toggle:=!toggle
	while(toggle=1)
	{
		send 3
		sleep delay
	}
return

$F4::
	toggle:=!toggle
	while(toggle=1)
	{
		send 4
		sleep delay
	}
return

~NumpadAdd::
	if((delay-increment) >= 25)
		delay -= increment
;msgbox,,,%delay%, 0.5
return

~NumpadSub::
	delay += increment
;msgbox,,,%delay%, 0.5
return


Pause::Reload

in my experience if you have a healthy amount of sleep time in your loop, a hotKey that calls "Reload" will break any currently running loop well enough
Try out my own frequency changing technique, it's a bit safer than what you had