2 questions.....

[Long Happy Man]

I was reading some useful modding tips on this site and while tweaking around with the editor I have some questions :

1) if I change let's say the prereq. of Map Making to Writing, Pottery and Literature (originally only Writing and Pottery), does it automatically draws an arrow from Literature to Map Making in the science advisor screen? or I do have to do some graphic editing?

2) In the Civilopedia.txt file, some tech entry are listed for example #DESC_TECH_Pottery and some are like #TECH_Map_Making. What difference does the DESC make?

[Spatzimaus]

If you've changed the basic civ3mod.bic, it won't move the lines and you'll have to edit them yourself. There are some good posts in this forum to explain how.

If, however, you load your .bic as a Scenario, it automatically connects each tech to its correct prerequisites. However, it simply uses straight, gray lines instead of the nicer default ones, and each of these lines connects the center of the prerequisite to the left side of the later tech. It also has a nasty tendency to lose icons if you reload your savegame without going to the main menu, leaving you with a tech tree full of blank boxes.

Several techs should be moved a bit if you do this, as the shortest-line approach tends to put their lines through other techs.

[Spatzimaus]

oops, forgot the second question.

Each tech has two entries:
TECH_Pottery
This gives the info you get when you pull up the civilopedia entry. For example, if Medicine says "removes disease from flood plains" that'd go there.
DESC_TECH_Pottery
When you pull up the pedia, notice there's a button under the picture (upper right) that's labelled DESCRIPTION or something? When you click on that, it replaces the previous screen with one giving a brief historical background on the unit. That's what goes in this section.

[Kuciwalker]

Actually, there's a secret code word that you type in while playing the game that allows you to access scenario editor functions, including a Civ2 style cheat menu, a powerful events language, and a completely bug-free rules editor.

Banana.