All Jobs Damage Simulator And Gear Sets

Excited to start seeing the new +4 gear added to https://www.bg-wiki.com/ffxi/All_Jobs_Gear_Sets

I've updated the sets for NIN, DRK, and RDM since I play those jobs most often. I'll gradually update the sets for other jobs later. Click the "Expand" button below each set to see the date they were last updated.

Since we're on a new page:

I've updated the code, especially for magic damage dealt. See my previous post at the end of the previous page for details.

Add stinger helm please

Sorry if I missed it, but is there any way to calculate SC damage (or put in parameters for specific SC to occur continously)?

An example might be spamming CDC which should have some SC damage coming out of it since CDC chains itself.

I did, I ask because it comes out on top for a few ws where you have 3k to and don't need tp bonus. Curious to see if others get similar results.

An idea for those who partake in editing. Can a "*" be added to gear sets that have already been updated on the main page: https://www.bg-wiki.com/ffxi/All_Jobs_Gear_Sets

IE: All Jobs Gear Sets/Dark Knight*

* Denotes gear sets which have been updated to utilize +4 gear.

Much respect for your work. Mind explaining why AGI Andartia's is listed in several of your sets? What am I missing here, ranged acc/crit rate?

I was wondering as well but then my assumption was that it was for the little bit of ranged acc+ it would give and that was bridging the gap on locus/trash mobs. DEX was likely just overkill from an acc perspective I imagine and it spits out AGL for the above reason.

That's plausible. There's a few Mpaca/Tatenashi +1 pieces in those sets which have no ranged accuracy, so that makes sense to add some in the few spots to make up the difference.

Just wanted to say thank you very much for updates. I probably use this tool more than I should :)

In the case of r30 nyame gear does the body n legs in particular win out most everything with 1 hit weapon skills?

Use the tool and find out

Updated COR with some +4 pieces.

I was reviewing some of the COR sets to make sure mine are current. Why would Odium get any placement in Last Stand and Terminus WS sets over daggers like Gleti's or Crepuscular? Can death land on either of these two WS?

Odium is one of the few daggers to have str/agi/dex on it where as most of the others will only have dex and agi. Before you say that STR isn't a mod STR will still increase Last Stand and Terminus damage with them being physical.

Has anyone else been encountering this issue?

https://github.com/IzaKastra/wsdist_beta/issues/14

If you were able to resolve it on your own, lemme know how you did it, it's been unfortunately sort of rendering the app not as useable for me because chunks of the UI are just cutoff even on fullscreen :c

Plug a second monitor in at 1900 x 1200 and move it there?

I've finished updating the BG Wiki pages to include +4 AF/Relic gear. All gear sets should also show damage dealt by the set against the test enemy. Click the "Expand" buttons to check the TP values used for each set.

I've added a few more sets to certain job pages, such as the MNK page now showing with/without impetus/footwork for some weapon skills, and the RNG page showing AM3 and Barrage sets (which are very strong if the math is correct).

Let me know if I've missed something important.

I added Stinger Helm +1 R15, but I'm not seeing the usefulness of this item outside hyperbuffed situations where you don't need accuracy or attack.

Yes and no. This feature exists for DPS simulations in an older version of my unpublished test code, but it is limited to 2-step skillchains. I wanted to allow up to 5-steps, but I ended up getting busy before finishing it.

This is my understanding of it as well.

The code adds +100 Ranged Accuracy for Daken by default, but that alone isn't enough to cap ranged hit rate against enemies with 1350 evasion (the test enemy for BG Wiki sets) when some of the best head/body/hands/legs/feet slots provide zero ranged accuracy bonuses (Mpaca/Tatenashi). The code finds that the ambuscade cape and Path C Adhemar are the best places to gain ranged accuracy without sacrificing too much else.

I use "AGI+20, DEX+10, Store TP+10, Acc/Atk+20" on my main NIN TP cape as a middle-ground. I lose 20 DEX (~15 accuracy and some dDEX crit rate), but gain +20 AGI (~15 ranged accuracy, ~10 evasion, and some dAGI subtle blow).



I have not looked into this in a long time, but I believe that I can safely say that this is almost certainly not an "easy" fix and it will not be implemented for a long time (if ever), unless I've missed a simple way to do it while investigating this exact feature long before the GUI was published. This is also currently one of the main reasons I've never removed the "beta" from the project name despite hiding the original project repository on GitHub. If I ever find time to learn how to properly write a GUI, this is something I'd definitely want to do.

Python is not a GUI-friendly language. TKinter GUI elements are built on a grid system, with all elements assigned a fixed column and row value. The way TKinter is built requires that the row/column positions remain fixed relative to each other, but their content can stretch/shrink to match the resized window. I've explored this as an option, but it doesn't always behave well or even look good. Your suggestion requires rewriting the entire GUI from scratch and implementing dynamic positions for all GUI elements based on the window size. I'm not even sure if this is technically possible with Tkinter.

