About Tiberium

[Crimsonum]

How can I place different types of Tiberium on a map? The XCC editor only displays one type, with all of its 12 growth stages. I've seen that it's possible to view the other variables of Tiberium in the editor, by opening one of the official maps.

[pichorra]

Use CCWMAP: http://www.cnc-comm.com/community/index.php?action=downloads;sa=view;down=2

 

Tip: Use Windows NT4.0 Compatibility for better stability of the program.

[Crimsonum]

I have that program. IIRC it's the same, only the "add random Tiberium" feature adds other Tiberium types (randomly).

[pichorra]

into overlay menu.

[Nyerguds]

I'm not sure how exactly tiberium states work in C&C1. It seems ti1 is indeed less dense than ti12, but ti12 only actually shows the "TI12" variations of the tiberium SHP files, which does make it rather monotonous.

 

The growth state is definitely influenced by the cells of tiberium around it though, just like in RA1; even TI12 is never grown to full side at a map border.

 

I'd say, make sure to vary between the tiberium types TI8 to TI12. In XCC, just like in CCMap, you can find them in the Overlay section.

[Crimsonum]

into overlay menu.

 

You just pointed out the problem. There is a handful of different types displayed in random stages, not all of them.

 

I'm not just talking about the growth stages, but the different overlays. IIRC there's 12 of them, each with 12(?) growth frames. That would make 144 placeable overlays. Yet there's only 12 of them. Unless the engine changes the frame of the Tiberium overlay which it displays depending on the density of the Tiberium field (ignoring what stage you place on a map)? In that case you'd only need 12 placeable overlays, but XCC Editor seems to allow placing only a single type, with its 12 growth stages. CCMap seems to have it the correct way.

[Nyerguds]

Eh, that doesn't matter at all. No matter what xcc editor displays, in the ini it's just gonna look like

2414=TI8

 

"cell number=overlay type"

 

What exactly that TI8 means is up to the engine. Nothing the editor can do about that.