actually reading the manual

[dexter4dxm]

i was introducing my bro to Civ 3 today, and I thought I could get a better idea of how to explain all the rules to him if I looked in the manual. Of course, the thing has been collecting dust since I bought the game, I just want to play and play. Now that I began reading a little from it, I'm actually learning about little things I didn't know about. Like for example, did you know that Walls have no effect on defence for cities that are size 7 and above?

So, I guess what I want to know is:

Have you read the manual?

Are there any other little interesting rules you've found?

[Wrong_shui]

Ive read it.

Im not gonna tell u all the ending though, dont wanna spoil it.

[SithUK]

Im not gonna tell u all the ending though, dont wanna spoil it.

Too bad I am.......last line is.......

"We i.e. firaxis, infogrammes and the rest of the world's evil minions only released this game to test the patience of the Civ community. Bah."

Or was that the end of my nightmare last nite....ah can't remember, need coffee.....

=p
Sith

[Proteus_MST]

Sure I have

Everything in the Manual is interesting, if it answers the Questions you have (and saves the time you need to post the Questions in the Forum )

[Thomas Paine]

Actually, the last line of the manual reads, "For the purposes of this Paragraph, both parties submit to the jurisdiction of, and waive any objection to the venue of, the state and federal courts of the State of New York." (p. 220)

Hmm... . Apparently it has something to do with building the courthouse improvement in all of your cities.

[cavebear]

The first thing I did after opening the box was to read the manual, cover to cover, then re-read several parts. Some of the things I learned were quite surprising (like that part about the city walls and size 7+ cities). Most of those things were useful. A few were just wrong (but the readme.txt cleared those up).

I don't always read instructions (sometimes things are just obvious). But with anything complex (like programming), I can't imagine why one would not read a manual. I never assumed that Civ3 was just a slightly modified version of Civ2.

The units chart was quite a surprise. I can only imagine how difficult it would be if I tried to use the Civ3 archer like the Civ2 one (man, that Civ3 archer is a wimp). How would one understand why you lost a city to "cultural expansion" (it would seem like a Civ2 spy thing).

I suspect that a lot of players contruct a sort of "mental manual" by asking questions on this site, one surprise at a time (I just don't have that kind of memory or habit of observation).

[Redstar]

one interesting things is...

no designer notes.

according to the civ2 one...Sid spent only 1 day on the project.
and it explained their rationale for the combat system.

I would have liked to have seen one for civ3. It would have been even more interesting given the choices.

[Kolyana]

Re: one interesting things is...

Originally posted by Redstar
no designer notes.

according to the civ2 one...Sid spent only 1 day on the project.
and it explained their rationale for the combat system.

I would have liked to have seen one for civ3. It would have been even more interesting given the choices.

You're kidding me, right?

1 day? That doesn't seem right.

[Xentropy]

Originally posted by Thomas Paine
Actually, the last line of the manual reads, "For the purposes of this Paragraph, both parties submit to the jurisdiction of, and waive any objection to the venue of, the state and federal courts of the State of New York." (p. 220)

Hmm... . Apparently it has something to do with building the courthouse improvement in all of your cities.

Funny, the end of my manual reads, "You must be 18 years or older or have parental permission to call the above 900 number (touch-tone phone required). The hint line is only available in the U.S. 08251"

Of course, that isn't a numbered page, so really I guess the last line on the last page of my manual reads, "writing, 43, 96, 138"

[Redstar]

yup

the exact quote is..

"Civilization II began as a day long brainstorming session aroud Sid Meier's round table with Sid, Brian Reynolds, and Jeff Briggs.
Brian then retreated to the dales of Yorkshire for a year to formulate the design and put together a series of prototypes which eventually became the game engine...."

It then goes on to mention a bunch of other people who worked on it.