🕸Fergus Duniho wrote on Thu, Apr 21, 2022 02:46 PM UTC:
During the night I changed my mind on one of my rule suggestions. I had proposed allowing capture of a piece on the occupied space of a switch when a piece moves to the unoccupied space of a switch. This was to fit in with rules regarding no double occupancy of switches and blocking any movement through the switch when one space in it is occupied. These happen to be the most difficult rules to program, and I don't think they're really essential to the concept of a switch. So, I'm going to program a stripped-down version of Chess66 that I'll call Reroute66. This will treat each space as a fully separate space, and the main feature of a switch that I'll retain is that spaces in the switch share some routes to and away from them, and movement from the narrow end can go in either of two different directions. I'll get to work on it later in the day.
During the night I changed my mind on one of my rule suggestions. I had proposed allowing capture of a piece on the occupied space of a switch when a piece moves to the unoccupied space of a switch. This was to fit in with rules regarding no double occupancy of switches and blocking any movement through the switch when one space in it is occupied. These happen to be the most difficult rules to program, and I don't think they're really essential to the concept of a switch. So, I'm going to program a stripped-down version of Chess66 that I'll call Reroute66. This will treat each space as a fully separate space, and the main feature of a switch that I'll retain is that spaces in the switch share some routes to and away from them, and movement from the narrow end can go in either of two different directions. I'll get to work on it later in the day.