From 4ba8c3a22b30408d97ebfdb56c1a9a0116e0586f Mon Sep 17 00:00:00 2001
From: holo <holo@thewisewolf.dev>
Date: Wed, 24 Sep 2025 21:49:25 +1000
Subject: [PATCH] Add config technical note

---
 Home.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Home.md b/Home.md
index ff1646b..d3b0d1d 100644
--- a/Home.md
+++ b/Home.md
@@ -59,6 +59,15 @@ For further configuration, see the next section.
 ## Configuration
 The name, points added per contribution, seconds added per point, and timer cap of the subathon are all dynamically configurable with `!subathon config`. Running `!subathon config` itself will show you the list of options and their values, `!subathon config <option>` will show you the current value and further information about that option, and `!subathon config <option> <value>` will set that option to the provided value, if possible.
 
+
+Scoretable (scores) adjustments are *not* retroactive. If, for example, a t1 subscription was given that contributed `5` points, and the `t1score` was then later raised to `10`, that contribution would still only contribute `5` points.
+
+Timer cap (cap) adjustments *are* retroactive. That is, even if a contribution was given while the timer was capped and did not raise the timer, if the cap is increased, then that contribution will now be counted towards the timer.
+
+Timescore adjustments are also retroactive. This means that if the timescore is updated, every previous contribution will now be treated as contributing the new amount of time to the timer. This is particularly dangerous because if the timescore is reduced, the subathon may end prematurely.
+
+**Technical note:** Each contribution is saved separately with a user (if given), timestamp, **number of points**, and associated event (e.g. subscription or bit contribution) if it exists. Time *earned* is calculated by summing the contribution points and multiplying by the *current* timescore. This is what gives rise to the sometimes-retroactive behaviour of the configuration. Since the contributions *are* saved separately with their event data this also means that in a pinch the historical score contributions can be adjusted or rebalanced if they do need to be, with some database magic server-side.
+
 | Usage | Permissions | Description |
 | --- | --- | --- |
 | `!subathon config` | Moderators | Display a summary of the current subathon configuration. |