11-27-2012, 03:25 AM
np 
And yeah, I decided on using skin files instead of hardcoded textures to make it easy for anyone to make simple items and also in preparation that maybe someday somebody might code a feature to allow multiple simple items sets. Seemed logical to me, skin files would make it easy to switch between them while in-game. I'd imagine a cvar like cl_simpleitems_skin and changing the value to different numbers would select the set you want, 0 being xxx.iqm_0.skin (default), setting to 1 would use iqm_1.skin etc. Actually I always wondered if/hoped that engine would allow something else than just numbers as value, that would make it even more easy since people could release their simple item packs and name them what they want, ie: cl_simpleitems_skin "machine" would use xxx.iqm_machine.skin files, causing no incompatibilities between sets using same number. But anyway, that feature (to change item set) doesn't exist, it was just an idea.
And yeah, I decided on using skin files instead of hardcoded textures to make it easy for anyone to make simple items and also in preparation that maybe someday somebody might code a feature to allow multiple simple items sets. Seemed logical to me, skin files would make it easy to switch between them while in-game. I'd imagine a cvar like cl_simpleitems_skin and changing the value to different numbers would select the set you want, 0 being xxx.iqm_0.skin (default), setting to 1 would use iqm_1.skin etc. Actually I always wondered if/hoped that engine would allow something else than just numbers as value, that would make it even more easy since people could release their simple item packs and name them what they want, ie: cl_simpleitems_skin "machine" would use xxx.iqm_machine.skin files, causing no incompatibilities between sets using same number. But anyway, that feature (to change item set) doesn't exist, it was just an idea.