I'm concerned about the number of calls to `simulator.error()` we're adding, especially since they're all passing it a message they didn't create, since that function displays a message to the developer in the primary interface, and we should be very careful about such messagse (unlike messages we write to a secondary interface like a console), because they are disruptive.

We should audit all such calls and make sure we're displaying information that it is absolutely necessary to display and that makes sense to the developers who will be seeing them.