diff --git a/docs/customisation.rst b/docs/customisation.rst
index 085d87de..3527da91 100644
--- a/docs/customisation.rst
+++ b/docs/customisation.rst
@@ -55,6 +55,43 @@ Try the above robot by pasting this into a ``.yaml`` file and invoking ``ev3sim`
 
 The rotation of all elements is measured in degrees, where 0 bearing is pointing to the right of the screen (which is assumed to be the front of the bot), and positive degrees indicated a counter-clockwise rotation.
 
+Buttons
+-------
+
+In addition to the usual devices, you can also add working buttons to your robot which can be interacted with as you normally do on ev3dev2.
+Just like with the devices, you specify a position, rotation, and port for the button. The port value determines which button this is recognised as, and can be ``up``, ``down``, ``left``, ``right``, ``enter`` or ``backspace``.
+
+.. code-block:: yaml
+
+  devices:
+  - Button:
+    position: [5, 0]
+    rotation: 0
+    port: enter
+
+Interacting with this button is as usual on the ev3dev2 code:
+
+.. code-block:: python
+
+    from ev3dev2.button import Button
+    from ev3sim.code_helpers import wait_for_tick
+
+    buttons = Button()
+
+    def state_change(state):
+        if state is True:
+            print("Enter pressed!")
+        else:
+            print("Enter released!")
+
+    buttons.on_enter = state_change
+
+    while True:
+        if buttons.up:
+            print("Up is being pressed!")
+        buttons.process()
+        wait_for_tick()
+
 Simulation Definitions
 ----------------------
 
diff --git a/docs/ev3_extensions.rst b/docs/ev3_extensions.rst
index d69c4b94..0ad05e3b 100644
--- a/docs/ev3_extensions.rst
+++ b/docs/ev3_extensions.rst
@@ -40,6 +40,48 @@ Importing this means you need to transfer ``ev3sim/code_helpers.py`` onto the br
 
 .. _code_helpers.py: https://github.com/MelbourneHighSchoolRobotics/ev3sim/tree/main/ev3sim/code_helpers.py
 
+Handling simulation events
+--------------------------
+
+While in simulation, for various reasons you might want to react to certain events occuring in the simulator.
+As an example, your code may want to be aware of when an enemy (or you) has scored a goal, so you can change playstyle, or evaluate current strategy.
+
+To handle such events you can use the code helpers EventSystem:
+
+.. code-block:: python
+
+    from ev3sim.code_helpers import EventSystem, wait_for_tick
+
+    def handle_scored(data):
+        if not data["against_you"]:
+            print("I scored a goal!")
+        else:
+            print("No we let them score!")
+
+    EventSystem.on_goal_scored = handle_scored
+
+    while True:
+        EventSystem.handle_events()
+        wait_for_tick()
+
+``EventSystem.handle_events`` must be called often (ie in every loop iteration, simply add this line after every occurrence of ``wait_for_tick``) to allow such events to fire the related code. Any event in the system returns a data object, which will contain any useful information about the event.
+
+Importing this means you need to transfer ``ev3sim/code_helpers.py`` onto the brick for this to run (Just create a folder named ``ev3sim`` and place `code_helpers.py`_ in there).
+
+.. _code_helpers.py: https://github.com/MelbourneHighSchoolRobotics/ev3sim/tree/main/ev3sim/code_helpers.py
+
+The full list of events is:
+
+``on_goal_scored``
+^^^^^^^^^^^^^^^^^^
+Fires whenever a goal is scored by either team.
+
+* ``against_you``: True if the enemy team scored against you. False otherwise.
+
+``on_reset``
+^^^^^^^^^^^^
+Fires whenever the game is reset manually.
+
 Robot Communications
 --------------------