Bushido - The Way Of The Samurai (A Guide) V. 2.0

Requiring a mountain of evidence, hours of logging raw data and spreadsheeting, aka work, before believing anything anyone says is also a bit.. let's go with disrespectful.

If absolute proof is so important to you, and think that what multiple people say is wrong, maybe go out and do your own testing to disprove it.

I've never been able to get good damage out of refulgent arrow, even on a job like RNG. The reason Empyreal ends up being good is because it has a 2x attack modified as well as scaling TP mod. Obviously a 2x attack modified won't matter on trivial things, but if you're on sam for an odyssey fight, it's very very good.

Also, that is where Ullr shines, when you aren't attack capped.

Okay I'm bored, please don't make me keep doing this..

Regarding Unity TP Bonus.

Firing Distance: 15 Yalms
Target: Wild Wabbit

Average 29725
UNM GK, Mpaca Head, Tenzen Bow, Moonshade= 1950 TP Bonus
Weapon Skill at 1100ish TP = 3000ishTP

Average 23,902
Mpaca Head, Tenzen Bow, Moonshade= 1450 TP Bonus
Weapon Skill at 1100ish TP = 2500ishTP

1000TP
Average:12695
*Sekka Used to get baseline. No TP Bonus Used

Edit: Quick edit to typo. Meant to list 1950 and 1450 as total TP Bonus.

Got a SAM earring+2 but got shafted with 3% WSD/7 STR. Decided I will still use it over Thrud for all the accuracy.

At this point:
sub="Utu Grip",
ammo="Knobkierrie",
head={ name="Nyame Helm", augments={'Path: B',}},
body={ name="Sakonji Do. +4", augments={'Enhances "Overwhelm" effect',}},
hands="Kasuga Kote +3",
legs="Wakido Haidate +4",
feet={ name="Nyame Sollerets", augments={'Path: B',}},
neck={ name="Sam. Nodowa +2", augments={'Path: A',}},
waist={ name="Sailfi Belt +1", augments={'Path: A',}},
left_ear={ name="Moonshade Earring", augments={'"Mag.Atk.Bns."+4','TP Bonus +250',}},
right_ear={ name="Kasuga Earring +2", augments={'System: 1 ID: 1676 Val: 0','Accuracy+16','Mag. Acc.+16','Weapon skill damage +3%','STR+7 DEX+7',}},
left_ring="Cornelia's Ring",
right_ring="Epaminondas's Ring",
back={ name="Smertrios's Mantle", augments={'STR+20','Accuracy+20 Attack+20','STR+10','Weapon skill damage +10%','Damage taken-5%',}},

Assuming capped attack then Emp+3 feet are going to beat Nyame R25 feet always right?

would you even need to worry too much about acc on a single hit WS since they have an innate 100~ acc on them assuming you're already at acc cap. Also isnt mpaca head the general go-to for WS? Unless its hybrids. Though if using aeonic and overflow i could see it being wasted potentially if there's not an auto-check in the lua

Hmm, probably not but 3 STR isn't going to add that much and I do have more acc on body+4 and legs+4 now than when I had Nyame already so probably don't need the acc at all. I'll tell myself the STP on WS is worth it!

Mpaca helm is norm but I leave Nyame default and toggle Mpaca.

My question is about feet.

I also suppose Sroda would beat Epam ring at this point but not willing to drop 18M for it for one job atm.

ItemSet 379403

Nyame feet for uncapped att. Nyame body if I can't WS from the front. Nyame head swaps in at 2500 tp.

Show me the logic you are using for head, I couldn't get it working. I'm not going to change ring either.

Since I don't have Nyame R30 then legs are 1%WSD on relic+4 vs 9 STR on R25 Nyame. Guessing this is negligible.

isn't it just if spell type == weaponskill and player.tp (<|>) [amount] then equip whatever

my logic just combines the relevant set with the specific slot i want to add