In your example image, moving the equipment selection from the bottom of a vertical GUI to the right of a horizontal GUI requires moving the frame holding the equipment selection subframes from position "row=2, col=0" to position "row=0, col=1" and rescaling everything else to not break format. The GUI still has a hidden "self.horizontal = False" flag to enable exactly that, but it looks like enabling it no longer works after all of the changes to the code since it was implemented. "Fixing" this would also mean maintaining two separate versions of the GUI code (~6400 lines of bad code at the moment), which I want to avoid doing.

Similarly, scrollbars are a huge pain in general since everything about them must be pre-defined manually. The GUI already has at least one issue with scrollbars that you may or may not have noticed:

• Scrollbar size does not always reset when changing jobs. This causes long item lists to reach the "end" of their scrolling limits before the final item in the list is viewable (the scrollbar size occasionally uses the old item list length, rather than the new one after changing jobs).
  

  • The opposite of this bug is easily seen with the "special toggles" scrollbar at the top of the first tab, where you can scroll significantly further than the last item in the list.
  
  

For now, I'll simply copy/paste my response here to GitHub for completeness. But I do not see myself closing that issue unless I have a burst of inspiration. Maybe AI could handle it if given the mess of the GUI code as is?

It's pointless for DRK (Emp+2/3, Sakpata's) and pointless for DRG (Gleti's). Maybe good for multihit WS on GKT/Polearm on SAM? Seems unlikely to be worth ever carrying since I bet TA+5% beats it.

Can you add Red Lotus/Sanguine to Blue Mage? They're in the RDM sets, and there's likely use case for the Relic legs there

I had it show up for 3k tp on:
Shoha
Fudo
Kasha
Gekko
Yukikaze

Which these already had pdl feet recommended
Maybe Mpaca legs would have taken precedence over Wakido but I don't have augments on it
Perhaps then it wouldn't be recommended because of the amount of pdl?

I've added Sanguine Blade and Red Lotus Blade to the BLU page. You were correct: the Relic+4 legs do show up for these weapon skills.

Best i could assume is max TP on gkt WS. its effectively 43 STR at its best(unity rank1), while nyame is 26 STR which would be your best alternative in that scenerio i think

Thanks, surprised Jhakri beats Nyame. 10 MAB > 5 WSD + some degree of INT? interesting.

Are we sure Empy+3 beats Pixie+1 for Sanguine? I figured it'd be similar to Leaden

4/5% DA on Nyame R25/30 too I guess

DA wont amount to much on most of SAM's go-to WS'


iirc nyame r30 was already pretty close to pixie+1 for leaden, blu emp+3 is more MAB and more str/int/mnd than pixie ontop of 12 WSD, should be an easy win

It's close, but it makes sense.

Looking strictly at the code's numerical output: Empyrean+3 head is 2.45% stronger than Pixie Hairpin +1 (18343/17904 = 1.0245).


Looking at contributions from individual stats in more detail:

Without a head slot, we have 271 STR, 378 INT, 301 MND, +20% Dark damage (Archon+Orpheus), +332 Magic Attack, and 46% WSD.

• Pixie Hairpin +1 provides +27 INT and +28% Dark magic damage.
  

  • The INT is additive with base damage as dINT, increasing base damage by 1918/1864=1.02897 = +2.897%
  • The Dark damage bonus increases the Dark magic attack multiplier by 1.48/1.20=1.23333 = +23.333% damage
  • Together, these are 1.02897*1.23333 = 1.26906 = +26.906% damage over no head equipped.
  
  

• Empyrean+3 head provides +28 STR, +35 MND, +34 INT, +51 Magic Attack, and +12% WSD (and +61 Magic Accuracy).
  

  • The STR, MND and INT are part of the WSC and dINT for Sanguine Blade. These increase base damage by 2003/1864=1.07457 = +7.457% together.
  • The generic magic attack multiplier increases by a factor of 483/432=1.11806 = +11.806%
  • The WSD multiplier increases by a factor of 1.58/1.46=1.08219 = +8.219%
  • Together, these are 1.07457*1.11806*1.08219=1.3001 = +30.001% damage over no head equipped.
  
  

Comparing the two: the Empyrean+3 head is 1.3001/1.26906 = 2.44% stronger than Pixie Hairpin +1. Empyrean+3 also has +61 Magic Accuracy that isn't being considered by the code.

Bumping this for you. I would like to see this implemented, too. I have always understood it to be the second scenario. That's how BGWiki explains it: https://www.bg-wiki.com/ffxi/Category:Multi-Attack

I understand you probably want some reliable sources. Hopefully someone here knows.

Mythic AM3 on that page is a bit wrong, but it's an editorial choice how to address it: https://www.bg-wiki.com/ffxi/Category_talk:Multi-Attack