| Archangel | |
| HI, I have just performed an update for my off-line editor and have discovered a duplicate 'deliver' order. Order=2010,"Deliver",0x214,5,0,0x17,10.00; OrderName="Position","Item","Quantity","Secure Code","Install"; OrderDataType=0,0,0,2,3; OrderInfoType=3,1,0,5,0; OrderDesc="This order delivers a specific item to another position. If the position is not yours then the security code or an authorisation is required. If the 'install' option is selected and the target position is a ship the items will be installed directly into the ship. Installing items reduces a ships integritry. The target position needs sufficient cargo capacity or install space to carry the items, and if this is not true the order will fail or reduce the quantity transferred."; Order=2011,"Deliver",0x214,5,0,0x17,10.00; OrderName="Position","Item","Quantity","Secure Code","Install"; OrderDataType=0,2,0,2,3; OrderInfoType=3,1,0,5,0; OrderDesc="This order delivers a specific item to another position. If the position is not yours then the security code or an authorisation is required. Unique items can be moved by using there #codes. If the 'install' option is selected and the target position is a ship the items will be installed directly into the ship. Installing items reduces a ships integritry. The target position needs sufficient cargo capacity or install space to carry the items, and if this is not true the order will fail or reduce the quantity transferred."; Of interest here is the OrderDataType values in the second order which indicate Parameters of type integer, string, integer, string, boolean which when compared to the first case the parameter types are integer, integer, integer, string, boolean. Or, in other words, the type of the 'Item' field has been changed from integer to string. A similar duplication occurs with the pickup orders Order=2000,"Pickup",0x214,5,0,0x17,10.00; OrderName="Position","Item","Quantity","Secure Code","Install"; OrderDataType=0,0,0,2,3; OrderInfoType=3,1,0,5,0; OrderDesc="This order picks up a specific item from another position. If the position is not yours then the security code or a 'pickup authorisation' is required. If the 'install' option is selected and your position is a ship then items will be installed into the ship's structure. Installing items reduces a ships integritry. You needs sufficient cargo capacity or install space to carry the items"; Order=2001,"Pickup",0x214,5,0,0x17,10.00; OrderName="Position","Item","Quantity","Secure Code","Install"; OrderDataType=0,2,0,2,3; OrderInfoType=3,1,0,5,0; OrderDesc="This order picks up a specific item from another position. If the position is not yours then the security code or a 'pickup authorisation' is required. Unique items can be moved by using there #codes. Again the data type for the 'Item' field has been changed from integer to string. As indicated in both 'extra' order descriptions the change is to allow for the pickup and delivery of officers using the # codes. The question is now whether orders 2000 and 2010 can be safely deleted ?? | |
| Wraith | |
| I noticed this happen at last upgrade. The difference in the orders means that you can deliver an Officer/Political etc. named "#1" from one position to another. The change you mention between integer and string would support that. But yes, the old order should probably be removed! | |
| Frabby | |
| I suppose the old order wasn't removed because it would cause havoc among starbase standing orders. Imagine you'd have to get an update on all your outposts to check if they had set one of the obsolete transaction orders, and redo it all... Although I agree that the old orders could be removed from the list of active orders so not to be issued anymore. | |
| Auld Nick | |
| Both the orders work, unless you are moving officers, but the lower number produces the comment along side the order "V3.1". If you want to delete one order delete the lower number, that is the one where the item field is an integer. |