All Jobs Damage Simulator And Gear Sets

Aminon reportedly has 1774 evasion and that checks out with the ws acc I needed to land WSs (eyeballing). The basement bosses are in the 1550-1620 range depending on the boss, I forget the exact values.

As for defense, yeah I have no idea.

If you can hit sortie basement bosses you're way over cap for V25 so they're for sure less than 1550. I wouldn't be shocked if they were under 1400 evasion too. Xevioso might be the exception, but wiki lists V20 as 1375 ACC needed to cap so I doubt it.

Wow. Thank you very much, lol. I should have known someone would have made an addon for this.

Yeah, didn't think to try this until today. I ran the program on my laptop and it runs fine because the recommended default scale is 125%, compared to my gaming monitor which is 150%. The program is likely defaulting to whatever Windows recommends by default.

I am glad to know I can use the program fully in some way in the mean time.

Using latest version on BRD/NIN and while optimizing WS set it keeps selecting Linos DA QA as BiS option for Savage Blade.
No option is selected in the Range slot.
If I only pick "Empty" same result.
If I select "all" it still says the best option is Linos DA/QA.

Thing is... if I pick no option and/or Empty in the Ranged slot, it should prioritize what I picked in the Ammo slot and tell me what is the best option there, it shouldn't pick something I haven't selected like the DA/QA Linos in the Ammo slot.

Unless I'm doin something wrong? But it didn't use to behave like this at least a few versions ago.


Edit:
Also for the TP set as /DNC it would leave me with ZERO dw from gear.
Just HM and Haste2 as haste sources, no haste samba.
Something is broken, never had such conflicting results the last time I used it a few months ago.

Thanks for the note.

There was previously an issue with the "select all" buttons not properly automatically selecting/deselecting gear after I pushed the virtualization update last week. I believe this may have been related to the software seeing the Linos despite it not actually being a selected option. I've also adjusted how the code handles initializing the gearset when finding the best set, but this part of the code hasn't been updated since September last year, so it is unlikely to be related. Let me know if you still see this issue after updating. I have not been able to reproduce it since the fix, so I'd need more details if it's still a problem.


I haven't been able to reproduce BRD/DNC returning sets with no dual wield. Maybe that set was coincidentally the best set given the options (high DT and accuracy requirements together?).



Other news from last week:

Gear selections have been virtualized: We now build a maximum of 1024 widgets to represent all gear in the gear.py file. This was previously around 8500, which caused tkinter to struggle to update everything when making selections such as job changing. Instead of hiding/placing 8500 individual widget objects for every selection, the GUI now simply changes a text label on 1000 already placed widgets. This should have fixed the issue with the GUI breaking after the December 12 rewrite update (which resulted in missing buttons and an inability to use menus/selections). Ideally, we'd reduce this down to ~100 widgets later, but 1000 should be good enough for now.

It was weird.
Condition set was "time to WS", no DT or any other requirement.
I can totally see how skipping some points from Capped Attack Delay (i.e. missing some DW) can still produce a BiS set even with uncapped DW, but missing ~21% sounds a bit too much, considering there was "just" capped magic haste, no JA haste, no other buff providing anything similar.

I wasn't complaining btw! Was just trying to find whatever it is that was broken!

new version working so much better. is there a post/link you can share on how to add monsters(would like to add the Sortie bosses).

Hi Izanami, new version giving me no issue at all with the selection thing.
I still get the no dualwield gear on BRD/DNC.
Which is possible but it sounds very unlikely to me?
More DW to get close to Att Delay Cap progressively slows the Tp/hit, and the metric here is "Time to WS".
Still, in spite of that we're talking about /DNC not /NIN, means 21% DW to cap att delay at capped magic haste.
I could see being like 5 or 6 or even 10 away from DW cap might be better, but 21% sounds too much?
I could be wrong of course.

Here is the setup I used:

BRD/DNC ML50

Buffs
GEO: Indi Precision, Geo Torpor (Bolster)
COR: Rolls+8, 9 Chaos, 8 Sam (Crooked, Lightshot)
BRD: Songs+9, HM, BM, Minu5-4-3 (Marcato)
WHM: Dia2, Haste2
Food: Sublime Sushi+1

