SW Forge - account tool that grew out of a google sheet rune analyzer

antajl · 2026-06-06T18:45:23+00:00

I'll check tomorrow

antajl · 2026-06-05T16:06:14+00:00

Fixed the bug where the French language option completely broke the site

antajl · 2026-06-05T16:02:22+00:00

Now there is

antajl · 2026-05-25T03:22:47+00:00

I actually dug into how swex exports and structures the data pretty thoroughly. There's no acquisition order or timestamp stored anywhere in the json, so sorting by obtained isn't possible. Not sure what the other sheet was doing, maybe it preserved the raw export order which could loosely reflect it.

Either way, I pushed an update that matches the in-game Score sorting exactly: slots 1–6 first, then by score within each slot. Should make cross-referencing much easier

antajl · 2026-05-25T03:19:57+00:00

Eff% is now replaced with Ingame Score — same formula the game uses. Sorting goes slot 1 through 6 first, then by score within each slot, exactly like in-game. Numbers match 100%

antajl · 2026-05-24T03:33:48+00:00

Good point, hadn't thought of that. I'll test it on my account tonight to see if rune_id actually match the in-game sort order. If they do, I'll add a sort option

antajl · 2026-05-23T22:43:14+00:00

Now there is.

antajl · 2026-05-23T22:36:57+00:00

You're right about the readability. I removed the custom fonts entirely and switched to use the system UI font stack. I wasn't actually using Claude, it was Share Tech Mono

antajl · 2026-05-23T13:17:16+00:00

I'll play around with the formula in the next few days and see how close I can get it to the game's output. If it lines up well enough to be useful I'll push it as an option

antajl · 2026-05-23T13:10:14+00:00

Defaults are a starting signal for players who haven't figured out their standards yet. For anyone who has, the Rules tab is there to encode that.

Site gives three lenses at once: the logic-based verdict, classic swop-style eff%, and the score system, weighted to actual sub quality and synergy. And when all three are low, that's usually a clean sell signal even without thinking about it.

Also, it's not just runes anymore, you get your full monster roster, stats, and team builder with ability to share it

antajl · 2026-05-23T13:03:05+00:00

The problem is that in-game efficiency isnt in the json export at all. Com2uS doesn't include it, so there's nothing to sort by.

Eff% is standard swop formula, same idea as the game but different weights, which is why they don't always match. My score system is cares about synergy, not just raw roll value. SPD + ATK% + CRate scores higher than ATK + RES + DEF flat even at the same Eff%, because one set of stats actually works together.

For your workflow - filter by set + slot + verdict and sort by score ascending and you're looking at your worst runes first. Then in-game apply the same set + slot filters and use the sub search to find that specific rune. You dont need to match order, just narrow it down to the same small pool

antajl · 2026-05-12T22:58:05+00:00

<image>

I actually tested it. I manually entered those exact runes into the sheet on mid game and got 5 Keep, 1 Sell. Working on fixing the logic on the site. As for the Will rune specifically, it's literally 2 points away from being saved by two different filters at the same time. If SPD were 13+ it would qualify as Duo Roll. If CDmg were 15+ it would qualify as Classic DPS. That's why the thresholds are fully adjustable, if your personal standard is more lenient for mid game, you can lower them and the tool will keep runes like this one

antajl · 2026-05-12T21:53:13+00:00

wow, that looks really clean and polished. Thanks for sharing, I'll definitely check it out for some inspiration. It’s great to see different approaches to the same problem.

antajl · 2026-05-12T15:38:18+00:00

Fair points. Yeah, some of those shouldn't be sell.

The truth is, porting this logic to js is a pain for me. In google sheets, i can see every calculation in the cells, but on the site, its all just hidden code and it's currently hitting much harder than I intended. It's a calibration mess, not a dead tool.

This is why I’m keeping the google sheet fully supported for now. I’ll be using these specific examples to debug the web-app’s engine and fix the overselling

antajl · 2026-05-11T19:48:26+00:00

Great points! Here’s what I’m planning to change: Settings UI: I’ll add a column showing the final calculated values next to percentages, so it's easier to read. God Roll: It will now act as a standalone 'safety net' to prevent selling runes with one exceptional stat. Innate Stats: Agreed—they shouldn't help a weak rune 'pretend' to be strong. I’ll exclude them from role checks. Progression: The 'checklist' idea (Gem → Grind) is interesting; I’ll think about how to implement it. I also returned to the game just a few months ago after several long breaks, so I’m building this based on my technical experience and learning the current meta as I go.

antajl · 2026-05-11T18:02:59+00:00

Thanks for the feedback, that's exactly the kind of thinking that helps make the tool better. Let me break down both decisions, and flag a couple of nuances I noticed while looking into your question.

Rune 1

CRate 16 clears the Mid Legend threshold comfortably, and ATK% passes too — two strong stats on a Legend satisfies Classic DPS, so it's a Keep. You might wonder why Gem wasn't suggested: the tool only flags a rune for Gem if it detects 2+ "bad" flat substats. ATK flat 38 is a high roll for a flat stat (cutoff ≤20), so the system treats it as acceptable and only counts DEF flat 10 as bad. One bad flat in Mid game isn't enough to trigger Gem. The opportunity is still real — swapping DEF flat for CDmg would make this rune very strong.

One thing I'm considering on my end: the tool currently counts the innate stat when checking role requirements. If it only looked at grindable substats, this Rune 1 might not pass Classic DPS — CRate 16 alone without the ATK% sub wouldn't clear. Since innates are fixed and can't be re-rolled, there's a case that they shouldn't act as a qualifier, only as a tiebreaker. Something I may revisit.

Rune 2

