QUOTE (gartic @ Nov 29 2009, 03:30 PM)

I have updated the file. Hopefully this one will have everything properly.
http://www.megaupload.com/?d=TR04CKJ0You're probably gonna hate me for this, but...
1. You might want to group the stats at the top in a bit more of a logical way... Meaning; drone stats, "brain" stats, and Autosofts.
Example: three vertical columns of five.
1st column, Drone stats: Body, Acceleration (Accel, which you forgot), Speed, Handling, Sensor.
2nd column, CPU stats: System, Pilot, Response, Firewall, Signal.
3rd column, ubiquitous Autosofts: Targeting, Defense (which you have two of on your sheet, top and bottom of the second column), Clearsight, Maneuver, Covert Ops.
2. Add a "Sensor Notes" area above Armor for those times when you need to know what sensors you have, such as when detecting an invisible mage with Ultrasound or Radar.
3. I know I told you to put ECCM up with the others, but...
Add an Electronic Warfare entry above Armor, but below the "Sensor Notes". Electronic Warfare is one of your available Autosofts (see P. 225, 227, and 240 of SR4, sorry, don't know the pages in SR4A if that's what you're using), but it needs it's own area, so you can note the ECM and ECCM with it. A derived version of Signal + ECCM is also a good idea to quickly note the drone's effective Signal when being jammed.
EW is the Autosoft.
ECM is the rating of a jammer if there is one on board.
ECCM is a hacking program (filter) that allows you to filter out jamming signals.
To use ECM and ECCM you need an EW Autosoft so putting them together makes sense. I'd do it like so:
| EW- Autosoft rating# | ECM- Jammer rating# | ECCM- Program rating# | Signal vs. ECM- derived Signal+ECCM# |
|Notes: *for the type of jammer; directional, area, smart, etc. And, if you're using a Non-standard Wireless Link (Unwired P. 196), or not.*
But, it's your call.
4. You need multiple values for your rigger's Initiative and IPs;
AR- Meat speed, the rigger's meat world Initiative and IPs which is used when working the Matrix through an AR interface.
Cold Sim VR- Normal VR.
Hot Sim VR- When using a commlink modified for Hot Sim.
For details see P. 228 SR4.
Add these entries with your rigger data on the right, either as six blanks to be filled by the user (three for IPs, and three for Initiatives), that auto-fill to the rigging modes; or as just AR and VR slots that the sheet calculates and then auto-fills (it would have to use the VR initiative and IPs twice each, with Cold Sim modifiers for one, and Hot Sim modifiers for the other). Your choice.
Move IPs down to the right of the Rigging mode (Jumped In, Auto, Remote), because they can be different for each mode.
The Drone IPs (Auto) should be set to a permanent three, because that's what it always is. "Auto" Initiative is fine as you have it.
Remote IPs can be AR (the rigger's normal meat IPs) or either of the VRs (Hot or Cold Sim, the two possible Matrix IPs), and all three need to be shown, along with the AR, Hot Sim and Cold Sim Initiatives.
Jumped In is VR only, so show Cold and Hot Sim IPs and Initiatives.
5. Add a 4 or 5 line "Subscriptions" field down with your "Modifications, Weapons, Autosofts" fields, because a drone can be subscribed to multiple riggers, or sent off unsubscribed after getting orders. It can also be subscribed to other drones so they can work together, as well as subscribed to a TacNet (Tactical AR Software, Unwired, P. 124) or Telematics Infrastructure (Unwired, P. 62). So, keeping track of what a drone is subscribed to is kinda important.
6. Don't take all this as criticism, I like your sheet and I'm trying to help. Get it all set and I'll probably use it. I know fuck-all about Excel, so, I can't check your formulas, you'll have to do that yourself, sorry. If I seem kinda picky, I'm sorry, Riggers just happen to be my favorite.
Cheers.