Board Thread:Questions and Answers/@comment-80.187.103.142-20150309120420/@comment-26185947-20150311121906

OK. Let's see what's the idea of a table.
 * 1) I'm searching for a specific item/train.
 * 2) How does it look (Image needed).
 * 3) What does it cost.
 * 4) Can I buy it (Lvl).
 * 5) When does it show up (date).

Let's say im collecting gems and I have enough to buy a SO i saw 2 month ago. Hmm… what's his name again? I need the image to find it, that's essentially. But what I don't need is e.g. the, here, needless info about Buy-XP, Tax, Ratio (good für buildings, but what does it tell me for the train?) and Dispatch-XP. 'cause I'm not buying trains after that infos. If I wanna know it, I look under the train-set.

So if the width of the tables are restricted to a specific size, delete needless info columns, but don't forget the important once. I have no problem with scrolling down a loooong table, as long as I can find what I'm looking for. If I can't find it, the whole table/page use useless.

A good info, which is missing at the train set-infobox, would be, how much gold I gonna make with a Pass-train-set with one neighbor. But that would be a lot of work ;-)

Hope it helps for further decisions. :-)