The table of contents is as shown below.

From last year, we have improved a lot from our previous standards.. Before Nationals last year, Andrew had already begun to work on improving the code, so that we had a proper menu.

The Code Design Process

The design process for our code was as follows:

• Get a working gyro readout

• Get a "working" menu setup

• Realise the menu did not work, so go back to the drawing board.

• Find the Seshan Brothers menu system, and make improvements to it

• Add in our original configuration code (Gyro, Colour, Motor)

• Add in a gyro drive

• Think about whether some pieces of mathematics were required in the gyro drive

• Realise that it was required

• Add a gyro turn

• Find that the gyro turn did not work

• Find the Seshan Brothers gyro turn, and draw inspiration from that

• Find the Seshan Brothers PID line follower, and use it

• Calibrate both the line follower and gyro turns

The Robot Design Process

For our robot design, we did the following, in order

• Decide what key parts of the robot have

• Those parts being 2 large and medium motors, 2 colour sensors, a gyro sensor and a touch sensor.

• Place the motors, sensors and brick in a rough shape of what we wanted the robot to be

• Realised  it might save space if we only had 1 colour sensor, but if the time comes, we could reconfigure the robot design to include 2 colour sensors.

• Begin to connect the motors to the brick, and then the sensors.

• Add a frame

We decided to go with the second design, with some modifications to fit everything in and be sturdier. We got the attachment motors on, the sensors on, everything connected to the brick and framed, then decided to improve some more, by moving the attachment motors, adding a second colour sensor and improving the sturdiness of the frame. We also considered renaming it, with some suggestions being "Boxetta", "Bee" and "Boxetto", on account of Boxbot V2.1 being framed in such a way that it looked similar to Bumblebee, from the Transformers movies, and the fact that we wanted to continue using the "Box..." theme. We decided that we had reached Boxbot V2.2.

We also realised that we didn't need to make everything above the O frame slip on/off, and instead just made a system to access the brick, without permanently removing anything else. We decided that we would need to colour code Boxer's wires, using 1x3 coloured beams and loom bands, but hadn't gotten around to that yet.
In the end, we managed to get a robot that was 3 studs longer than T.R.I's robot, which was the aim of Andrew, who was a main coder, and who realised that Spike was much more compact compared to Mindstorms, and was rather persistent on getting the robot to be extremely compact.

For fun, we decided to put an FLL chicken into our robot, and considered including a spring, for fun (Alright, and also for miscellaneous fidgeting). We decided not to, though, due to space constraints.

We then began duplicating the robot (which we named Boxetta) and made "Hattachments" - placeholders that go onto the top of our robot to hold attachments. Because it went on top, we thought it was like a hat. We made 3 of these, and then created 2 more a couple of weeks later. 

We ended up designing some attachments to go onto the "Hattachments". For example, for a lot of missions, there was a claw action that could be done. So Iain and Muse had designed a working claw that came off of the top motor. The missions that would benefit from this attachment was M01, M02, M04 and some collection of materials for M15. There was also  a passive attachment that was used for M04 and M01 to get the Scuba Diver and the Coral tree onto their support. There has also been innovation for the Unexpected Encounter Mission. The plan originally was to build an attachment for the "Droptopus" to go onto, but it was found that it was easier to just let the "Droptopus" go onto the top of the robot and make it back to home. 

We finished duplicating Boxetta, although we ended up without the FLL Chicken or a Spring within it. We then worked on creating attachments for certain missions, with varying success. Aaryan also worked on creating a dud robot, which was just a frame on wheels, to work on his hattachment without needing a full robot. He eventually succeeded, and it was used thereafter.

Iain created 2 boxes, for the Unexpected Encounter Droptopus, and the Shark, as well as a "hook" and one-way trap (Tim made it, Iain utilised it) for the Coral Tree and collecting the shrimp and coral. The one-way trap was later added to his hook hattachment, for compaction during Equipment Inspection.

Tim, meanwhile, created a dropping system for Feed the Whale, which was mostly reliable 3 weeks prior to the tournament.

We managed to make a lot of progress in the three weeks leading to Regionals, with 6 runs by tournament, allowing us to score enough to get to Nationals, which we compacted our code significantly for, with some reliability improvements.