Advertisement
Page 1 of 1
changemode; fire; changemode; fire
Good find ... being fixed... Classed as Exploit!
#1
Posted 28 May 2014 - 09:23 PM
Dear All,
I'm sure many people realise that this is not exactly what we had in mind with the functionality of scripting.
Every now and again there is something that "Surfaces" which is not in keeping with what we wanted to happen with a particular feature.
In the upcoming releases we will remove "fire" as a scripable option. You must press this button in all cases yourself. Thus removing said exploit of making a "spread reset" system.
It is official FS Possition that this is an exploit, not a feature! We wish people to treat it as such!
Thanks
R
Added: https://github.com/F...ror42/issues/32
I'm sure many people realise that this is not exactly what we had in mind with the functionality of scripting.
Every now and again there is something that "Surfaces" which is not in keeping with what we wanted to happen with a particular feature.
In the upcoming releases we will remove "fire" as a scripable option. You must press this button in all cases yourself. Thus removing said exploit of making a "spread reset" system.
It is official FS Possition that this is an exploit, not a feature! We wish people to treat it as such!
Thanks
R
Added: https://github.com/F...ror42/issues/32
#3
Posted 29 May 2014 - 12:03 AM
o.0 i didnt even knew this existed... but its pretty cool. more or less. more less...
totally agree that its an exploit though, i just like scripting. :)
Though i wouldnt like to see +attack to be removed from scripting. (-attack could be totally removed then...):
this would also break scripts that change the crosshair while firing or automatically reload the HK after firing. A delay on the firing mode change would break scripts that 'skip' a firing mode. Like i wrote a script that skips the burst mode on the g36, since its pretty useless.
i would prefer the options that only stop this exploit. So "removing" the spread reset on firingmode change would be the best way i can think of. You probably could just add a spread to the firingmode change, since noone that uses it in a common way would toggle it that often or while firing that it would create problems.
Please consider this :)
totally agree that its an exploit though, i just like scripting. :)
Though i wouldnt like to see +attack to be removed from scripting. (-attack could be totally removed then...):
this would also break scripts that change the crosshair while firing or automatically reload the HK after firing. A delay on the firing mode change would break scripts that 'skip' a firing mode. Like i wrote a script that skips the burst mode on the g36, since its pretty useless.
i would prefer the options that only stop this exploit. So "removing" the spread reset on firingmode change would be the best way i can think of. You probably could just add a spread to the firingmode change, since noone that uses it in a common way would toggle it that often or while firing that it would create problems.
Please consider this :)
Sorry for my bad spelling - I am still asleep. :)
|=| Iye's UrT Addon |=| Firefox Personas |=| Maps |=|
http://www.mediafire...vk3a602hcfg.jpg
|=| Iye's UrT Addon |=| Firefox Personas |=| Maps |=|
http://www.mediafire...vk3a602hcfg.jpg
#5
Posted 29 May 2014 - 10:42 AM
Yes, but additionally to making fire unscriptable, also an ingame delay (equal to spread cooldown or burst delay) should be added to the gunfiremode change, as Barbatos said, because some people use programable keyboards/mouses that allow macros (like external scripts) to be assigned to keys/buttons.
This post has been edited by karnute: 29 May 2014 - 10:46 AM
Advertisement
Page 1 of 1
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement