Well, perhaps it was a 2-round burst for me because I'm running the game at 15-25 FPS (5-9 during explosions) because DICE didn't put low enough settings in for the game to be laptop-friendly like other developers do.

As far as having the gun automatically fire, yes, that would be easy. I don't know why I never thought of it.

And now it is up.

thank you very very much
this is EXACTLY what I wanted

I loved rolling the xm8 with single fire mode
infact only about 5 minutes ago I had 25 killstreak with my xm8 on nelson bay

until select fire is implemented in the game I will use xm8 (ump-45 ns-2000 too but they are irrelevant )
if the game gives me the option to single fire the abakan, then Id use abakan
but as that 2nd bullet wil never hit enemies far away and add extra spray, meh

thanks again

I have another idea; I know it would work but I dont know if it would be comfortable enough to use.
can a script be made so that after mouse 1 is pressed nothing will happen for 25 ms after that mouse moves somewhere around 5-15 pixels relatively -y
this should be equal to the ammount of an-94's recoil so that the second should would have a better chance of hitting those targets really far away (when the second shot cannot possibly hit because of the recoil)

so if someone can make a script such as:
caps lock: toggle
mouse 1 is bound to:
mouse1
Xms delay
mouse moves relatively X pixels direction:-y (I can figure out the exact value that X needs to take if you do not want to bother, the template of the script will do)
Yms delay
mouse moves relatively X pixels direction:+y
Zms delay
mouse 1 should be unusable for A ms (so that accidentally double tapping etc. mouse 1 wont take the mouse -y 2X)

I'm not entirely sure what you're saying. Do you mean like a mechanism that makes it so if you accidentally click twice, the second click does nothing? Also, yeah, include that value of X in your reply please.

I cannot know the values of X etc right now
if you give arbitrary values, I can test it myself and find the proper values then Id post the script with proper delays/pixels

also what I meant was:
while the script is active; when mouse button 1 is clicked, mouse button 1 should be disable for certain ammount of time
for example I clicked mouse button 1 while the script is active, script started to do its thing, I must be INABLE to press mouse button 1 and mess up the sequence (I can physically be able to press it ofc. but the script be written so that for a certain ammount of time nothing should happen when mouse button 1 is pressed)

Well, that SetMouseDelay part of the code already handles that. It is the amount of time that the computer spends ignoring your left mouse click. As far as messing up the sequence, that isn't possible. It runs so quickly that you can't click fast enough to screw with it or anything.

battlefield.Cadeyrn1 wrote:Well, that SetMouseDelay part of the code already handles that. It is the amount of time that the computer spends ignoring your left mouse click. As far as messing up the sequence, that isn't possible. It runs so quickly that you can't click fast enough to screw with it or anything.

the problem is: if mosue button 1 is clicked before the "third shot" (first burst is fired now its time for second burst) script will move the mouse up and down etc where the gun doesnt actually fire anything
because I also had scripts for mw2, and if you would click the button before the script has finished then the whole suff would be messed and stupid things used to happen
isnt it possible to add disable mouse button 1 for hmm say 120 ms
I think there is a disable button code, because I think there were "disable windows" key in auto hotkeys manuscript (I couldnt comprehent the whole stuff so I sort of gave up)

SetMouseDelay already disables mouse button 1 for whatever amount of miliseconds you set. And as far as I can tell, it's the only option. My first choice when coding that script was to disable the mouse rather than set a delay, but AutoHotkey does not have a disable mouse button feature. The closest thing it has to that is disabling the input, which means no mouse or keyboard at all, including moving the cursor/aiming the gun.

okay then that would be fine too

No, you don't understand. The mouse button is already being disabled for, in your case, 250ms after you click it. If there's a big extra recoil with the AN94, then there's nothing the script can do. It's probably a problem with the game, as I find all the full-auto and burst-fire rifles in BC2 will have a recoil effect that doesn't start until half a second (maybe slightly less) after the last bullet was fired, and it does feel pretty damn weird.

battlefield.Cadeyrn1 wrote:No, you don't understand. The mouse button is already being disabled for, in your case, 250ms after you click it. If there's a big extra recoil with the AN94, then there's nothing the script can do. It's probably a problem with the game, as I find all the full-auto and burst-fire rifles in BC2 will have a recoil effect that doesn't start until half a second (maybe slightly less) after the last bullet was fired, and it does feel pretty damn weird.

there is a recoil after the first bullet, after first bullet is fired mouse should lower few pixels in -y direction then after 2nd bullet is fired +y direction
recoil doesnt that that much to take effect, if you write a script of the sequence I have written, (with arbitrary values) I can test and find the values which would work myself

EDIT:
okay Ill make some assumptions and write down the script in detail with estimated values (which can be perfected afterwards by testings)
capslock=toggle
mouse 1 is bound to:
send mouse 1
delay 75 ms
mouse moves 10 pixel in -y direction
dealy 75 ms
mouse moves 10 pixels in +y direction
delay 10 ms

Oh, now I see what you mean. Yeah, I can do that easily, and I'll let you find the values yourself.

EDIT: Finished. Here's the link again: http://code.google.com/p/bc2-single-fire/

And read the two paragraphs after "ADDITIONAL:". There's a guide and an advisory in there.

EDIT2: Whoops, I set the mouse movements to 20 pixels. I'll let you change it.

mouse moves very slow (REALLY slow)
isnt there an "instantaneous" movement?
I would actually want a very fast movement rather than instantaneous but this way, it is very very slow

and that movement actually disables any other mouse movement (if I slide mouse right for example, mouse teleports back to the coordinate that I initially clickled it *or someplace below/over it depending on the movement etc.")

Well, for instantaneous movement, delete the 50 and its comma and space altogether. For faster movement, raise it to a higher number. As far as the mouse locking thing, that's a limitation of AutoHotkey that I can't work around. Sorry.

i already had the pleasure to meet cheaters on some servers -.-