Community DLC - Proposed reservations for 'multi-sources'

[Yanna]

Hi all,

Since many modders are now building custom contents, I was thinking of a 'reserved' DLC that would hold multi-sources releases (a bit like what Uresti prepared). This would eliminate conflicts beetween cards/decks/illustrations and provide a 'standard' base for custom contents to be added.

All IDs, naming and so on would be 'fixed and reserved' and thus modders should avoid using those in non-community content.

Here's my suggestions (feel free to make others !):
- Data_DLC_1111 is the name of the reserved DLC. (I would be suprised if stainless ever realease more than 100 DLCs.)
- XXXX is a code attributed to every modder (say for example Uresti's is 9999 and mine is 7777).
- Reserved picture IDs : XXXXYYYY XXXX is the modder's code again and YYYY is the card ArtID in that modder's realease.
- Decks DATASET to build up a proper 'DATASET' file, every modder code would appear in a 'community' dataset.

For example :

<DATASETS>
<DATASET_DEFINITION name="COMMUNITY">
<DATASET_INCLUSION name="Land"/>
<TEXT filename ="7777_card_text"/>
<TEXT filename ="9999_card_text"/>
<TEXT filename ="10e_card_text"/>
<TEXT filename ="EVE_card_text"/>
<TEXT filename ="SHM_card_text"/>
<TEXT filename ="LRW_card_text"/>
<TEXT filename ="MOR_card_text"/>
<TEXT filename ="Earlier_card_text"/>
</DATASET_DEFINITION>
</DATASETS>

What do you think of it ?

YannA a.k.a NOVA

[kevlahnota]

I agree. So that we can easily track every card / sets we have.

[pun1sher666]

I agree with it, it's a good idea to avoid conflict
My code is 6666.
I will update my release with 3 new decks and i will include your suggestion...

[Uresti]

then the big dlc will have what number please'?

[Yanna]

- Data_DLC_1111 is the name of the reserved DLC. (I would be suprised if stainless ever realease more than 100 DLCs.)

It would contain the up to date 'DATASET' and decks could be put there.

DLC could still be released separately by the community, and updated as well. Just that it will be easier to mix cards beetween modders whithout conflicts.

[Huggybaby]

Hi all,

Since many modders are now building custom contents, I was thinking of a 'reserved' DLC that would hold multi-sources releases (a bit like what Uresti prepared). This would eliminate conflicts beetween cards/decks/illustrations and provide a 'standard' base for custom contents to be added.

All IDs, naming and so on would be 'fixed and reserved' and thus modders should avoid using those in non-community content.

Here's my suggestions (feel free to make others !):
- Data_DLC_1111 is the name of the reserved DLC. (I would be suprised if stainless ever realease more than 100 DLCs.)
- XXXX is a code attributed to every modder (say for example Uresti's is 9999 and mine is 7777).
- Reserved picture IDs : XXXXYYYY XXXX is the modder's code again and YYYY is the card ArtID in that modder's realease.
- Decks DATASET to build up a proper 'DATASET' file, every modder code would appear in a 'community' dataset.

For example :

<DATASETS>
<DATASET_DEFINITION name="COMMUNITY">
<DATASET_INCLUSION name="Land"/>
<TEXT filename ="7777_card_text"/>
<TEXT filename ="9999_card_text"/>
<TEXT filename ="10e_card_text"/>
<TEXT filename ="EVE_card_text"/>
<TEXT filename ="SHM_card_text"/>
<TEXT filename ="LRW_card_text"/>
<TEXT filename ="MOR_card_text"/>
<TEXT filename ="Earlier_card_text"/>
</DATASET_DEFINITION>
</DATASETS>

What do you think of it ?

YannA a.k.a NOVA

This of course is an excellent idea. The guys in the manalink forum have a similar system.

Please allocate any codes you think necessary (leaving as many as possible open for future members and other needs) and document the codes in the wiki.

And may I say again that the wiki looks great?

Thanks,

HB

[Uresti]

Im not agaist community releases thats why this forums exist i just was asking for a number to release a DLC with all the current work so other people just "install" that and start playing right away because i think not all likes to have multiple files.

[Yanna]

Im not agaist community releases thats why this forums exist i just was asking for a number to release a DLC with all the current work so other people just "install" that and start playing right away because i think not all likes to have multiple files.

I understand what you mean, and it's true a single file is better rather than multiple ones.

The problem with a single file is that every updated release of someone needs to be added to the 'all-in-one' DLC. And that's certainly a lot of work.

[pun1sher666]

I'm working to a multi-source managment with a source hosting via SVN on Google Code.
I already created the repository, and i'm currently doing a merging between Yanna's DLC and mine.
I will try to merge all DLC to have a unique database of cards, so that ppl won't code the same cards.
I'll keep you all updated when i'm done.
To give you an overview on how it will work, after checkout of the repository you will be able to commit your change quickly so that all the community can update the DLC. If some conflicts are detected, merging tools are avaible.

[whismer]

Great idead...if I understand well

we will work on a virtual DLC on the svn and we can add card each day one by one to this SVN so you are up to date to wich card are created until now

Cool i will upload my 20 cards and continue my progress and it will be better for making deck with the editor when you don't have to load 4-5 different DLC

Some suggestion :

Maybe we can start using the ID of the card on the Gatherer for the picture so it will be more easier to work with all the amount of card image...

Have someone try to put the flavour line and etc... in the card .xml directly?

[pun1sher666]

The repository is now operational on Google Code.
I merged Yanna's DLC and mine to create a unique DLC : DATA_DLC_1111.
I can integrate others DLC if you post you'ra last updates.
I use Yanna's code formatting to have something readable and clean in the XML's.
Everyone keeps them own code as the extension name and the label file associated.
I will give you all the informations to access the repository when everything will be merged.

Best regards,

Pun1sher.

[Yanna]

Confirmed, this works perfectly !

Multiple users can add/modify content of the 'DATA_DLC_1111' repository. Of course you need to be authenticated and allowed to do this (otherwise it's read-only).

[whismer]

What's the URL ?? I will upload my cards directly in the SVN ...

Thx

Whismer!

[pun1sher666]

Whismer, you can post your DLC on the Release part. I need to do an integration in the main DLC before. Yanna will post on the wiki everything for you to use the repository.

[Yanna]

Wiki updated !

I've written a short guide on how to Setup Tortoise SVN on your computer to get live updates from the DATA_DLC_1111 Sources :

http://www.slightlymagic.net/wiki/COMMUNITY_DLC_Tutorial_-_Setup_Tortoise_SVN

Soon will come another short tutorial explaining how to add/modify content.