First of all:
Hastur is on crack. Don't take him seriously.
However with his random jumping and wild guesses
he has hit a few good points.

>4) You aren't the player I design for. The player I design
>for plays games to have fun, not to run simulations. I'm not
>sure if you're the player that anyone designs for. If every
>player was you, I'd move to another MUD before conforming to
>the style of administration you want, because it would be the
>most boring place imaginable.

There is one obvious thing about CF.
It is so obvious that many fail to notice it.
Immortals constantly enforce roleplaying
and constantly try to hinder number-crunching.
Why is that?
Ask this question not a philosopher but a child and he will asnwer:
"That is because people don't like to roleplay
but they like to PK and thus they are crunching."
Now you can start to deny that.
After all, why would there be a need to enforce something
that everyone likes and tries to do anyway?
And why to hinder something that people don't like to do
and avoid to do anyway?

>5) It's not even practical to enumerate what effects what in a
>lot of cases. Bash is ~600 lines of code. The skill
>is potentially effected by dozens of things. No one wants
>helpfiles that are 3 pages long. Good luck reverse
>engineering that, by the way.

I don't mind to have help files that are 3 pages long.
I would prefer to see a detail help file and trust me
I'm able to skip its parts that would be unimportant for me
rather than to see a very vague roleplaying help file
that gives me slightly above the usage syntax.
And if I want to have a clue how this or that skill/spell works
I have to create a test character.
Many people actually do that ( I don't merely because I don't have time for that )
A good example is the whole deal with legacies and their help files.
Every second deleted warrior writes that he rolled just to test legacies.