Hey all. I have a couple of kitbashes I'm cleaning up for submission, and any kitbashes that have tiles, I'm making TLX planner files for. However, there are a bunch of details that don't work all that great:

1) Each entry in the model sets has a "buy now" link. That's cool, but the submission doesn't know where to go. Should they point to the kitbash area? What I've been doing is just pointing "buy now" to the set the kitbash is most based on, assuming that the bash will be available from that page. Perhaps the kitbash approver could repackage the bash with a better link when it's finally pushed to the store?

2) Each entry that I've made tends to be named after some set. For example, "Hinterland Forests - Shoreline". That title doesn't fit well at all in the planner, and the differentiating bit is the part that tends to get cut off. I wonder if we could have some mechanism for the following:

2a) Note in the manifest that this is a kitbash related to other sets.
2b) Separate the .tlx files of kitbashes from full-fledged model sets. The import feature could move the .tlx file into the right place if it contains a manifest that indicates it is a kitbash or not.
2c) Kitbash tlx files would display their bits as sub-items of the model sets they relate to, perhaps with some special chrome around the item to denote that it's part of a kitbash.

Basically, I wanted to get some better integration from the TLX planner and kitbashes. My listing of "model sets" is getting to be an unwieldy mess with different packs of streets tiles, forest tiles, garden tiles etc.

1. I would put a link to the major product...

2. It's a good idea. I'll have to see what can be done about that, but my time runs really short for the moment, so I don't know when such a feature could be added...

That's the best answer, since that's what I've done


At least I've planted the seed, and now you will be tormented with thoughts of how to get it implemented in your copious free time!

I agree with linking to the main product.

Also,

rofl

Mproteau you are a mean mean dude!!!

If/When I get to this, it should be great if we don't have to redo all kitbash planner files.

So I propose the following, for those who want to create bah planer files :
in the first line of a tileset manifest file, use the following format :
KB_<original set id>_<kitbash unique id>=<kitbash name>

For example, for a kitbash about hinterland shoreline:
KB_Himmelveil Forests_Hinterland Shoreline=Hinterland Shoreline

That way, the planner could be able to determine which sets are kitbashes, and from which set they derive.

OK, so you got me...



That's what it could look like in the planner...
I used a different color arrow to distinguish bashes, and also because it was *very* difficult to shift bash title to the right

I tell you what - it's going to be light-years ahead of potentially having dozens of top-level items with super long names that all get cut off. Plus, not having to have the huge image and stuff with each kitbash is great. Saves time making the bash tlx file, and saves space in the panel.

Another thing to consider - a kitbash may be associated with multiple sets. While I tend to enumerate all of the sets involved, does it make sense to pick *one* set to associate it with in the planner? I think it'd be OK, but I thought I'd bring it up for consideration.

The way I implemented it, a bash will be associated with one product, no more. So you should choose the main product to rattach to.
Note that the tlx file should be a valid tlx file : it will be compatible with older planners (ie planner not including the kitbash possibility) : so it means having a set thumbnail, etc.