Merge branch 'main' into main

Author: bosh

README.md

@@ -1,4 +1,3 @@
-
 # Mission Pinball website & documentation
 
 This repo contains all the source code for [MissionPinball.org](https://missionpinball.org), which also includes all user documentation.

docs/code/BCP_Protocol/ball_end.md

@@ -1,7 +1,6 @@
+# ball_end (BCP command)
 
-## ball_end (BCP command)
-
-Indicates the ball has ended. Note that this does not necessarily mean that the next player’s turn will start, as this player may have an extra ball which means they’ll shoot again.
+Indicates the ball has ended. Note that this does not necessarily mean that the next player's turn will start, as this player may have an extra ball which means they'll shoot again.
 
 ## Origin
 Pin controller
@@ -12,4 +11,3 @@ None
 ## Response
 
 None
-

docs/code/BCP_Protocol/ball_start.md

@@ -1,4 +1,3 @@
-
 # ball_start (BCP command)
 
 Indicates a new ball has started. It passes the player number (1, 2, etc.) and the ball number as parameters. This command will be sent every time a ball starts, even if the same player is shooting again after an extra ball.

docs/code/BCP_Protocol/device.md

@@ -1,4 +1,3 @@
-
 # device (BCP command)
 
 ## Origin

docs/code/BCP_Protocol/error.md

@@ -1,4 +1,3 @@
-
 # error (BCP command)
 This is a command used to convey error messages back to the origin of a command.
 

docs/code/BCP_Protocol/goodbye.md

@@ -1,6 +1,5 @@
-
 # goodbye (BCP command)
-Lets one side tell the other than it’s shutting down.
+Lets one side tell the other than it's shutting down.
 
 ## Origin
 Pin controller or media controller

docs/code/BCP_Protocol/hello.md

@@ -1,4 +1,3 @@
-
 # hello (BCP command)
 This is the initial handshake command upon first connection. It sends the BCP protocol version that the origin controller speaks.
 

docs/code/BCP_Protocol/index.md

@@ -1,4 +1,3 @@
-
 # BCP Protocol Specification
 
 This document describes the Backbox Control Protocol, (or “BCP”), a simple, fast protocol for communications between an implementation of a pinball game controller and a multimedia controller.
@@ -7,11 +6,11 @@ This document describes the Backbox Control Protocol, (or “BCP”), a simple,
 
     BCP is how the MPF core engine and the MPF media controller communicate.
 
-BCP transmits semantically relevant information and attempts to isolate specific behaviors and identifiers on both sides. i.e., the pin controller is responsible for telling the media controller “start multiball mode”. The pin controller doesn’t care what the media controller does with that information, and the media controller doesn’t care what happened on the pin controller that caused the multiball mode to start.
+BCP transmits semantically relevant information and attempts to isolate specific behaviors and identifiers on both sides. i.e., the pin controller is responsible for telling the media controller “start multiball mode”. The pin controller doesn't care what the media controller does with that information, and the media controller doesn't care what happened on the pin controller that caused the multiball mode to start.
 
 BCP is versioned to prevent conflicts. Future versions of the BCP will be designed to be backward compatible to every degree possible. The reference implementation uses a raw TCP socket for communication. On localhost the latency is usually sub-millisecond and on LANs it is under 10 milliseconds. That means that the effect of messages is generally under 1/100th of a second, which should be considered instantaneous from the perspective of human perception.
 
-It is important to note that this document specifies the details of the protocol itself, not necessarily the behaviors of any specific implementations it connects. Thus, there won’t be details about fonts or sounds or images or videos or shaders here; those are up to specific implementation being driven.
+It is important to note that this document specifies the details of the protocol itself, not necessarily the behaviors of any specific implementations it connects. Thus, there won't be details about fonts or sounds or images or videos or shaders here; those are up to specific implementation being driven.
 
 !!! warning "Infinite Loops Possible"
 
@@ -94,5 +93,3 @@ The following BCP commands have been defined (and implemented) in MPF:
 * [reset_complete](reset_complete.md)
 * [switch](switch.md)
 * [trigger](trigger.md)
-
-

docs/code/BCP_Protocol/machine_variable.md

@@ -1,4 +1,3 @@
-
 # machine_variable (BCP command)
 This is a generic "catch all" which sends machine variables to the media controller any time they change. Machine variables are like player variables, except they're maintained machine-wide instead of per-player or per-game. Since the pin controller will most likely track hundreds of variables (with many being internal things that the media controller doesn't care about), it's recommended that the pin controller has a way to filter which machine variables are sent to the media controller.
 

docs/code/BCP_Protocol/mode_list.md

@@ -1,4 +1,3 @@
-
 # mode_list (BCP command)
 This message informs the media controller about which modes are currently running. It is sent whenever a mode starts or stops, but only to clients currently [monitoring](monitor_start.md) the `mode` category.