I am looking for a way to use zoc buttons to re-write the zoc Fkey macros the same way that revhelper rewrites the zoc buttons.

Mostly needed for the attack macro's seeing as how every ship in every game has different max figs per attack.

Maybee rev's _menu.zrx can do the macros also?

Or perhaps...does anyone know how to make a batch file that replaces lines of txt in other files...then I could just make zoc buttons for those batch files.

i use a simple REXX script to rewrite my Fkeys

quote:Originally posted by PHX

Or perhaps...does anyone know how to make a batch file that replaces lines of txt in other files...then I could just make zoc buttons for those batch files.


I think this has been cover'd before..
your wanting FKeys .. so
so you should look up ZocGetOption() and ZocSetOption()

ex
value1 = ZocGetOption(Fkey#00)
or
Call ZocSetOption "Fkey#00=ay9999^^M"
Call ZocSetOption 'Fkey#00="Ay9999^M"'

I think that should be the info your really wanting (note, I think scripts are something like ^Run=Scriptname

you CAN just save the whole keyboard layout too and change that.. Anyhow the help file with zoc has everything you need to know (back up your settings file before you muck about with these types of scripts"

Thanks Doc...now I can change all attack Fkey macros in about 2 seconds. Have everything set from 1k, and every 5k up to 60.

what is a macro?

Also known as a burst.

A string of commands sent to the game simultaneously. In this case...pressing F1 in zoc would send

"ayy25000^M" .....for those of you who have not read res's documentation or just never thought of it, 2 y's in case there is a beacon in the sector....and actually...put a space after ^M

Be careful about the yy, you can end up shooting a fed that way. Something like ayz9999^m would be better.

This is true...so to make sure that don't happen..know...if a fed is in the sector he will always be the first target...so you better hit F2 instead.

anyy25000^M

ayz9999^m would work but then your back to getting hung up on on beacons again.

No you don't. You just pound your macro twice. ayz9999^m will kill the beacon and leave you at the command prompt. If there is a fed in the sector and a beacon, you'd need annyy25000. I find it easier to just make my macros so I don't have to worry about it at all, but that's just me, I guess.

lol, i knew someone would answer, hehe. beware of playing the MAC game with a fed in sector as they can leave just as fast as they come in. ayy.. ya, res told me to use that, and the first time i did zyrain popped my Butt, heh, i have NEVER been held up by a beacon in sector, so i avoid the whole yy personally. sure, a beacon would screw me up, but i see feds a whole lot more. also not knowing what macro you are hitting or what it is going to do is just as safe as running a script afk, it will get you killed.

Slim

quote:Originally posted by Slim Shady

lol, i knew someone would answer, hehe. beware of playing the MAC game with a fed in sector as they can leave just as fast as they come in. ayy.. ya, res told me to use that, and the first time i did zyrain popped my Butt, heh, i have NEVER been held up by a beacon in sector, so i avoid the whole yy personally. sure, a beacon would screw me up, but i see feds a whole lot more. also not knowing what macro you are hitting or what it is going to do is just as safe as running a script afk, it will get you killed.

Slim


You have never played against good players if a beacon hasnt ever been there.

A little research on how things work and you CAN make a macro that is safe for attacking spot 1 AND it will kill beacons AND it wont fire at fed.

Personally my spot1 attack would look something like
AYN Y0^M AY9999^M
If I wanted to avoid fed, Kill beacons, and attack spot 1..
Mines make the macro longer .. as would quasars.. So I am not giving a sector entry macro ..

I aint fully sure that macro will work but I know I have made them before..
I think it's important to note that attacking someone with 0 figs will break the attack cycle AND do it with no delay .. In essence it's not going to cost you a large 250ms wait.