Removing machinegun siege towers

**GrimSta** · 11-23-2005, 16:23

you could always change its ranged attack to 0 in export_descr_unit

**Mouzafphaerre** · 11-23-2005, 16:28

.
Thanks. Will try and see now...
.

**Mouzafphaerre** · 11-23-2005, 16:58

Originally Posted by GrimSta

you could always change its ranged attack to 0 in export_descr_unit

.
Unfortunately, in 1.3's exprt_descr_unit file there's no single mention of any tower (siege or wall).
.

**Red Harvest** · 11-23-2005, 17:42

Originally Posted by Mouzafphaerre

.
Unfortunately, in 1.3's exprt_descr_unit file there's no single mention of any tower (siege or wall).
.

No, but the range is set in the engines file. As well as attack, etc.

**Mouzafphaerre** · 11-23-2005, 18:19

.
Yes, thanks. Was trying to have some sleep (sick today) but couldn't before finding a way or being sure there isn't any.

So, my next target is -again- the engines file.

.

**Mouzafphaerre** · 11-23-2005, 18:30

.
GAH! The engines file has nothing to do with wall towers. But I already knew that, oh well...

.

**Red Harvest** · 11-23-2005, 19:14

Originally Posted by Mouzafphaerre

.
GAH! The engines file has nothing to do with wall towers. But I already knew that, oh well...

.

Correct. The walls themselves appear to be hard coded. I remember seeing some comment notations about something related to the wall tower fire rate in the projectiles or units files (or other?). Think it had something to do with resetting the number of engines in siege units. Might have been a CA comment online though. From it I had the impression that it was hardcoded.

Afterall, aren't the arrow/javelin/sling/ballista/onager fire rates hard coded already? I am thinking that the siege engine fire interval is the only example of the game going around the projectile fire rate hard coding (and making it modable.)

**Mouzafphaerre** · 11-23-2005, 19:37

.
Actually their fire rate seems to be adjustable in the walls file. But the maximum usable number is the question here.

Originally Posted by Shigawire

Ticks you say? in the world of 3d animation, 1000 ticks equal 1 second.

~~So, even if we set it to 1,000,000 ticks, assuming the engine will accept it, we will only get a delay of ten seconds.~~

So, even if we set it to 1,000,000 ticks, assuming the engine will accept it, we will only get a delay of 1,000 seconds (~=17 minutes).

Well, you're right. They are hardcoded.

.