QUOTE
name='Triangle Games-Master' date='Nov 10 2011, 07:38 AM' post='533405']
I've played around with C++ at home (yes, I own a "For Dummies" book),
me too

, that and a host of other books, and what not. I love coding. I'm still just getting good at it, but it's a lot of fun, lol.
QUOTE
Facilitating die-roll combinations would be handy, like 2d6 for instance.
That's actually a good idea. I had thought of it, but I wasn't considering amount of dice rolled. Thanks for that. Easy enough. Pass in a variable for amount of dice, up to say 10, because no one should need more than that. Then have a variable passed in for what type of dice it is. Having all the standard roll playing dice.
QUOTE
If possible, a combat calcuclator,
not the entire combat "scene" or overall function since there are SO many ideas how to run that,
but rather just a tool for calculating the technical events in a single round of action.
This actually sounds interesting, but I'm not sure what you mean. Could you explain a little more. This reminds me of a function that I alread created for the library. It's a random sword strike battle function. It takes in a variable RanSwordStikesID if this is 1 it generates a for a light attack, if it's 2 it generates for a critical attack. It also takes in DamageAmount, Enemy Health, and a string Enemy Name. It calculates and subtracts the damage from health, outputs a message for the attack, and returns the remaining health.
example light attack : " sword grazes [enemy name] for [DamageAmount] damage"
example criticle: "Blade gashes [EnemyName] doing [DamageAmount] damage."
I'm creating these methods for a ton of weapons types. Also if the user wants to work with their own variable and math they can use the functions that I'm creating to parralell the battle functoins except they only generate the damage discription, no math involved.
QUOTE
A method for tracking/organizing changes in party size and character order.
That's a good one too, but I'd have to think hard about it. lol, still learning as I go.
QUOTE
An equipment storage array for an "Items Menu" to access.
That's a good idea. I'm sure it would be possible to create this array inside a function, and have the function save the array details to a ini file, or something simular.