Stash Battle

GreatJar · March 1, 2026, 4:38pm

Any functionality to allow the filter to apply to both scenes drawn?

dtt · March 1, 2026, 4:57pm

Not at the moment, what is your use case?

I’m thinking I could add a config menu to allow more specific uses in the future.

GreatJar · March 1, 2026, 5:26pm

Just rating a performer’s scenes against their other scenes only, or studio

rawbeast · March 2, 2026, 3:33pm

I’d like the filter to be able to apply to both sides too. Often I want to battle a subset of my stash against each other, and not just my current filter vs my whole stash. My use case right now is to filter to a specific performer to try and rank my favorite scenes of theirs. (i.e. I don’t want to battle other performers)

RagingHippo · March 2, 2026, 5:02pm

I also want to run the battle using just scenes from a single performer as rawbeast mentioned.

rawbeast · March 2, 2026, 7:28pm

Just had a whirl at implementing the change myself (using AI )

sakoto · March 2, 2026, 10:43pm

You modified alot of lines here. Are you sure you preserved root functions?

dtt · March 5, 2026, 12:54am

It’s mostly just renaming var names it looks like.

Thanks @rawbeast I’ll do a review this week!

dtt · March 11, 2026, 12:23am

Updated to Ver 2.6.3:

Added toggle to use filtered scenes for both sides (Thanks @rawbeast )
Opening modal pauses all media in background now (Thanks @rawbeast )
Cleaned up some code
Fixed unrated scenes sometimes showing up on the right side when a suitable candidate could not be found.
- This condition is disabled when the use both sides filtered is checked, so incase you want to pit unrated scenes against other unrated scenes
Changed unrated scenes to start from rating 1 in calculations instead of 50
Fixed ranking text (#XXX out of #YYY) to not include unrated scenes
Updated gauntlet/champion logic to no longer set a scene to 1 just cause its the lowest scene
Fixed a bug where the first battle for gauntlet didn’t update rating
Added a “finding final placement” badge to gauntlet mode so its more clear
Fixed issue where unrated scenes show up as 1 on the loser card

Give the new version a whirl!

dtt · March 12, 2026, 3:43am

I didn’t like how unrated scenes were battling the same opponents climbing up in gauntlet mode so I added more variance to make battles more interesting hopefully.

Updated to Ver 2.6.4:

Increased reach for swiss pairings to 10
Gauntlet/champion mode now randomly picks from 5 opponents instead of just the next highest opponent

rawbeast · March 13, 2026, 4:56am

Is there a way to choose what scene enters the gauntlet?

dtt · March 13, 2026, 4:49pm

What i’ve been doing to select one is just searching for the title as a filter.

Although I could see that being tricky if you want to filter a specific pool but select a specific scene.

rawbeast · March 14, 2026, 4:34pm

I only just discovered this great documentation:

github.com/dtt-git/stash-battle

DOCUMENTATION.md

main

# Stash Battle — Technical Documentation

> For LLM agents and contributors working on the plugin. This documents the nuanced behavior, architecture, and design decisions that aren't obvious from the code alone.

## ⚠️ Keeping This Document Up To Date

**This file must be updated whenever you change behavior in the plugin.** If you modify rating logic, scene pool filtering, mode behavior, caching, UI components, or any other documented behavior, update the relevant section here in the same changeset.

When adding new features or fixing bugs:
1. Update any existing sections that are affected by your change
2. If the change introduces a subtle edge case or non-obvious behavior, add it to the **Common Pitfalls & Edge Cases** section
3. If you add a new mode, config option, or major feature, add a new section for it

If you're an LLM agent: read this file before making changes to understand existing behavior, and update it after making changes to keep it accurate.

---

## Architecture Overview

The plugin is a single IIFE (`stash-battle.js`, ~2600 lines) injected into the Stash UI. It has no build step — just raw JS, a CSS file, and a YAML manifest. It adds a "Battle" button to the `/scenes` page that opens a modal where users compare scenes head-to-head to build rankings via an ELO system.

This file has been truncated. show original

I think I’d like to be able to keep everyone in filtered pool when in swiss mode, rather than removing them after they battle (makes sense that the loser is removed in gauntlet/champion though). Maybe another option can be added, like the recent change to apply the filters to both sides? I just dropped in a checkbox, but maybe you have better ideas for how options can show up on the UI? Maybe something like a collapsible element?

Is it tracked how many battles each scene has had? It would make sense to me that all the scenes in the filters I regularly return to all have about the same number of battles, and those with less are prioritized for the next pairings… Maybe the logic already does something like this? I just need to keep reading

dtt · March 15, 2026, 2:37am

I might need to add a config menu or something so I can support all these specific settings.

Nope, I currently don’t do any history tracking as I usually use an incognito browser so anything stored in browser would be wiped for me that’s why I avoided it.