Gear:
I left gear with no options, except cape, waste and earrings where I turned on pretty much anything minus a couple of things I wanted to exclude.

The result tells me Brutal+Cessance+Sailfi+1R15+NullCape is the Best.
Suppa is 0.6% below, Eabani 1.8% below, Reiki 1,4% below, JSE cape with DW10 doesn't even appear in list.


It feels to me something is strange but, as I said before, maybe it's actually correct?




I might have found something:
Even if I remove Haste and Honor March entirely, in the Player Stats section my Magic Haste still appears at 55% and gear haste at 29%.
I think there's something wrong somewhere?
And are the caps even respected? the ~25% gear haste, the ~42,5% Magic haste etc?

Found another case of sub optimal findings

==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Null Loop
ear1 Eabani Earring
ear2 Dedition Earring
body Malignance Tabard
hands Adhemar Wristbands +1 A
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX DA
waist Reiki Yotai
legs Malignance Tights
feet Malignance Boots

Avg WS Time = 8.791 s
Avg TP per round = 317.0 TP
==============================================================

I removed Reiki Yotai as an option under waist and got something better

==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Null Loop
ear1 Cessance Earring
ear2 Dedition Earring
body Malignance Tabard
hands Adhemar Wristbands +1 B
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX Dual Wield
waist Sailfi Belt +1 R15
legs Meghanada Chausses +2
feet Malignance Boots

Avg WS Time = 8.676 s
Avg TP per round = 326.2 TP
==============================================================

it a small difference but it seems to happen regulary that something seems off to me and when i remove options then it will find a more optimal set even thoug that set combo was always available

once again a case of sub optimal findings

First sets:
==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Combatant's Torque
ear1 Cessance Earring
ear2 Dedition Earring
body Malignance Tabard
hands Adhemar Wristbands +1 C
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX Dual Wield
waist Sailfi Belt +1 R15
legs Chasseur's Culottes +2
feet Malignance Boots

Avg WS Time = 4.554 s
Avg TP per round = 327.1 TP
==============================================================

THen i removed the Dedition Earring as a choice

==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Null Loop
ear1 Cessance Earring
ear2 Brutal Earring
body Malignance Tabard
hands Adhemar Wristbands +1 B
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX Dual Wield
waist Sailfi Belt +1 R15
legs Chasseur's Culottes +2
feet Carmine Greaves +1 R15B

Avg WS Time = 4.542 s
Avg TP per round = 328.0 TP
==============================================================

Again the difference is minor but it worry meat that i cant trust the findings .or is there some other goal its trying to archive that is unknown/not displayed?


both this and prior post was done with -50 PDT and MDT

just pumping these in while im tinkering around in a work meeting


==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Null Loop
ear1 Suppanomimi
ear2 Dedition Earring
body Adhemar Jacket +1 B
hands Malignance Gloves
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX DA
waist Sailfi Belt +1 R15
legs Chasseur's Culottes +2
feet Malignance Boots

Avg WS Time = 4.564 s
Avg TP per round = 321.3 TP
==============================================================


I Removed the adhemar bodies ( A and B)

==============================================================
main Naegling
sub Gleti's Knife R15
ranged Ataktos
ammo Devastating Bullet
head Malignance Chapeau
neck Iskur Gorget
ear1 Dedition Earring
ear2 Brutal Earring
body Malignance Tabard
hands Adhemar Wristbands +1 A
ring1 Epona's Ring
ring2 Defending Ring
back Camulus's Mantle DEX Dual Wield
waist Sailfi Belt +1 R15
legs Chasseur's Culottes +2
feet Malignance Boots

Avg WS Time = 4.462 s
Avg TP per round = 333.8 TP
==============================================================

again minor improvement from removing choices.

In my case I can say that when I removed Null Cape from the options, then it "rightfully" picked the Dex/DW cape option + Suppa + Reiki + Eabani (capped DW with /DNC, just what I would expect or something close to that).

If I put Null Cape back in the options, then it picks Null + Sailfi+1 R15 + Brutal + Cessance.


I mean... maybe that REALLY is the best option I dunno, but it sounds very very fishy to me, I think there's something off in the "attack Delay" calculations. The simulator reaches the 80% delay reduction earlier than it should, as a consequence it rightfully thinks adding more DW would do nothing and simply reduce tp/hit.
It makes sense, doesn't it?
Thing is... you're not at the 80% delay reduction when the simulator thinks you are, and this throws the results off.


