leafan

TLG acquires Bricklink

Recommended Posts

16 minutes ago, Pdaitabird said:

@vermontcathy Just change the set number for your flower tree build to 25. That way only people who understand binary will get it! :wink:

Ha. Yeah, that'll work for THAT set...

But seriously, I'm not even sure it's the set number that causes the flag because I have other models with set numbers that didn't get flagged. At this point, I was about to say that I think all models are being flagged for some reason (a bug, a mistake). But I uploaded a "model" of a single brick, no set names, numbers, Lego lines, etc. and just now I see it was not flagged: https://www.bricklink.com/v3/studio/design.page?idModel=126070

And although earlier today, it seemed like all recent uploads were set as Display Only (flagged), some recent ones now allow you to download the Studio file. 

Maybe the rule (among others) is that you can't have a set number in the name, and the bots just haven't yet got to my unflagged models? I'll try uploading the tree flower again with no set number and see what happens. But I refuse to remove the set number from the names - that's how I sort my models so I can find a what I'm looking for.

Share this post


Link to post
Share on other sites
1 hour ago, vermontcathy said:

Maybe the rule (among others) is that you can't have a set number in the name, and the bots just haven't yet got to my unflagged models?

 

1 hour ago, Pdaitabird said:

Just change the set number for your flower tree build to 25.

Well, if that number issue proves to be true: The binary to decimal conversion @Pdaitabird suggested is very clever but may have serious restrictions.

The hexadecimal notation used in VB6(:innocent2:) may work though, where you put the "&H" first and the hexadecimal number. VB6 development came to an end 20 years ago - I firmly believe that no TLG bot catches "&H2AF9" as set number "11001". "&H" is totally weird by itself ... and you can use the native Win10 calculator to easily convert the remaining hex numbers.

That way you'd make the TLG bots look dumb AND you can still use the number to find your sets ...

Just kidding. I liked the 25 very much.

Best
Thorsten 

Share this post


Link to post
Share on other sites

Hexadecimals may be enough differentiation to that someone not well versed in the ways of bricks wouldn't confuse it with a real TLG product.  :pir_laugh2:

 

Share this post


Link to post
Share on other sites

Do you know how many people were downloading instructions/ designs before the change? For licensed MOCs of popular subjects I imagine it is quite high. For alternate builds of smaller sets I imagine less so.

Share this post


Link to post
Share on other sites
5 hours ago, MAB said:

Do you know how many people were downloading instructions/ designs before the change? For licensed MOCs of popular subjects I imagine it is quite high. For alternate builds of smaller sets I imagine less so.

Surprisingly, they were downloaded a decent amount. I say surprising, because I use it for the online 3D steps. But when it's someone else's model, and they may remove it at any time, I guess downloading the Studio file is safest. As an example, this silly little tiger, posted for just over a year, has been downloaded 117 times. This elephant, up for less than a year, 126 times. 

The hexadecimal thing is cute, kind of a secret code, but that's the problem - it's secret. If I want people to know that it's an alt of a certain set, how do I tell them which set? I've got one that hasn't been flagged (yet) that doesn't have the set number in the name/title but does have it in the description. But I want it in the name, for sorting purposes. 

I've got one model re-submitted with the set number listed as 1.1.0.0.1. We'll see if that gets flagged or accepted. 

Share this post


Link to post
Share on other sites

I stumbled upon the Lego AMA. Haven't found any info about it here.

Quote
9. Is the LEGO Group planning to enforce an element availability that strictly matches S@H? If so, does this not really limit AFOL creativity?
To clarify, we are not placing such a restriction on brick availability on the site. Sellers can continue to sell LEGO elements (e.g. old/retired) that are not currently in production.

Do I get the last sentence wrong? Sellers will not be allowed to sell Lego elements, which are currently produced by TLG?

Share this post


Link to post
Share on other sites

You got it wrong. 

Quote

(snip) we are not placing such a restriction on brick availability (snip)

 

Share this post


Link to post
Share on other sites
Just now, LegoFjotten said:

You got it wrong. 

 

But still... the last sentence... "Sellers can continue to sell LEGO elements (e.g. old/retired) that are not currently in production."

Share this post


Link to post
Share on other sites
Just now, Andman said:

But still... the last sentence... "Sellers can continue to sell LEGO elements (e.g. old/retired) that are not currently in production."

Your are looking too much at the answer, and not enough at what the question being answered was. :classic:

My simplified version of the question & answer:

Q: "Will you only allow sellers to sell elements that are currently in production?"

A: "No, sellers can continue to sell old/retired elements".

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.