Saying it's easy without giving the actual solution helps noone. I tried one I saw on ffxiah somewhere before but the logic didn't work, think others said it didn't work for them either.

I can tell you the logic I use to swap certain pieces when above a certain threshold of TP in my lua, but I'm not sure it's gonna help you and, likewise, I'm not sure it's the best way to do it.
It's just the way I do it, developed this logic ages ago and it always worked for me.

First, I define a variable called TPthreshold.
Its value changes according if I'm using Doji or not.
Technically I have two variables on SAM, for 2 different TP threshold (one swaps just moonshade, the other swaps earring and head), but I think it's the only situation. On all my other jobs lua where I bother with tpthreshold, I normally have a single variable and a single set (moonshade is the only thing I swap)

Then somewhere in my "get_sets" I define a custom set.
Like for instance the two I use on SAM

Then I do something in my precast.
My precast normally has a single chained if inside.
"If action is a spell equip this set
Elseif action is a ja, equip the proper set
Else if action is blahblahblah, equip the proper set
End"

Normally my precast function ends right after that.
When I want to handle tpthreshold I do a second, separate if.
This "if" is inside the precast function, but comes after the main "if" (the one I described above). It's not chain inside it, it's a second, separate "If".
This is mine for sam


Basically the first If, the long chained one, equips the proper set.
If it's a WS we're talking about, it will equip the relevant WS set, which by default includes Mpaca helm and Moonshade earring.
Then, separately, it checks for my current TP value.
If it's above a certain threshold, it equips a different set which is empty except for the 1-2 relevant pieces I want to swap.

Gearswap doesn't equip sets the second they get processed into an if, the packet to equip them gets sent to the game after the precast function is over.
This means that my two ifs will be combined into a single set, and a single "equip" packet will be sent to the game after the precast function is over.



Soo... I dunno if I explained myself to you and I'm sure there are way better and more efficient ways to do it, but this is the way I've been doing it for all these years.

I don't see where the TP values are defined there.

I don't see where the TP values are defined there.

You can pretty much define them wherever you want, but I do it at the beginning of the lua, inside the Get_sets function


I also had another function that changed this value whenever I swapped weapon to a non Dojikiri Yasutsune GKT but it's currently on hold because it's the only GKT I use atm.
I guess... technically you would want to swap these values if you swap, say, from Dojiri to Shining One.
Shining One doesn't have the +500 TP bonus.

But the values you put inside the variables are completely arbitrary and you can put whatever you want according to your needs, your gear, your weapons.
What's important is the logic in how these variables are used.
The values contained inside are not really that relevant.

For Doji wouldn't you need to swap out at anything over 1950? I'd probably set it to 1800 to be safe since over TPing is super common, and 2200 or so for Masa. I will try it this way later.

I mean there's only so much I can pretend to do for you without knowing what your lua looks like to know why your logic failed.

Currently not home so I can't copy paste my list, but the example I gave isn't particularly far off from Sechs. His uses predefined variables for the thresholds but you could set those yourself in the line instead of said variable.

This could then be spread out into if/if else statements or nested statements based on your needs.

I personally just have a catchall for weaponskills rather than specific tachi(name), so:


or something along those lines; I'm going strictly off memory atm. change to 2500 if you never use doji, or alter the threshold to meet the criteria you prefer, right? Mpaca is 200, moonshade 250.

I actually might still do that in some of my jobs lua, because I don't need to change those values on the fly, they're always the same, so might as well put them straight in the line without use of any variable.
I know for sure this is how I used to do it initially, years ago.
On some jobs I had to change this and use a variable for the simple reason that this value is not always the same and changes according to the weapon I'm using, so I need to dynamically change it (with a custom function somewhere else or whatever).
This way the logic remains exactly the same but I don't have to go and manually edit a plethora of values in the lua.

But yeah, same deal. Using numbers instead of variables is way more straightforward and, as I mentioned before, I'm sure on some of my luas I still handle it that way lol