Template:TOC right
(most recent first)
Applies only to texture mods. Propose that we include Section as a Mod Attribute to indicate the STEP Section to which a mod will belong if added. Only Section G will apply to the DDSopt Property set.
If IsOptimized is not true, then the following could also apply:
Added reference to new Form:Mod Version and Template:Mod Version Stoppingby4now (talk) 19:51, October 16, 2012 (UTC)
I think in some cases you are trying to force data into Semantic Properties when there is no need to. Particularly when you start trying to associate large amounts of data, Semantic Properties are just not efficient enough. There is a lot we can still accomplish with typical Wiki structure. Mod Updates is a perfect example of tying information together without needing to use Symantic Properties on a grand scale (Update date is being used, but only for the purpose of determining the latest update). In other words, don't think of this exercise as creating an application (I was stuck in that mindset in the beginning myself), as the application is already written (MediaWiki). We are just extending it in order to store data in a different way where it makes sense. Stoppingby4now (talk) 21:13, 11 October 2012 (UTC)
- Please define "sub-headings" as you reference them in the intro. - Also confused about contexts of "new data structure" and "second-level heading".
Would you care to clarify or elaborate? ~z929669Talk 04:41, October 17, 2012 (UTC)
{{{for template:ModList|multiple}}}
{{ParentTemplate |parentfield={{ChildTemplate |childfield1=some data}}{{ChildTemplate |childfield1=some other data}} }}
Assuming that mod testers will have a detailed guide as to how to set up their base system to prepare for mod testing (SIS should be specifically employed so that testers can save their current profiles and set up two additional profiles from scratch as we define then. This should be a strict protocol and prerequisite to begin official testing for STEP.