ptb
	Date 41.4: Pickup {22735} {1} {30000} {(null)} {Install - No} Teleporters picked up 30000 Metals (1) from RIP Remote 1 (22735) Notice the null because there was no code (it's my position), i assume there might be other such (null) cases. Minor issue
MasterTrader
	I don't think this is a bug. In this case the "(null)" is not in the actual action result, but just showing that there was an order field that was not completed. I think that it is helpful to be aware that the security code was not used in the pick up; that way you know that any authorisations are working, for example. Richard AFT
David Bethel
	Its a bug of a kind. printf very generously does not crash if you pass it NULL, and just prints (null). At some point in the saving process, i did not catch all the nulls. edit: I found/fixed a standing order issue with this, but i can not find a problem in the standard orders.... any other details about how the order was issued.
ptb
	opps... you wanted this line too ------------------------POST PRODUCTION STANDING ORDERS-------------------------
David Bethel
	So that will be fixed in future howvere the (null) will stay until the standing order it sremoved.