Update README for new setting
This commit is contained in:
1 parent
601b1641d8
commit
134de5fc69
1 file changed
+3
-4
@@ -10,14 +10,13 @@ The alarm cannot be disabled until the user solves their configured number of tr
|
||||
|
||||
Guards are in place to prevent the user from force-quitting/resetting the alarm when an alarm is meant to be active.
|
||||
### Adaptable
|
||||
Trigalarm is meant to be adapted to your needs with as little confusion as possible. There are three powerful settings:
|
||||
Trigalarm is meant to be adapted to your needs with as little confusion as possible. There are four powerful settings:
|
||||
1. Number of triangles to solve in order to disarm the alarm
|
||||
2. The time limit for the final (fastest) triangle
|
||||
- Time limits for prior triangles are calculated automatically based on this one
|
||||
3. Pavlok integration (API key + zap intensity)
|
||||
3. The time limit difference between each successive triangle
|
||||
4. Pavlok integration (API key + zap intensity)
|
||||
- Punishes the user via mild electrocution if they...
|
||||
- ...take too long to respond to the first triangle
|
||||
- ...get demoted from a higher level triangle
|
||||
- ...force quit the app by holding the back button (the app re-opens and sends a zap)
|
||||
## Tips & Tricks
|
||||
- When you successfully disarm the alarm, you are prompted with the options to either exit and keep the same alarm time for tomorrow, or to select a new time. If choosing the latter, whatever time you select will assume you mean tomorrow. This avoids situations where you wake up at 6 on a Friday, set an alarm intended for 9 on Saturday, and end up with your wrist buzzing in three hours!
|
||||
|
||||
Reference in new issue
Block a user