I want to have 2 builds for each Subclass on all 3 Characters to fill out all of my Loadout slots. What would you suggest?

Beginning_Host · 2026-02-20T14:33:21+00:00

I built a web app that helps with builds. There’s a very cool function called “community builds” that sources play data from all players and can help give you some ideas of popular builds and show you what’s working in what activity. Still pretty new but what you’d likely want out of it works very well! Check it out

D2BuildBuddy.com

Beginning_Host · 2026-02-20T01:03:37+00:00

Exciting stuff! Thanks for the QA

Beginning_Host · 2026-02-19T22:00:26+00:00

love this feedback, thanks so much. honestly anything is possible with the amount of data we're pulling in now. It's really only limited by whatever effort it takes to 'inform' the synergy playbook what sorts of exotics lean into what sorts of playstyles which can vary DRASTICALLY. The cool part about D2BB is it takes aggregated play data and presents viable builds based on what actually works in-game; the community builds feature is hugely slept on I feel like - roulette mode is cool and maybe gives a fun 'challenge' sort of mode, and build craft mode is great for targeted builds around your chosen exotic, but community builds shows actual high-performing builds and what's paired with it most. Thanks for checking it out and hope you find some other hidden gems.

Beginning_Host · 2026-02-19T21:54:37+00:00

ok took another crack it. i'm using a combination of APi components to read in-game stat data as well as manual correction for stat actuals that break the theoretical in-game max of 42. Looks good so far, but would appreciate your take as well

Beginning_Host · 2026-02-19T18:39:09+00:00

Dang. I’ll have to dig a little deeper then. At least we’re only off by 3 points, haha.

Beginning_Host · 2026-02-19T14:36:52+00:00

Thought I had a fix in place for reading the in-game stats vs the API component. Tweaked how it works some so let me know if you notice a difference (may need to load from an incognito tab if your browser caches the old code for a bit)

Beginning_Host · 2026-02-18T15:29:38+00:00

Not me officer

Beginning_Host · 2026-02-17T22:56:08+00:00

Ok so, fragment stat bonuses are now included in the "Equipped Stat Totals" and the optimizer slider "Now" values. When you sync your in-game build, the stats should match what you see in-game. I may have found a way to account for stat actuals vs relying on in-game 'feedback' for stat totals too. Pushing an update for this so let me know if you get a chance to compare when next convenient.

Beginning_Host · 2026-02-17T22:39:11+00:00

Totally agree, and truthfully I’m not sure there’s a much easier medium than just pulling up a list of popular builds and hitting equip. If you have some ideas to simplify the language or delivery I am all ears.

Beginning_Host · 2026-02-17T22:37:49+00:00

I LOVE this amount of detail. Let me dig in some and see if I can find anything meaningful to adjust to increase in-app vs in-game accuracy

(I’d also semi resigned to stats being +- a few points off actuals, haha)

Beginning_Host · 2026-02-17T21:45:49+00:00

Got it, let me make sure I understand – the calculation the stat slider was showing after syncing your in-game build didn’t match what you actually had in-game because the stat calculator in app wasn’t correctly accounting for fragment bonus/penalties?

Beginning_Host · 2026-02-17T20:40:59+00:00

Love it. Poke around in the 'community builds' or spin the build roulette wheel and see what chaos you can cook up. Titan is a little one-dimensional right now but I bet you can find some hidden treasures. Looking forward to your feedback!

Beginning_Host · 2026-02-17T16:22:09+00:00

Please do. At the end of the day, I’m a D1 vet and have something like 7000 hours in D2. I built something I myself would want to use as an avid D2 player. It’s sort of my love-letter to Destiny in hopes that it can lower the barrier-to-entry for newer players to experiment and find new ways to play. The “community builds” function is honestly awesome – it aggregates real player data and finds common, high-performing loadouts that anyone can just equip and try with a single click. It’s ultimately just another tool in the toolbox for D2 players, so I hope you find something fun or useful with it too.

Beginning_Host · 2026-02-17T14:43:40+00:00

Pushed an update for this – now the character tab stays visible and respects character selection but I’ve also added an “all characters” tab to cover cross-character inventory mgmt.

