Ascension Match History Add-on

Sakoto · February 11, 2026, 3:06am


	Summary	This is a add-on for the Ascension Stash plugin. Features streaks, color coding, and badges.
	Repository	https://github.com/Servbot91/HotorNot-Stat-Addon/tree/main/plugins/HotorNotAddon
	Source URL	https://raw.githubusercontent.com/Servbot91/HotorNot-Stat-Addon/main/plugins/manifest.yml
	Install	How to install a plugin?

Ascension Stats Add-on

Add-on for the Hot or Not Stash plugin. Features streaks, color coding, performer win/loss ledger and accumulated streaks.

What is the Ascension plugin?

The Hot or not plugin for Stash uses an ELO-style rating system to rank performers and images through head-to-head comparisons. You can find find it here

Features

The Ascension plugin adds custom values to each performer detail page detailing total matches, last match, wins, losses, current streak, best streak and worst streak. This add-on formats the values in a more palatable structure, adds streaks, and color coding for wins\losses. Custom fields is also auto expanded so these values display on load. Supports mobile, and values are displayed as a single column.

Streaks

Streaks are marked by badges and are as follows:

Streak values 3-5:
Streak Values 6-9:
Streak Values 10-14:
Streak Value 15+ :

Easily modifiable via JS. If the streak is broken, the badge resets.

Best Streak

The best streak field retains all of the highest obtained streaks. A streak of 15+ for example will show next to the performers best streak number. If a performer only has a best streak value of 8 for example then they only show next to their best streak.

Performer Ledger

The performer ledger tracks the last 10 win\losses for a performer. The win\loss cards contain win\loss performer name, the value their rank updated to, color coded for win\loss, and a link to the performer profile.

Installation

This plugin requires the Ascension plugin

Settings → Plugins → Available Plugins
Add Source → Name: Ascension Match History Add-on
Source URL: https://raw.githubusercontent.com/Servbot91/HotorNot-Stat-Addon/refs/heads/main/plugins/manifest.yml
Click checkbox, Install
Reload Plugins

Release Notes

03-28-2026 - Version 1.3:
- Screenshot 2026-03-28 103136736×155 128 KB
- Tasks are now specific to hot or not fields. When wiping match history, it will not wipe all custom fields but only fields related to the hot or not plugin
- Added wipe all performer ratings option
- Fixed styles conflict with other plugins preventing performer page to load
03-19-2026 - Version 1.2: Updated to include the new performer ledger feature prodded in update release notes of 3.1.0 - Added task to wipe custom fields or performer match history

image768×114 29.8 KB
02-12-2026 - Version 1.1: Fixed backend UI errors when not in performer card.

Screenshots

panar · March 17, 2026, 7:49am

Great addon! Any thoughts why I’m getting this error in the logs ? Error loading plugin C:\Users\….\.stash\plugins\HotorNotStatsDisplay\HotorNotStats\HotStats.yml: plugin ID HotStats already exists ?

Sakoto · March 17, 2026, 11:07am

Are you using the senpai theme by chance?

panar · March 17, 2026, 12:12pm

Not using the Senpai theme.

Sakoto · March 17, 2026, 8:26pm

Thanks for calling this out. It is fixed, the github workflow was busted and has been corrected now. You should be able to fix by uninstalling via the UI. If it persists delete the folder from the plugins folder location then reinstall. Wont be an issue going forward.

obatzdamelt · March 22, 2026, 4:55am

I kept running into a weird read-only error in an entirely different plugin and pretty sure I have traced it back to this line here. Any chance this const variable could get a stronger name? Having a global const named simply style is pretty likely to conflict with anyone using a throw away variable of the same name. I’ve temporarily fixed this locally myself by renaming it but getting it fixed permanently would be nice so it doesn’t revert in the next update.

github.com/Servbot91/HotorNot-Stat-Addon

plugins/HotorNotAddon/HotorNotStatsDisplay.js

4aba209b2


      
          });
          
          recordObserver.observe(document.body, { childList: true, subtree: true });
          
          recordObserver.observe(document.body, { childList: true, subtree: true });
          
          
          // ===============================
          // Styles
          // ===============================
          const style = document.createElement('style');
          style.textContent = `
          /* Match Timeline Styles */
          .match-timeline {
            display: grid;
            grid-template-columns: repeat(5, 1fr); 
            gap: 6px;
            padding: 8px 0;
            width: 535% !important; 
            font-family: sans-serif;
          }

An example of this conflicting is in this plugin which uses style as a throwaway in a for loop. Example in code below. If you have both of these plugins enabled it errors out on rendering the performer page.

github.com/shinekokunoichi/stash-plugins

plugins/API/Shinobi-Api/Shinobi-Api.js

ed0e75d39


      
          
          /**
           * Return or change the element styles
           * @param {string|object} styles Styles to apply or the style to get {css:value}
           * @param {boolean} [important] If true apply the styles as important
           * @returns {string} Style value
           */
          base.style = (styles, important = false) => {
              if (typeof styles === 'string') return base.element.style.getPropertyValue(styles);
              important = important ? 'important' : '';
              for (style in styles) { base.element.style.setProperty(style, styles[style], important) };
          };
          
          /**
           * Return or change the element attributes
           * @param {string|object} attributes Attributes to apply or the attribute to get {name:value}
           * @returns {string} Attribute value
           */
          base.attribute = (attributes) => {
              if (typeof attributes === 'string') return base.element.getAttribute(attributes);
              for (attribute in attributes) { base.element.setAttribute(attribute, attributes[attribute]) };

shinekokunoichi · March 23, 2026, 2:52pm

wrapping everything in a function should do the trick

Sakoto · March 23, 2026, 11:31pm

Yo thanks for letting me know. Since you got it working locally ill take my time pushing a hot fix but ill take care of this for you probably by the weekend.

Sakoto · March 28, 2026, 3:26pm

Should be good now. Let me know if its still a problem.

Ver 1.3 Fixes

Tasks are now specific to hot or not fields. When wiping match history, it will not wipe all custom fields but only fields related to the hot or not plugin
Added wipe all performer ratings option
Fixed styles conflict with other plugins preventing performer page to load

Sakoto · March 30, 2026, 9:18pm

Patched for stash release v0.31.0. Corrected some minor CSS Styling bugs while I was at it.

Pratik · March 30, 2026, 9:38pm

Post the update, the details are shown as plain text. Pre update it was correct.

Sakoto · March 30, 2026, 10:06pm

You need to update the plugin. My last post corrected this in version 1.3.1. Its due to the new stash release.

Edit: I need to add some backwards compatibility. Ill do that in the next hour.

Sakoto · March 30, 2026, 10:41pm

I just pushed v1.3.2. Can you test and screenshot how it looks??

To be honest my dev env doesnt account for schema migrations but def something I should probably consider in the future.

Pratik · March 31, 2026, 12:17am

now its working thanks