News:

A forum for users of LackeyCCG

Main Menu

Background not loading

Started by dmenard, April 10, 2020, 04:56:59 PM

Previous topic - Next topic

CrazyChucky

Yay, progress!

I'm stumped as to why it would work for your text files, but not your images. You're sure they're in plugins/NFL-Gametime/sets/setimages/general/ ? If you want to attach a zip file of your whole plugin folder, I could take a look and see if I notice something.

You have three (sort of two-and-a-half) options for telling Lackey where to download your plugin files.

  • CardImageURLs
    With this option, yes, you have to list each individual image URL separately in your updatelist. As you'd imagine, this is... a lot.

  • CardURLFiles
    You still have to list each individual image URL, but you can put them in one or more separate files, and list those files in your updatelist. Note that these URL files have to be listed among the checksummed plugin files (so Lackey knows to download them) and in a "CardURLFiles:" section, so that Lackey knows to use them to find card images. This method, at least, keeps you from having an enormous updatelist.

  • CardGeneralURLs
    This is by far the simplest method if you can use it, but I don't know that it can play nicely with Google Drive. You define a base URL, something like "http://mywebsite.com/pluginimages/", and then whenever Lackey needs a card's image, it will combine that with the card's listed imageFile (adding ".jpg" automatically if no extension is specified).

    For instance, if a card says its imageFile is "card001", Lackey will attempt to download "http://mywebsite.com/pluginimages/card001.jpg".

As far as I know, you can't use the last method with Google Drive. Even if you set your CardGeneralURL as "https://drive.google.com/uc?export=download&id=", and you set each card's imageFile to the long string of characters that represent its ID, Lackey would still attach ".jpg" to the end and it wouldn't work. (And even if it did, it would still be just as much copying and pasting as using either of the first two methods.)

Have you looked into other file-hosting locations? Perhaps Github? It's possible they might check content and get upset about hosting copyrighted images... but they do let you access your files with actual URLs that aren't made of alphabet soup.

dmenard

I uploaded all of my images to dropbox. I have attached my update list file. I have not added in the stuff for dropbox yet. Let me know if you see where I went wrong.

dmenard

Sorry missed the first part of your last post. All under set images I have 4 folders they are, general, base, 19, 20. I believe they are in the proper location unless I missed something with how they are ordered.

CrazyChucky

#18
Ah, I see the issue now. The plugin tutorial mentions: "Before a proper checksum is generated, just include any number as a placeholder checksum." Just stick a zero (or something) at the end of each line (after a tab):

plugins/NFL-Gametime/plugininfo.txt https://drive.google.com/uc?export=download&id=1QYi6bonq5zgBtze4q4x4jdkejJheAHE- 0
plugins/NFL-Gametime/pluginpreferences.txt https://drive.google.com/uc?export=download&id=1gkDAiNTEivXVwh02ryt8KbUS3DYKPG8q 0
plugins/NFL-Gametime/sets/carddata.txt https://drive.google.com/uc?export=download&id=1JopDJfx9efQNSnITdVuL4MrS2UXTl4mY 0
plugins/NFL-Gametime/sets/setimages/general/cardback.jpg https://drive.google.com/uc?export=download&id=1aCkH7ARuuutsAlAjPQZfxnMdpU3_rFx7 0
plugins/NFL-Gametime/sets/setimages/general/spawned.jpg https://drive.google.com/uc?export=download&id=1_wzAag3Rg5i_LJ_RNH7DWzMJi3H523gd 0


(If you notice, the messages Lackey prints when you run the checksum command on your current file indicate that it's jumping ahead to the next line too early in search of that final column. It thinks, for instance, that 'plugins/NFL-Gametime/pluginpreferences.txt' is the checksum for your plugininfo.txt. Then it says it can't find a local file named 'https://drive.google.com/uc?export=download&id=1gkDAiNTEivXVwh02ryt8KbUS3DYKPG8q'.)

Does DropBox give you predictable URLs for file access? If so, that's good to know about. I haven't tried it out.