Question: I remember you’ve posted some lua months/year ago, maybe SCH was your 1st. Anyway, how many jobs-lua files have you done so far ?
All of them following the same construction and functionalities ? (Like auto-carmine legs+1 when moving for applicable jobs)
Im asking because I like to have consistency in the different job-lua files so that I follow the same keybinds, etc. Without having to say to myself « how no this job lua is not like the other one, I have to press window+r to equip the carmine legs+1 with this job »
I've only done the jobs I play regularly. SCH, RDM, GEO and SMN, Outside of SMN which is quite different. The sch Lua was the base on which the geo and this one were built so they are quite similar. They use the same style of keybinds and UI. However, they aren't all up to the same exact functionality.
I never intended to make a full suite like Selindrile's, just sharing the Lua I made for my use so others can enjoy them.
That being said, as far as keybinds goes, they are listed in the same file you put your gear into. (RDM.Lua) So you can change them to fit what your muscle memory gravitates to.
How to unload all the features called by your lua ?
I switched to another job which lua isnt based on same as yours, and when I press F8 button to target NPC, I got an error message, and I still have to press the Window key+F8 to target npc (as per your lua)
That's on purpose, and why I commented out the gear pulled out of there as that would be different for everyone. Unless I missed out on commenting some.
That's cause Carm.Head.D means nothing if it isn't defined, other than letting you know I use that gear there. I commented it because as you just found it errors out.
I actually assign Carm.Head.D to something.
Carm.Head.D = { name="Carmine Mask +1", augments={'Accuracy+20','Mag. Acc.+12','"Fast Cast"+4',}}
I was trying to use an alias for the gear like you did but didn'T seen to work.
Ah yes casting them into a variable won't work in the current way it's done cause that cycler is taking the inputs as string, not variables.
BUT, the cycler for weapons are only for idle / engaged. (that's the only time this is checked)
Looks like your Grio is for casting so technically, you should put them in the relevant midcast sets and that should swap correctly (as long as you didnt lock weapons) and then it will swap back to the weapon in the cycler list that is currently selected after cast.
Hello Elizabet,
I'm using it and its awesome.
Thank you for sharing it.
I hope you gona make more for other jobs.
Somehow I have an issue w Utsusemi.
It doesn't equip the precast set for me.
I had to set specific precast sets for them.
I'm also suggesting to add an Auto cancel shadows if up when casting utsusemi Ichi.
That would be really awesome.
What ive found confusing was the "Match SC Element" would be simpler to just call it "Magic Burst".
If i see anything else i will let you Know.
What ive found confusing was the "Match SC Element" would be simpler to just call it "Magic Burst".
Well, I suppose. But It's not like the typical "cast in Magic Burst gear" toggle. As it will temporarily change your saved element that goes into the casting macro. The fact that during the SC window the casting set automatically goes into MB mode is just cherries on top.
Now after im using it a bit longer i understand what you want to say with that.
I agree w you to leave it that way, its perfect.
Gona setup the SCH one next.
Thx again, your doing this perfectly.
You mentioned that you would like to have help w AM etc up for testing.
Let me know if i can help you w that.
Cheers