Writing Macros

[Thorny]

I would very much like to see my sample macro duplicated with Windower. I'll give you a hint, it isn't this:

/p {Gather Together} {Protectra} {Shellra}
/target <st>
/console exec ProShell.txt

input /ma "Protectra IV" <me>;
input /equip "Main" "Seveneyes";
input /equip "Head" "Selenian Cap";
input /equip "Body" "Goliard Saio";
input /equip every other macro piece you wouldn't have space for normally;
wait 8;
input /ma "Shellra V" <me>;

[Mojo]

That's not exactly using a Windower macro lol

[Cymmina]

/p {Gather Together} {Protectra} {Shellra}
/target <st>
/console exec ProShell.txt

input /ma "Protectra IV" <me>;
input /equip "Main" "Seveneyes";
input /equip "Head" "Selenian Cap";
input /equip "Body" "Goliard Saio";
input /equip every other macro piece you wouldn't have space for normally;
wait 8;
input /ma "Shellra V" <me>;

That's still using FFXI macros, try again. I can't bind that.

[Thorny]

Who cares if you can bind it? It serves the purpose by allowing you to do your wait and have additional lines as a windower macro would allow. Arguing windower vs ingame is blatantly retarded, the goal is to get your macros working the way you want them to.

[ZhiGaruda]

That's still using FFXI macros, try again. I can't bind that.

Most people use windower scripts for the purpose of doing things you just can't fit in FFXI macros, or for executing further scripts and the like. Stop being stupid. Thorny's example is spot on.

[Mojo]

Binding is huge, it bypasses a few processing layers. Bound macros execute quicker and never lag out. If you've never bound your macros before, I suggest that you try it, as unbound windower macros are barely a step above normal FFXI macros.

[Cymmina]

Who cares if you can bind it? It serves the purpose by allowing you to do your wait and have additional lines as a windower macro would allow. Arguing windower vs ingame is blatantly retarded, the goal is to get your macros working the way you want them to.

I'm arguing nothing. I am simply pointing out that it is foolish to just say "use Windower scripts" when they can't replicate everything a FFXI macro can do. It's not always about about additional lines, you know? If you need to swap more than 5 pieces of gear, there's Spellcast for that. Let's be honest, not many people are wanting extra lines in their macros so they can cast more than 6 spells.

