Tech Tree

[winsrp]

well the problem i see here is that is not exactly a tree... its a node array, and as such you can get some real scrambles, like when on your tree you have (look above/below) for something that should already been researched...

I think it would be really cool to have an automated graphical tree, where you can select just a single upgrade, and it will do the node graph of what it takes to get there, since when i see the hole node array for all upgrades, i cant even follow the lines right.... i get lost.

[Anon]

The new tech tree is great. However, there's still one thing I like in the old one: data such as accuracy, ROF, etc. for defences, or range for sensors... Sure, often I can go look for the equivalent under Turrets, but it's not very practical, and sometimes there is simply no equivalent (eg. canon fortress).

[Zarel]

The new tech tree is great. However, there's still one thing I like in the old one: data such as accuracy, ROF, etc. for defences, or range for sensors... Sure, often I can go look for the equivalent under Turrets, but it's not very practical, and sometimes there is simply no equivalent (eg. canon fortress).

Actually, at the bottom of Turrets, there are "structure-only weapons", which is intended to resolve this issue: http://guide.wz2100.net/w/#struct

I'm planning on adding detailed statistics to the structure charts, but at the moment I haven't done so.

[Anon]

Oh ok. Solves my problem for now I guess, thanks .

Some time ago I was planning on doing a similar tech tree, and I'm wondering... Do you generate it by parsing the data files, or do you write it manually?

[Zarel]

Some time ago I was planning on doing a similar tech tree, and I'm wondering... Do you generate it by parsing the data files, or do you write it manually?

Parsing data files.

Here's an example of what a parsed file looks like:

http://guide.wz2100.net/cache/research.inc.txt