JM2C, I'm dumb when it comes to math. We need someone proficient like Thorny, Simon or Byrth! XD

I don't know the specifics of the algorithm (and for the purposes of this post I'm not going to read it), but I can state definitively with this stuff when building something 'optimal' the number of possibilities is the amount of gear choices available for each slot times the number of choices for each other slot.

Suppose you have: heads, hands, feet
2 head pieces (A, B)
3 hand pieces (C, D, E)
4 feet pieces (F, G, H, I)

That's 2x3x4 choices: 24
A C F
A C G
A C H
...
B E H
B E I

So with 16 slots lets just pick 16 choices each (most are probably more than this) so 16^16:

That's 18.4x10^18 choices. At 1 microsecond to analyze them each it would take 584 thousand years to check them all. (not happening)

As such there's shortcuts taken. A common one is change 1 or 2 pieces of gear at a time and check the set, but this can change the answer depending on what you start with (ie different stats will help more depending on what you might have too much or not enough of in your starter set)

Coupled with I believe it allows parameters (keep -DT maxed) that could prevent certain choices.

Also I presume its solving for a single stat (not sure which and if its overall dmg not sure if its using the random or just take an avg. between min/max pDiF)

My recommendation is to use it for a starting point and use your intuition to tweak and check stuff, don't ask for magic.

yeah but it's not the first time I'm using, been using it for a long time and I never found these behaviours before ^^'

In the examples above the choice of items was extremely limited btw, everything was locked except Cape (4 options), multiple options for waist and lotsa options for Ear1 and Ear2.

I'm just explaining that shortcuts have to be taken and shortcuts will miss things, general problem scope stuff.

I've used the simulator to just check for optimal setups but its non-deterministic so you almost need to monte carlo it. Although if you have to squint to figure out which is better the actual answer is it probably doesn't matter because of the game RNG and just other things happening anyways.

There is no formal guide for this. The non-formal guide is:

1. Open the enemies.py file

2. Copy/paste one of the existing enemy lines

3. Adjust the stats to whatever you want

4. Reload the GUI. No need to recompile/repackage anything

From what I can tell, there are no issues with the code anywhere related to the delay reduction or haste values. I have confirmed this "issue" on my end as well with your extra information, though.

The various haste values displayed on the "Player Stats" tab did not respect their haste caps (they do now for version Feb24a). This was a design choice to show exactly how much haste you actually have to give you an idea how much "slow" you can withstand, but it can be confusing as you pointed out. I've updated this to show the effective haste values, which will stop increasing when reaching the cap. This is the only change in the updated build on GitHub, so maybe not worth updating just for it. I'll look into adding a tooltip to display total over-capped hastes later.

You can confirm that the haste caps are and have been applied properly in the get_delay_timing.py file. It uses caps at 256/1024 gear haste, 256/1024 JA haste, 448/1024 magic haste. The delay reduction maximum of 80% is applied as a minimum at 20% of the "base weapon delay before DW and MA."

The issue with BRD/DNC not liking DW appears to be more "Null Shawl is very strong when you don't need DT", especially when using TP Bonus off-hands that need accuracy. It is weird to see the code return a BRD/DNC set with only -73.4% delay reduction, but it looks like using a DW cape only brings this to -76.6% and loses 7% DA, 7 Store TP, and 7 accuracy. The accuracy loss corresponds to a loss of up to 3.5% hit rate for the off-hand (up to about 1.5% DPS loss) if the code built your set to barely reach hit rate cap (which it often does for enemies with moderate Evasion). The set I've seen in my testing finds that Null Shawl is quite a bit better than a DEX+DW ambuscade cape, but something like Suppanomimi is only marginally worse than Brutal Earring.



This is correct on how the algorithm works and on why unlucky initial conditions can result in slightly sub optimal sets.

This problem mostly affects critical hit weapon skills (building for WS damage or crit% depends on how the set builder starts) and sets with constraints like DT and accuracy, especially those with both constraints where equipping something like Null Loop can effectively lock that piece of gear permanently since it provides a ton of accuracy and DT in a neck slot (I believe this is the main issue with one of Daneblood's posts above).