Ive noticed, while looking at the various tools, that there are three categories that they seem to fall into.
1. Character creators.
2. Dice Rollers.
3. Reference materials.
There is, I feel, a rather glaring gap in tool coverage that I have set out to cover.
Bookkeeping. Yes bookkeeping.
I'm talking about things like keeping track of each of the ammo counts for the weapons you have on you. How much damage you've taken. Your dicepools in any given situation while easily selecting which modifiers apply without having to remember or look out the penalty. These are the goals that I'm aiming for including potentially adding a dice icon next to each pool so that pressing that button rolls the dice for that pool rather than an application where you must type in the value you want to roll.
Some of the original ideas for specific goals can be viewed at the below Google docs spreadsheet. Specifically, the Combat Dice work and Combat Data provide the basics. In case it isn't obvious, the ugliness of buttons in Google docs and the poor features provided by Google Scripts is what pushed me to this application.
https://docs.google.com/spreadsheet/ccc?key...ZlVPbV9DSjdacGc
Some specific goals.
-Character Arsenal/Closet/Garage: The application will store an arsenal of the modified weapons of a character. At the very worst case it would require manual entry of each weapon, the modified Damage, AP, Ammo, Ranges, etc (sans ammo) as well as what ammo types you have available for that weapon. This same style will be applied to a character closet for selecting currently "active" armor for damage resistance tests as well as a character Garage that you can use to select the vehicle you're using for any vehicle tests that may crop up.
-Other dice pools: I want the application to also keep track of all other dice pools in an easy to browse fashion.
-Running Commlink: I want to have the player be able to load all available programs (and their relevant attributes) and be able to dynamically select what is running on the commlink for matrix dice pools and determining if the commlink is overloaded.
-Magic Stuff: I'll admit it. I have practically zero knowledge regarding the magic system in Shadowrun, so while I would like to include it, I don't have the rules understanding to make sure what is needed is being taken care of.
While the idea of manually entering weapons/armor/vehicles and everything may sound tedious, the value I perceive is that the application will be source book independent. It will require minimal updating to permit new items. For example, if I put an Aiming Bonus attribute on a weapon, that covered laser sights and smartguns, as well as reflex sights. Additionally, since some people may disagree on whether reflex sights stack with either of those bonuses, having an open entry permit either method to be applied. This also makes the application receptive to custom weapons or vehicles.