Board Thread:General Discussion/@comment-26692787-20151030123440/@comment-15636815-20151030205905

TrashTerrier wrote: I leave out such options on "my" wiki, when ppl check the items they'll see how to get them anyway ;)

And it makes the contract list look messy, but that's just my opinion Johann is a very clear example. Of his 35 contracts, 11 (almost one-third!) have objectives with a gems-only option. Most of the time, users quickly check the contract list to see the requirements for the next one or two contracts. If one of the options for a contract is gems-only, then you're right: Clicking through to the article page for the locomotive or wagon would give the user that information. Seeing next to the item in the contract list saves the user from needing to load the article page.

In other words, a contract objective that displays makes the contract list far more informative, which ultimately makes the wiki far more useful.

On the other hand, as you stated, it also makes the contract list a bit messy, which makes it more difficult to read. That means we, as a community, must decide whether "quick" or "easier to read" is more important to us. That's something we've never discussed in the two years I've been here. The users and editors before me added them, and our community has kept them.

Should we continue to keep them to deliver information more quickly? Or, as TrashTerrier says, do they make the contract list messy, and therefore difficult to read, when the desired information is only one click away, anyway?