The Agent/Operative "Remove from List" order appears at this point to be useless. Most starbases put entire affiliations on their lists that they would either attack, support or defend. The Order Editor only allows individual positions to be entered into the "Remove from List" order, and when individual positions of a posted Aff are attempted to be removed, a response comes back that the position is not on the particular list.
By way of example:
1) A Starbase has all PIR on it's Space Enemy Lists (pretty standard actually <G>).
2) PIR Starship (123456) wants to orbit the planet to survey it (for whatever reason), but knows that All PIR will be shot.
3) An Operative is inserted into the Starbase and instructed to REMOVE PIR (123456) from the Space Enemy List.
4) The order will technically succeed, yet return the result of "Position 123456 was not on the Starbases Space Enemy Lists"
5) Meanwhile, security has a chance to find the Operative (as the order succeeded), and there is the potential that the Starbase owner will be notified that someone was mucking around in their lists.
6) PIR Starship (123456) get attacked by the Starbase as soon as it enters orbit.
One possible solution would be to have an "Exclusion List" that only accepts single position data and has a flag for which list it applies to (E-enemy, S-support, D-defend, G-ground enemy). This would allow positions to place an entire Aff on their lists, yet maintain an exclusion list of certain "Trusted" positions within that Aff (to facilitate limited trade, etc...), or suspect positions (I don't trust that one guy, so I'm not going to support him...). Anytime a list check is performed, if the result comes up true, then a check could be run against the Exclusion List. If this came up true, then the initial triggering list check would be flagged back to false. This would allow an Agent/Operative to effectively remove a single position from a list. As the "Exclusion List" would appear on the starbase printout each week, any changes to the Exclusion List would be immediately noticeable and able to be corrected fairly quickly. This also means that an Operative should be able to remove a position from the Exclusion List as well (using the Remove from List order) in order to cover their tracks <G>
Just some thoughts. Comments?
Rich Fanning
aka
Lord Lawrence Scrimm
CIA Director of Regional Operations
| QUOTE (Lord Scrimm @ Jun 20 2003, 03:46 PM) |
Just some thoughts. Comments? |
I like this proposal and think it would make a nice addition to the skulduggery aspects of the game.
Kerry
Also game proposals get sent here by me when i'm willing to consider them. There is nopoint putting them here until then as they are still questions....