Quote:
Originally Posted by Muhznit
Normally I just hide in the shadows and patiently wait for you to answer notes on dev. art (It's a bit cumbersome that you insist on their system being the one to use). But I thought I'd pop out of my cybercave to comment on the way stats are handled.
Ahem.
Having stats handled that way is interesting. I considered something like that a while back where you would have a stat in the the range [0,1] (can be translated from yours using the equation y = x / 2 + .5, where -1 <= x <= 1 and 0 <= y <=1) That value could then be used as an interpolation factor across an array of say, breast sizes. That way, as I come up with more ways to describe breast sizes, I could just add them into the array and have increasing amounts of detail over the course of the game development.
So, you might have just "big", "huge", and "massive" to describe breasts at first, but later on the array would expand (pun!) to become "large", "big", "enormous", "huge", "giant", "massive", "gigantic". In using y = .3 to map to these arrays of sizes, it would first represent "big", (y * numberOfListElements = floor(.3 * 3) = 0, words[0] = "big"), and over time as more amounts of detail are added to the sizing system, y would later represent "enormous" (floor(.3 * 7) = 2, morewords[2] = "enormous").
Discreet Values being used to describe breast sizes is so high school.
|
*nods*
That's exactly the way I was thinking of doing the size descriptions
Edit: The line 11 error is problematic. I think I'll rephrase that codeline into something else and see how that goes.
Edit2: I'm going to make a "CuddleBeam Plays the Beta" youtube video with commentary for those of you curious folks who want to see what the beta looks like. Should be fun.