My main macro set for SCH is full and I need the extra macro space without swapping macro sets for things like Stoneskinga and Phalanxga that I cast regularly in places like Nyzul where people just run off when they get to a new floor (no, my macros can't be rearranged because they were carefully laid out to be as familiar as possible between WHM, RDM, and SCH). Windower scripts can't solve that because the macros I wish to bind to additional keys are impossible at this point in time. My G-keys would have made a lovely spot, don't you think?

So yes, being able to bind *does* matter to me.

[fishstix]

Even if you could use notepad to open up the ffxi files and manually edit it, notepad is a 3rd party program, so just use POLutils lol

[Wrish]

Hey now. Argument was never about using scripts exclusively.

You can't bind stuff without Windower. You can't use spellcast without Windower. Amirite?

OP seems to have ethical issues about installing Windower... I'm in the same boat.

[Feedmenow]

Binding is huge, it bypasses a few processing layers. Bound macros execute quicker and never lag out. If you've never bound your macros before, I suggest that you try it, as unbound windower macros are barely a step above normal FFXI macros.

Yeah, I love how I've set up my bindings with the Autoexec plugin and Windower:

My current setup for usage with the numberpad:

Spoiler: show

Starting binds:

Spoiler: show

bind numpad9 Macro9;
bind numpad8 Macro8;
bind numpad7 Macro7;
bind numpad6 Macro6;
bind numpad5 Macro5;
bind numpad4 Macro4;
bind numpad3 Macro3;
bind numpad2 Macro2;
bind numpad1 Macro1;
bind numpad0 Macro0;
bind numpad/ Macro/;
bind numpad* Macro*;
bind numpad- Macro-;
bind numpad. Macro.;
bind numpad+ Macro+;

And a counter-acting script to unbind everything. Add in another script:

Spoiler: show

Alias switch on;
Alias on alias switch off; exec startbits.txt;input /echo ==Bits are on==;
Alias off alias switch on; exec endbits.txt;input /echo ==Bits are off==;
Bind Pageup switch;
switch;
switch

And I can use the numpad whenever I want by hitting pageup to toggle the bindings on or off.

Standard job-specific binding (my syntax is under the assumption that I'm running spellcast):

Spoiler: show

alias Macro9 sentinel;
alias Macro8 Box step <t>;wait 1;Animated Flourish <t>
alias Macro7 flash <t>;
alias Macro6 rampart;wait .1;sc set mdb
alias Macro5 cure4 <stpt>;
alias Macro4 input /ma "Cure III" <stpt>;
alias Macro1 Curing Waltz II <me>;
alias Macro2 Healing Waltz <me>;
alias Macro3 Aspir Samba;
alias Macro0 sc set idle;
alias Macro. sc set hastemelee;
alias Macro+ reprisal;
alias Macro- atonement <t>;
alias Macro/ Shield Bash <t>;
alias Macro* sc set town;

And finally my autoexec XML to automatically set everything up when I log in or change jobs:

Spoiler: show

<?xml version="1.0" ?>
<autoexec>
<!-- This is an autocreated AutoExec file. the next line is commented out and not going to be ran, its to show an example on how to add commands to this file. -->
<!--register event="login" silent="true" runonce="true">load expwatch</register-->
        <register id="1" event="Login_Feedmenow">exec bitstoggle.txt;</register>
        <register id="2" event="Jobchange_BRD/WHM|Jobchange_BRD/BLM"> exec brdbits.txt;input /echo == BRD Macros Loaded ==</register>
        <register id="3" event="Jobchange_BRD/NIN"> exec brdnin.txt;input /echo == BRD/NIN Macros Loaded ==</register>
        <register id="4" event="Jobchange_BRD/SCH"> exec brdsch.txt;input /echo == BRD/SCH Macros Loaded ==</register>
        <register id="5" event="Jobchange_PLD/WAR"> exec PLDmain.txt;sc group dynamis;input /echo == PLD settings Loaded ==</register>
        <register id="6" event="Jobchange_PLD/DNC"> exec PLDdnc.txt;input /echo == PLD/DNC settings Loaded ==</register>
        <register id="7" event="Jobchange_PLD/NIN"> exec PLDgods.txt;input /echo == PLD Gods Macros Loaded ==</register>
        <register id="8" event="Jobchange_WAR/NIN"> exec WARnin.txt;input /echo == WAR/NIN Macros Loaded ==</register>
        <register id="9" event="Jobchange_WAR/SAM"> exec WARsam.txt;input /echo == WAR/SAM Macros Loaded ==</register>
        <register id="10" event="Jobchange_WAR/THF"> exec WARthf.txt;input /echo == WAR/THF Macros Loaded ==</register>
        <register id="11" event="Jobchange_WAR/DNC"> exec WARthf.txt;input /echo == WAR/DNC Macros Loaded ==</register>
        <register id="12" event="Jobchange_WHM/BLM"> exec WHMblm.txt;input /echo == WHM/BLM Macros Loaded ==</register>
        <register id="13" event="Jobchange_WHM/SCH"> exec WHMsch.txt;input /echo == WHM/SCH Macros Loaded ==</register>
        <register id="14" event="zone_Dynamis*|zone_Ru'Aun_Gardens|zone_The_Shrine_of_Ru'Avitau|zone_Ve'Lugannon_Palace|zone_Al'Taieu|zone_The_Garden_of_Ru'Hmet|zone_Grand_Palace_of Hu'Xzoi|zone_Apollyon|zone_Tenemos">ll profile Defiance;</register>
        <register id="15" event="zone_Xarcabard|Zone_Beaucidine_Glacier|zone_Windurst_Woods|Zone_*_[S]">ll profile default</register>
        <register id="100" event="Logout_Feedmenow"> exec endbits.txt;input /echo == End Macros Loaded ==</register>
</autoexec>

Planning on adding a more bindings and aliases to toggle some spellcast variables and groups at some later point.

[Dammerung]

Who cares if you can bind it? It serves the purpose by allowing you to do your wait and have additional lines as a windower macro would allow. Arguing windower vs ingame is blatantly retarded, the goal is to get your macros working the way you want them to.

No, you're missing the point. You CANNOT replicate /target <st> as a pause function with ONLY a windower script - because the script won't pause at /target <st>.

[Deader2818]

If you really want to get that technical, you can't even run a windower script without using a FFXI macro.

[Dammerung]

If you really want to get that technical, you can't even run a windower script without using a FFXI macro.

False. You can bind keys to run scripts, and you can type in the console to run the script as well. I'm not going into spellcast.

[Aikar]

I personally use Yekyaa's macro editor (FFXI ME). While I don't particularly care for some of the behavior/UI, I preferred it to POLUtils. His site appears to be broke at the moment (<3 PHP):

http://ffxime.faservers.net/

Hey that has nothing to do with PHP -.- He's missing files after Vega moved his servers and Yekyaa never restored it, not a PHP problem >_>

[Takedown3]

man i got off the boat before all this cool shit like binding and xml came out, looks like some very efficient gear swapping is available now

[Aikar]

If you really want to get that technical, you can't even run a windower script without using a FFXI macro.

I type //cure3 and about 40+ input /ma and /equip lines go off

[Deader2818]

Well then, I will admit I don't know much about macros then or spellcast.

But either, get windower, no reason NOT to use it.

[Wrish]

It's a slippery slope. And an ethical issue. And breaking the TOS. Countless people have slipped and gotten caught by SE. People make assumptions that SE can't detect it. Assumptions that SE won't change its policy on who it catches.

It's a luxury, not a necessity. I do fine without it. Gameplay that you can accomplish with Windower, but that I can't, is achievable with the use of very questionable methods. And it takes time to set things up, and patience to wait for windower updates when a patch breaks things. That's all time I spend progressing in the game. Instead of rebuilding an account that got caught for going a little too far.

[Kohan]

It's a slippery slope. And an ethical issue. And breaking the TOS. Countless people have slipped and gotten caught by SE.

Yeah, you're right. That's why those massive amounts of people who were banned a while back were associated with Windower usage, right?

Oh, wait.

People make assumptions that SE can't detect it. Assumptions that SE won't change its policy on who it catches.

You're rather good at making assumptions yourself. You really seem to believe you know how SE thinks. Why, when it comes to that, you are simply the bee's knees! Except not, because you're pulling this nonsense out of your ass as spectacularly as the people you're vilifying.

It's a luxury, not a necessity. I do fine without it. Gameplay that you can accomplish with Windower, but that I can't, is achievable with the use of very questionable methods.

What the fuck kind of statement is that, even? "Things that you can accomplish through questionable methods, which I can't, is achievable through the use of questionable methods"?

And it takes time to set things up,

Copying and pasting in text files and XML is hard.

and patience to wait for windower updates when a patch breaks things.

Since everyone who uses Windower stops playing completely when a patch breaks it.

That's all time I spend progressing in the game. Instead of rebuilding an account that got caught for going a little too far.

Too bad you'll never be as effective as the Windower users, bucko. Enjoy your self-righteousness. I hope it keeps you company when you're sucking cock all alone.

[LordTrey2]

OP seems to have ethical issues about installing Windower... I'm in the same boat.

Time to get over those issues. Windower makes FFXI 10000x more tolerable. Try it, love it.