309
edits
Changes
no edit summary
Yep, until there is no links, I think it will be okay. However not sure about mentioning other proprietary software on the page, so I would still leave out Toolbox section ;) [[User:50keda|50keda]] ([[User talk:50keda|talk]])50keda
Sounds reasonable. I ''think'' this latest revision should meet your recommendations. My eventual goal regarding the list of mods is to highlight some unique features/advanced techniques used in each and link within the wiki to tutorials and documentation to guide the user towards producing similar results. I figure if I set the example, maybe someone with ''actual'' talent might do the same. ¯\_(ツ)_/¯ [[User:Smarty|Smarty]] ([[User talk:Smarty|talk]])
== Units pages ==
## Ok, I'll work on setting up the moves after breakfast. [[User:Smarty|Smarty]] ([[User talk:Smarty|talk]])
## I [[Documentation/Engine/Units/Accessory_data_(%22accessory_data%22)|tried one]] but it looks like there is no way to preserve the underscore (_) in the title. I think it might be better to omit the part in parentheses entirely. The class name with underscores is included, bolded, in the first sentence of each article already (a deliberate convention) so including it in the page title seems redundant. Let me know what you think. [[User:Smarty|Smarty]] ([[User talk:Smarty|talk]])
== Shader documentation ==
=== Structure ===
I'm thinking of using [[Documentation/Engine/Shaders]] as a general hub for the technical documentation (see [[Documentation/Engine/Units|Units]] and [[Documentation/Engine/Units/accessory_data|Units/Accessory_data]] for an idea of the general organizing structure I'm thinking of), splitting off into something like [[Documentation/Engine/Shaders/Eut2/Dif_spec]] for each general effect family, following the folder structure of <code>//effect/...</code>, and then additionally having [[Documentation/Engine/Shaders/Eut2/Flavors]] as a sub-hub for flavours. Thoughts? [[User:Smarty|Smarty]] ([[User talk:Smarty|talk]]) 01:42, 21 September 2016 (CEST)