Author Topic: A .bls file brown townyzer that finds bricks that aren't default  (Read 540 times)

I'm sure everyone's had the problem of making a save years ago and not being able to pinpoint what custom bricks it actually uses, making you say that it requires stuff that it really doesn't. What I suggest is a decent way to detect non standard bricks, according to their names in a .bls file, and then spit out what brickpacks they actually are from a database... This could probably work as a website, and could also probably work as some kind of program or even an add-on, though a website would be preferable.

Perhaps this could function as an extension to a save file upload site, too, so that people know which addons a save file requires, but that's another suggestion.


what brickpacks they actually are

Where do you want to get this from? There are hundreds of brick packs and noone has a database of their contents. Plus many brick packs actually have the same names for different bricks.

RTB had something like this (it would report all brick packs found on rtb), but it was only possible because they managed all add-ons and could prevent people from uploading packs with duplicate names.


You can probably create such a database from an rtb archive, but it won't contain newer brick packs... so it will never be perfect.
« Last Edit: November 18, 2015, 01:50:10 AM by Zeblote »

It exists sort of - Client_BrickDatabase. It tries to manage a user-submitted database to find required packs for a save.