diff --git a/html/documentation/wiki-snapshot.html b/html/documentation/wiki-snapshot.html index e64e27c50..2a4e687de 100644 --- a/html/documentation/wiki-snapshot.html +++ b/html/documentation/wiki-snapshot.html @@ -834,9 +834,15 @@
Clearing browsing data is strongly recommended if you are upgrading from version 3.x to version 4.x. It shouldn't be needed when switching between different releases of 4.x.
+Enable Replace on Undo. Without Replace pressing the wrong one of the clock controls is a huge pressure situation as every second you don't fix it the clocks run further away and you will have to fix them manually, if that is possible at all. Plus you may have messed up other data, e.g created another jam, which will take more effort to clean up. With Replace you have the time to first think for a moment what just happened and what you can do to fix it and then fix it completely with two clicks/button presses. +(It is planned to make this enabled by default in a future version but as the times when undo is being used tend to be the worst for learning about a new feature by being confronted with it, we want to give people plenty of time to learn about it before that.)
If you are using a Windows system, leave it connected to the internet a day or two beforehand and manually run Windows Update to ensure that patches won't be automatically applied during the game. (Or alternatively, ensure you disable the devices ability to communicate with the outside world so it can't capture updates.)
+Don't rely on Auto-End Jam and disable it when you have control over the ruleset you are using. (But if you are setting up the ruleset for someone else and disable it make sure they are aware.) Simply reacting to the jam ending whistles when they happen takes less effort than checking the jam duration first. And if Jams are not called off on time, your lineups will still last 30s from the end of the jam instead of being shortened (or requiring the jam timer to ignore the publicly visible lineup clock). +(The setting is enabled by default because it has been this way for a very long time and there are a substantial number of people out there that have trained themselves to explicitly rely on it. The default may be changed in the future, when this number drops sufficiently.)
+Clearing browsing data is strongly recommended if you are upgrading from version 3.x to version 4.x. It shouldn't be needed when switching between different releases of 4.x.
+If you are using a Windows system, leave it connected to the internet a day or two beforehand and manually run Windows Update to ensure that patches won't be automatically applied during the game. (Or alternatively, ensure you disable the device's ability to communicate with the outside world so it can't capture updates.)
This is not tracked by the software. Just make a mental note that nothing has to be recorded the next time the jammer emerges from the pack.
(e.g. if your primary scoreboard computer broke down and you need to bring in a spare mid-game