Hey - as usual I'm leaving a comment on your newest node - thanks for all these new textures!
The nitpick is just with your CFGs.
Since I know so few packages are done well (guess why I wrote the packaging guide) I usually unpack to a safe place first,
but the idea is that people should just unpack into their personal data-directory (like ~/.sauerbraten on linux) - to emphasize this - not the game installation folder, but the personal one .. at there they couldn't mess things up completely.
Well, you've packaged it alright, but still - if I've got the previous woodtex packages already this one will overwrite the package.cfg/package-nospec.cfg files .. effectively disabling all the other textures.
You have two possible approaches:
- either have specific pack_01 .. pack_99 CFGs for all the bits and have the user call them specifically from his map-CFG
- or, if you know in advance how-many/which textures you'll publish, have the package.cfg be the same in every one
The last solution definitely expects the user to either really have all available packs in place or he has to edit the package.cfg to fit his situation. I'd go for the 2nd one actually - easier to manage on all sides, you could even have a package.cfg that loads the different sub-pack-CFGs in sequence though - a little nicety for the extremely lazy but download-hungry :-)
What you really need to fix in the CFG is the following:
- don't do a texturereset!
- don't run default_map_settings!
- if you've put in some call to "setshader ..." then you should end your texture-listing with a line reading "setshader stdworld" or else other peoples textures will turn up with unexpected shaders applied!
You still get 5/5 though .. since your work is really the graphics, the config stuff should still be fixed though!
