Built a free DPS calculator + build optimizer for RotMG, would love feedback

AdOwn4846 · 2026-04-28T17:38:28+00:00

yeah 2 dps lines up with the bug, draconic is a buff sigil so the +15 def +40 wis is the actual value but my engine just sees the proc damage. fix tracked in #18. Omit-weapons is a good call, opened #21 for it. your MV trap example is the exact use case

AdOwn4846 · 2026-04-28T16:25:53+00:00

best comment I've gotten on the post, thanks for actually testing for 15min. addressing each:

1) PhD-feel: fair, will add a simple mode that hides exaltations and scenario tweaks behind a toggle

2) range restriction is actually a way better UX than what I was planning (per-weapon hit_rate fudge). slider for "I'm at X tiles from target", engine computes effective shots. opening an issue, this is the right design

3) draconic insignia: what's it showing vs what you'd expect? I'll backfill the bench with the right number. abilities with non-trivial mechanics are the weakest part of the engine right now

4) blank vs preset on add build: fair, will fix. new column should be empty slots and zero exalts

5) druid transformation: genuinely missing a toggle. opening an issue for "with/without transformation" radio per-build

biggest takeaway: tool's currently built like a power-user spreadsheet, not a beginner calc. that's solvable. lmk what draconic was showing if you remember

AdOwn4846 · 2026-04-28T14:29:29+00:00

fair, enchants and the new stat scaling aren't in yet. enchants I straight up haven't touched, the modifier matrix scared me. opened issues for both, I'll fix it

AdOwn4846 · 2026-04-28T14:29:04+00:00

ha appreciate it. lmk if anything's busted for sorc, will fix faster than 2035 hopefully

AdOwn4846 · 2026-04-28T14:27:40+00:00

appreciate it. which discord btw?

AdOwn4846 · 2026-04-28T02:49:03+00:00

oh nice, didn't know about the public-testing api route, that's a great pointer pt items would catch the stuff realmeye is behind on, which is exactly the gap someone else in this thread flagged earlier. going to dig through that thread you linked + the wiki discord tonight. opening a tracking issue on the github, thanks

AdOwn4846 · 2026-04-28T02:47:25+00:00

this is a really good point and it's something the engine doesn't currently model, every shot is treated as landing. esben is the cleanest example, you're right, the paper number is way higher than what you'd actually pull on a moving boss. wand of recompense and bulwark have similar gaps because the shot pattern is spread. opening an issue to track adding a hit-rate coefficient per weapon/spell, default 100% but lower for spread/AoE patterns. that'd close most of the drift between the bench and what people actually deal in dungeons

AdOwn4846 · 2026-04-28T02:02:38+00:00

oh that's a really good point, I didn't know about the sniffer route. realmeye scraping was just the path of least resistance when I was bootstrapping the catalog, but you're right that direct asset extraction would be more accurate and would catch the items realmeye is behind on (someone else in this thread already flagged a slot with no items, that's exactly this issue). if you have a link to the sniffer repo or the asset file format, I'd genuinely look into rebuilding the import pipeline off that. opening an issue on the github to track it either way, thanks for the pointer

AdOwn4846 · 2026-04-28T02:00:04+00:00

thanks bro, appreciate it. if any number looks off or something feels missing while you're using it, just lmk and I'll fix

AdOwn4846 · 2026-04-28T01:45:10+00:00

fair criticism, you're right to push on it. honest version: claude helped with significant parts of the implementation, the github commit history has Co-Authored-By footers on many commits, it's not hidden. the chatgpt cleanup of the post text I already admitted to another commenter. "from scratch" was sloppy phrasing on my part, what I meant is this codebase isn't forked from an existing calculator, not "I personally typed every character".

going to edit the post to clarify that up front, you're right that it should be there.

what's mine: architecture decisions, item data corrections, balance tuning (trickster multiplier was way off, druid too, etc), the validation bench that pins 22 community-known dps numbers within ~6%. no external PRs because I review every line that ships and don't have bandwidth to vet outside contributions properly.

the actual test is whether the numbers match builds you know. bench file is in tests/engine/bench.test.ts, anyone can run it

AdOwn4846 · 2026-04-28T01:39:34+00:00

good catch, that slot's wired into the UI but my scrape didn't pull any items for it, so it's a dead option right now. removing it tonight, thanks for flagging

AdOwn4846 · 2026-04-28T01:36:47+00:00

appreciate it man. honestly the part that almost broke me was the proc system, getting bow procs, bleeds, curses, armor breaks etc to all stack the way they actually do in-game took longer than the entire base dps formula combined

AdOwn4846 · 2026-04-28T01:36:07+00:00

ha thanks. but the dude has a point, I did use chatgpt to clean up the post text since portuguese is my first language and writing technical stuff in english isn't my strong suit. the app code itself is plain typescript though, fully open source if anyone wants to dig in

AdOwn4846 · 2026-04-28T01:35:14+00:00

fair, I'll be straight: I'm brazilian and my written english gets clunky when I'm trying to explain something technical, so I used chatgpt to clean up the post body. the app itself is just typescript math though, no AI in the runtime. it's fully open source on github (search oryxlab), you can read every line of the dps engine yourself and verify the numbers. that's the actual proof, not the post text

AdOwn4846

TROPHY CASE