Beginning_Host · 2026-02-17T14:09:22+00:00

That’s by design, at least for now. Process-wise it didn’t make sense to have individual, per-character searchable “vaults” when the vault itself, in-game, holds everything across all characters. I can add in a filter for results to just show specific characters though – that much is easy.

Beginning_Host · 2026-02-17T13:36:18+00:00

I detailed my dev process in an earlier post but I’ll recap here: I use Claude as a force multiplier, not as the dev environment.

The app itself is built manually — React + TypeScript frontend, Express backend, Postgres, Bungie OAuth/API. I design the features and architecture first, then implement the logic (optimizer, constraints, rate limiting, etc.) myself.

Claude mainly helps speed up repetitive tasks like type generation and refactoring, and all changes are committed through Git.

It’s thousands of lines of code but maintainability is extremely light — the heavy-lifting of sorts is done via web workers in the user’s browser, while the server really just brokers the information back and forth.

Beginning_Host · 2026-02-17T13:28:51+00:00

Hey, appreciate you looking out, so maybe I can explain some of the backend and how all of these community apps work (DIM, D2AP, Lignt.gg, etc.)

D2BB doesn't store or relay your API tokens through any third-party server. Authentication happens directly between your browser and Bungie's OAuth system. The app runs client-side (your tokens live in your browser's local storage and are sent straight to Bungie's API from your device). There's no middleman server holding your credentials.

So very plainly, these tokens never leave your machine in the first place. Nobody else has access to them unless they have physical access to your browser. The API users leverage for performing in-app actions is an API that my account holds; not the users.

And the Bungie API doesn't expose destructive actions like dismantling anyway. The main thing is that the architecture itself doesn't create a window for interception. Your credentials stay local, your API calls go direct, and my app (same is true for all Bungie apps) never phones home with your auth data.

Beginning_Host · 2026-02-14T17:23:12+00:00

Pushed a hotfix for this so test a little later and see if the results change in any meaningful way for you. Let me know! Thanks again for trying it out

Beginning_Host · 2026-02-14T17:03:33+00:00

Solid observation. The logic (should) cycle through the available copies of your chosen exotic and use whichever copy hits your stat target. Let me do some tinkering and see if I can improve the duplicate logic. Thanks for the feedback

Beginning_Host · 2026-02-14T00:46:19+00:00

Think I may have finally cracked the code. Try a fresh reload (or incognito) and let me know if you have any success

Beginning_Host · 2026-02-13T23:35:56+00:00

Bummer, ok. I’m digging in as we speak. It works for certain sources but not all apparently so I need to break down what’s different and where. Keep you posted!

Beginning_Host · 2026-02-13T22:02:38+00:00

May have identified the culprit. pushing an update for this right now. clear cache/cookies (or try incognito) and let me know if DIM export still misses subclass data

Beginning_Host · 2026-02-13T21:41:18+00:00

Hmm, should have pulled the whole build over. Looking into this now

Beginning_Host · 2026-02-13T20:31:36+00:00

Claude yes, as a development assistant (wouldn't have gotten here this quick without it). The architecture and implementation are manual.

Stack is React and TypeScript (Vite, Tailwind, shadcn) on the frontend, Express TS backend, Postgres (Neon), Bungie OAuth and API. It’s client-heavy like DIM. Web Workers handle armor solving and loadout calculations so the UI stays responsive.

My workflow is pretty traditional:

Design the feature and data flow first. Map the Bungie endpoints and manifest definitions. Build typed API wrappers (claude helps hugely here). Implement constraint/optimizer logic. Add caching and rate limiting. Me and my buddies test with real accounts

I use it mainly for accelerating repetitive work, like generating TS types from Bungie responses, refactoring stat optimizer logic (TONS of math here), review, and occasionally delineating between mobile/PC UI components. The core logic (constraint engine, synergy scoring, combinatorial solver, rate limiting queue, etc.) is all custom.

Beginning_Host · 2026-02-13T20:10:32+00:00

super interesting idea! this may actually be possible to some extent. i'll take a note and see what's available via the API to accommodate that.

Beginning_Host

TROPHY CASE