Uniform names for need stats

[GoogleCodeExporter]

If hunger/poop is too low, it represents the hunger need and if it's too
high, it represents the poop need.

We must add some uniformity to the names we choose for the new stat needs
we will create, or else, it will get confusing.

Problem:
If we keep the current logic for the names we give to the needs, some needs
will have awkward and confusing names.

Proposed solution:
We should rename all the needs so they represent the substance of WHAT is
needed (or sometimes, NOT needed (when the stat is too high)) rather and
giving names which represent situations when the need is too low or names
which represent the various level of satisfaction the concept could represent.

Proposed new names:
Hunger -> Food
Thirst -> Water
Sleepiness -> Sleep
Heat (rather than temperature)
SocialCohesion
Happiness
IntellectualStimulation
MaleOrgasm
FemaleOrgasm
ChildBirth
Light

Original issue reported on code.google.com by glaca...@gmail.com on 1 Dec 2007 at 4:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Agreed. It will simplify things when we get to having more complex needs. This 
is a
bit like having properties called "nutrition" instead of something like 
"nutritiveness".

Original comment by tristanl...@gmail.com on 2 Dec 2007 at 2:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

integrity -> health?

Original comment by tristanl...@gmail.com on 2 Dec 2007 at 3:37

[GoogleCodeExporter]

I agree for integrity -> health

Original comment by glaca...@gmail.com on 2 Dec 2007 at 7:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This issue has been fix and tested by me.

Original comment by glaca...@gmail.com on 4 Dec 2007 at 3:45

• Changed state: Fixed