Inclusion of card data files

[Rob Cashwalker]

Now that we're primarily hosting the release packages on Google, I was wondering if we should move towards reducing the amount of Magic-specific game data that we release with it. The code will almost certainly always have card names and game-specific terms in it. External files on the other hand, can be distributed outside of the main package, reducing the package size ever so slightly...

Once the card files contain the Oracle text, they would be just as objectionable as the card images. The card files can be hosted at cardforge.org as a separate download, either as a package, or through an in-game update.

I have some work sitting on the side based on reading card and creature type lists from a file into elements in Constants.java. This will be in a specific resource folder, "/res/gamedata/".

Thoughts?

[Sloth]

Once the card files contain the Oracle text, they would be just as objectionable as the card images. The card files can be hosted at cardforge.org as a separate download, either as a package, or through an in-game update.

In-game update is not so easy, since new cards shouldn't be downloadable by incompatible old betas.

[Rob Cashwalker]

But new cardfiles don't need to be uploaded to the server immediately either, unless they don't require new functions...

[Sloth]

But new cardfiles don't need to be uploaded to the server immediately either, unless they don't require new functions...

Yes, there are several solutions to this. It's just something to be aware of.

I have some work sitting on the side based on reading card and creature type lists from a file into elements in Constants.java. This will be in a specific resource folder, "/res/gamedata/".

This would enable making cards like Conspiracy more user friendly.

[Rob Cashwalker]

Files changed since the previous release go into a unique folder (using build number) of the website. The download client would be able to retrieve the build number of whatever version is running, then download files only in the proper folder.

[Sloth]

Files changed since the previous release go into a unique folder (using build number) of the website. The download client would be able to retrieve the build number of whatever version is running, then download files only in the proper folder.

Sounds good. Relieving the SVN of the cardsfolder seems to be a good idea now that every commit leads to a (harmless) error. And it can't be bad to further disassociate from copyrighted material.

[Chris H.]

Hmm, we have another issue to consider. I think that we would need to keep the working card.txt files located on the SVN. Dave's Maven script would have to be modified to not include these card.txt file ... it may just be a simple edit to the script.

[Rob Cashwalker]

The cards do need to stay in the SVN...

The subfolders of cardsfolder didn't come up until after I had posted this... I'm sure it can be worked around.

[Braids]

i rather like the idea of separating the card files out, as it could be another way to ease the burden of making a working copy primarily to edit source code.

i know my current efforts are hampering this. i'd rather be part of the solution than the problem. i'll be watching this thread from now on.