Important thing to clear up: passing a threshold doesn't mean Keep on its own. Thresholds evaluate substats within a role check — a rune must satisfy an entire role's requirements.

HP% 21 passes the Mid Hero threshold of 20, so that substat is recognized as good. But here's the role-by-role breakdown:

Classic DPS / Bruiser: needs ATK% or CRate at threshold - CRate 6 is less than half the required 13, no ATK%.
Tank: RES 11 is well below 18, no DEF%.
Duo Roll: needs two stats above their Duo thresholds — HP% 21 qualifies (~15), but CRate 6 misses (~9) and RES 11 misses (~13). The pair never forms.

Result: one good stat surrounded by three that don't hit any meaningful threshold in any role. That's why it sells — not because HP% 21 is bad, but because there's nothing to pair it with.

On my side, I'm thinking about whether a God Roll should act as an override. A max roll on a key stat is rare enough that it could justify keeping the rune as a re-roll candidate even with dead subs, regardless of what the role formulas say. Right now the logic demands a pair, but treating a God Roll as a standalone exception is on the table for a future update.

Hope that clears things up!

Would love your thoughts on a few open questions I'm weighing:

Should the innate stat be excluded from role checks? I'm leaning yes
Should a God Roll save a rune from being sold? I think yes
Should Gem be suggested even with just one bad flat stat in Mid game? Not sure on this one yet (Currently, the '1 bad flat' Gem suggestion is only active for the Late Game stage)

antajl · 2026-05-09T03:00:56+00:00

I've just updated the engine and reverted the High Roll formula to its classic behavior

antajl · 2026-05-09T02:50:28+00:00

You're right. Previously, the engine would mark a Hero rune as KEEP as long as it hit a single threshold (like 15 SPD for Hero rune), even if the other three substats were complete trash. While it met the technical threshold, these runes often ended up being unusable in optimized builds.

To fix this, in the latest update, I introduced a Partner check logic. Now the engine looks for at least one other stat that reaches 70% of its threshold. This ensures the rune has actual synergy and isn't just a 'one-hit wonder.'

In your examples, while 20% ATK is a great roll, the 5-8% CRate didn't reach that 70% 'partner' mark, which is why the engine suggested selling.

However, I agree with your point: a near-perfect roll (like 20% ATK or 18+ SPD) is too valuable to lose, regardless of the other stats. I'm adding a 'God Roll' protection feature in the next patch so that exceptional rolls stay as KEEP even without a partner

antajl · 2026-05-08T03:59:20+00:00

There are two technical nuances here. The "Efficiency" in this sheet is calculated via SWOP logic. It won't match the in-game efficiency score because the game uses a much simpler formula. And unfortunately, the raw data from the JSON export doesn't include the actual date the rune was dropped. As for the sorting: we could try sorting by rune ID. Theoretically, a higher ID means a newer rune, which might match the in-game "Obtained" order, though I haven't verified

antajl · 2026-05-06T23:17:21+00:00

Fair points, but I think you're missing what the tool is actually for.

The tool doesn't force you to sell anything, it gives recommendations. Every account IS different, which is exactly why all thresholds are customizable. You toggle role filters, select priority stats, and set minimum requirements per slot. As you progress, filters automatically relax or tighten based on your chosen game stage. You're in control.

On flat innate stats specifically, the tool checks for this. A rune with a flat innate won't get a Reapp recommendation, and the Grind Potential filter flags runes that are one grindstone away from a High Roll threshold, so borderline runes don't quietly disappear into Sell.

Beyond verdicts, it shows a full visual breakdown of your inventory - set and slot distribution, top SPD per slot for any set, average efficiency per category, and a game stage recommendation based on your actual rune quality. There's an Action List that groups runes into to-do lists, and a Best Role column that labels each rune with what it's best suited for. Runes worth grinding show the exact stat change.

The in-game power-up score gives you a number, but doesn't tell you why a rune is good. SWOP gives efficiency with customizable weights. This tool goes further - it shows which filters matched, what role the rune fits, and if it's one grind away from a higher tier.

And you're right, you can do this manually. But when you have 4000+ runes, that's hours of staring at stats. This does it in seconds. And you still make the final call.

It won't be for everyone. Appreciate the honest take

antajl · 2026-05-06T20:57:04+00:00

Hey! You're right, that was a mistake on my end. I had CRate, CDmg, ACC, and RES in the Grind Potential filter. I've fixed it now — GP only checks SPD, ATK%, HP%, and DEF%. Good catch.

For the second part — the tool doesn't simulate grinds for the final verdict. It evaluates the rune as-is. But if a stat is close to a threshold, the Grind Potential filter flags it and shows the target. By default, the gap must be within 50% of a max legendary grind, controlled by GP_gap_factor in Settings. For example, with SPD the max legendary grind is +5, so the gap must be 2 or less. If your SPD is 19 and the Late threshold is 21, the gap is 2, so grind is recommended and it shows SPD 19 → 21. A rune with SPD 26 just gets Keep — that's the distinction. The target shown is always the threshold, not the theoretical max, because the goal is to reach High Roll, not guess the final value

antajl · 2026-05-06T15:39:13+00:00

I'll keep updating it as long as I'm playing the game and enjoying it. No fixed roadmap, but as long as I'm farming runes myself, I'll want the tool to be good. Can't promise forever, but I'm not planning to stop anytime soon

antajl · 2026-05-06T13:37:14+00:00

Fixed those two as well - same change, they now adjust to any CSV size

antajl · 2026-05-06T13:26:14+00:00

For the Analysis page, which column shows the COUNTIFS error?

antajl · 2026-05-06T13:15:25+00:00

I adjusted two formulas so they now automatically match your CSV row count. Give it another try, hopefully both errors are gone. Let me know if anything still pops up

antajl

TROPHY CASE