1,894
edits
Changes
Jump to navigation
Jump to search
no edit summary
:::: Aesthetically I like what you did very much. However, and speaking of redundancy, doesn't it seem redundant to list a skill twice in a row when talking about improving? Is there a way we can indicate that making an item relies on a skill as well as the tools that belong to that skill set to improve? I do worry that the method section may have been tightened up too much. While it was kind of bloated, there was a use. When confronted with the act of using an iron lump on a large anvil there may be two dozen choices in 4 menus available. For clarity's sake, I think it would be nice to somehow concisely indicate the path down that tree. Again, the old way was a bit bulky and not at all concise. I'm hoping we can come up with something new. --[[User:Hephaestus|Hephaestus]] 16:59, 27 August 2007 (CDT)
::::: That's what discussion is for. I agree that having the skill listed twice seems redundant, I did it that way to allow for exceptions. However, it's also possible to hide that entire section unless there is an exception. Adding the create category is also just a matter of including new parameters. We could do "Select Create / {{{group}}} / {{{name}}}" or "Select Create / {{{create}}}" or some other variation. Which would you prefer? - [[User:Dashiva|Dashiva]] 17:14, 27 August 2007 (CDT)
