Some model paths still need some organizing

[Fidcal]

Just looking for a button. There is still only one surprisingly - the numberwheel button - but this is under mechanical whereas there is a separate folder mechanical/switches. This whole folder wants reorganizing really but I guess that will break maps. I would always have a misc subfolder otherwise there is a mix of folders and models whereas in Windows we're used to folders being listed together. So we might have something neat like...

 

chains

gauges

gears

misc

.. L watermill

pipes

switches

.. L buttons

.. L levers

 

I don't mind doing the work but I don't want to break anybody's map without agreement.

[Springheel]

If we're just talking about the mechanical folder, that's probably ok...I get a sinking feeling in my stomach when I think of any more than that. (btw, currently chains are placed in dungeon)

[greebo]

We still have sparhawk's model script around (written in Python, iirc), which could be used to traverse the map and def files to replace model occurrences. I think last time we missed the skin files, so we'd have to improve that script a bit.

[Fidcal]

If we're just talking about the mechanical folder, that's probably ok...I get a sinking feeling in my stomach when I think of any more than that. (btw, currently chains are placed in dungeon)

Well there are chains in both dungeon and some other chains under mechanical. I think there are also some chains in Doom resources. This is why I tried one or two dummy models with names as links, eg, forMoreChainsSee.. etc. Is there any way to have some kind of text file that DR could read to display in the model selector? It can only get worse as different people put similar things in different folders. If each main folder had something like 'NOTES' so if you look under mechanical for a chain but can't find the one you want then look in NOTES and see, 'see also dungeon and doom' or something.

[greebo]

Is there any way to have some kind of text file that DR could read to display in the model selector? It can only get worse as different people put similar things in different folders. If each main folder had something like 'NOTES' so if you look under mechanical for a chain but can't find the one you want then look in NOTES and see, 'see also dungeon and doom' or something.

This is possible. The ModelSelector could be set up to read the NOTES.txt from the currently highlighted folder.

[Tels]

We still have sparhawk's model script around (written in Python, iirc), which could be used to traverse the map and def files to replace model occurrences. I think last time we missed the skin files, so we'd have to improve that script a bit.

 

The scripts I developed for packaging can do the same easily. Just give me the list of "old name" "new name" and I fix the maps.

[Springheel]

Well there are chains in both dungeon and some other chains under mechanical.

 

There shouldn't be. We'll need fewer readme files if we're consistent.