Recommend @The Squar-Cube Law approach - flow charts, but from technological tree point of view - technologies are not just chain one after another, how it is done in many games very primitive dependencies, in reality it has more complex codependance - what it requires and what it provides. So as versioning is important, as an example - Glass making v9.5.6 depends on a lot of stuff, while glass making v0.0.1 it depends on few, what they provide is also different.
In that sense more closer way is to imagine it like linux packaging dependencies, so as linux package managers more suitable to keep track of such things(and other managers of that kind).
Have seen few open tech projects/initiatives and one of those used wiki to record technologies and their dependencies and what it provides - not such a shabby way to do that.
In that sense JSON is sufficient to keep track, and descriptions and dependencies, and what it provides etc, so as any markup language really.
Then use some python(as an example) to show it in some sort of flow chart/tag cloud (will require googling, but seen not such bad visualisations of that kind, so stuff is out there)
So depends on complexity, low/moderate complexity a flow chart can be quite good, especially when there are different applications under mind mapping name, so as flow charts online etc.
can't comment due old browser so this way
Will to be honest I planned a pretty default tech tree without such realism. Would be happy to know how one can find mentioned "tech wiki" still. –
Example of article from wiki I mention - https://wiki.opensourceecology.org/wiki/Steam_Engine
- and no, sadly mind maps don't allow to place all data I want into node. –
You can, same as json and other markup languages do not have any magic ingredient for your goal but can be use to describe, so as using template approach(manual way, copy paste as an example) may be(depends on your tastes and goal) be a solution there.
And speaking of which, manual approach, idk if you knew but most of internet tech was done trough RFC plain text files, which have loosely defined formatting, so it needs adapting to exiting solution/tools this or another way. And in that sense bunch of text file my be all you need plus some script to show the connection, generate connection diagramm.
Idk, I did simple tech stages diagramms in kde Dia(not the best tool, but simple so passable as a tool for my case back then) which is flowchart drawing tool, for simple cases work well, but I didn't have some special wishes and such, just relationship between blocks on a timeine, and time line was represened by 2d space of that diagram because I decieded/defined it in that way for my self, not because it is a typical use of it.