anothergol

Members
  • Content count

    6
  • Joined

  • Last visited

  1. anothergol

    Easier commissions

    Simple suggestion for easier AND cheaper Rebrickable commissions: you take 10%, so why not just redirect each 10th sale to Rebrickable's own Paypal? First, it makes things simpler as there's no invoices to bother with, second, it doesn't involve a 2-way payment & Paypal taking a commission again. And if someone changes the price of his MOC, or too many months have passed and invoices have to be recomputed, well just feed yourself on the next sales until the remainder has been payed. Still easier IMHO.
  2. anothergol

    Tip Jar/Donations for free instructions?

    Indeed, but consider that the amount that people would tip, they would most likely donate more to Paypal than to you. And I would also suggest a switch to accept all currencies, to reduce a bit what Paypal steals. It's safe to say that half is paid in EUR & the other half in USD, I would prefer to accept both (or define a price in both currencies). I think that when you're as low as 1 or 2 bucks to get instructions, it's more or less a tip system. Only, again, it's mainly Paypal that gets the 1 or 2 bucks. I have no solution to this, though. Is there any cheap micropayment/tipping system out there that'd be suitable? If not, a credit system build-in Rebrickable would be welcome. I would have suggested cryptocurrencies, as *some* (not BTC of course) have very low fees (& there's BAT designed for tipping in browsers), but Rebrickable would have no way to tell when it has been paid (or perhaps there is with BAT, I don't know, anything that's not BTC/ETH is not mainstream yet anyway). Other than that, I'd suggest setting up a Paypal.me, it's very simple to insert as an URL. But beware, no one's gonna donate. I've tried it
  3. anothergol

    "Any color" and easy import from LXF

    Not to dig up my old thread, but am I the only one thinking it's kinda critical, or has this suggestion been made in different words? Or is this what "spare parts" are about? Because it's different: I can imagine 3 extra marks for a part in an inventory, which could be combined: 1) "any color", for all hidden parts. Let's face it, hidden parts are a big part of many MOCs, and it's a bit silly to require the user to buy a part of a specific color, while he may already have the part in another color. Also, it would drastically reduce the amount of shops required to find all of the parts. 2) "any sub-type". This is for those many elements that have mold variations, or similar molds. The most common example being tile+clip. Let's agree that generally the type of clip only matters aesthetically. Looking for shops that have "any tile+clip" would also reduce the amount needed. 3) "any filler". This would be for hidden parts that are just fillers, & for which another part taking the same room would do as well. Granted, this would be much less easy to make work. I'm saying this because in the past, I've color-coded hidden parts in instructions, telling the reader "green parts are any color - just use what you already own", but I then realized from pictures that actual green parts had been bought & used for the assembly.
  4. anothergol

    Light brick not parsed from LXFs

    I don't remember having seen anything related to those 2 parts, but well, cool that it's fixed, thanks.
  5. anothergol

    Light brick not parsed from LXFs

    I just noticed that the light brick, 98782 in trans red, was not added to the inventory of a MOC I just added. I then checked another MOC of mine which also had a light brick, it was not there either. Not a big problem to add it manually, but the importer didn't complain about it at all, so the problem is to be sure that no other part is missing. Shouldn't the importer complain about parts it couldn't interpret from LXF files, to be safe?
  6. anothergol

    "Any color" and easy import from LXF

    I thought that this feature was already there, so I'm sorry if it really is, but I couldn't find it. Basically, in a MOC there are generally hidden parts, for which the color doesn't matter. Is this what the "none" part color already is? If not, could we get a new "any color"? Also, even if that's what "none" already is, I can't imagine myself doing this manually, especially when those parts are merged with those for which the color matters. So I'd suggest the LXF importer to use an uncommon LXF color like "metallic sand blue" (or a user-defined color) to import parts as "any color". That way, say a MOC of 200 parts has 50 totally hidden parts, you just color them differently, and the importer does the rest. That should result in more shops having all the necessary parts.