[FS |HSO|RaideR]

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

[Mingus]

yeah!!! I had been waiting for this since long time ago

Regards

[Mod Iye]

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 :)

[fr.Biddle]

We normaly shouldn't be removing "attack" (fire) from scripting. We will just make it impossible to shoot continuously while switching weapon modes.

The problem of this bind was that it made shooting ignore the spam/burst delay on guns, especially the UMP.

[karnute]

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

[FS |HSO|RaideR]

Barbie's comment is valid and is most likely what we will do.

BK / RaideR response is allways a little harsher than that needed. If Barbie can do it to a point where we dont care any more with a delay mechanic that is fine.

Thanks

R

[Kolossus]

Good news. Keep up the good work, FS!

[FS Barbatos]

A delay of 800ms has been added between 2 weapon mode changes. This will take effect in 4.2.019.

[SilverFoxZ]

Barbatos, on 31 May 2014 - 11:09 PM, said:

A delay of 800ms has been added between 2 weapon mode changes. This will take effect in 4.2.019.

What about a kewl 800ms animation for that? :3

[`Lv.niima]

Barbatos, on 31 May 2014 - 11:09 PM, said:

A delay of 800ms has been added between 2 weapon mode changes. This will take effect in 4.2.019.

Ok nice, but when we have the new version (4.2.019) and especially the new banlist? : D