@ MerCyKiL:
Protip: The "attack" command will interrupt the current attack sequence, regardless of if it is within a sleep or not.
But yes, in SVN/next version, you can set the # of rounds for each burst on automatic weapons via the menus/commands.
All weapon attack/switch actions happening outside of key binds are ignored. (The various mouse buttons are considered "keys") --- The only special case that I know of is the attack command being executed within a sleep. It has some special effects.
Which means there is no script that can fire for you. There are scripts that can *stop* firing for you though. ;)
Protip: The "attack" command will interrupt the current attack sequence, regardless of if it is within a sleep or not.
But yes, in SVN/next version, you can set the # of rounds for each burst on automatic weapons via the menus/commands.
(16 Jun 13, 03:48AM)Waffles Wrote: afaik it is intentionally disallowed because a script should not be able to fire your gun for you.
All weapon attack/switch actions happening outside of key binds are ignored. (The various mouse buttons are considered "keys") --- The only special case that I know of is the attack command being executed within a sleep. It has some special effects.
Which means there is no script that can fire for you. There are scripts that can *stop* firing for you though. ;)