Re: Typo thread
Posted: 29 Aug 2013, 03:00
An example of what you mean please.Korath said:
(Actually combining effect cards from separate activations is a little harder; keep those separate, please.)
High Quality Resources for Collectible Card Games and Home of the CCGHQ Team
https://www.slightlymagic.net/forum/
https://www.slightlymagic.net/forum/viewtopic.php?f=56&t=11601
An example of what you mean please.Korath said:
(Actually combining effect cards from separate activations is a little harder; keep those separate, please.)
Best to do the changes to both the code and the data in the same commit.Sonic wrote:Would you like the current manalink.xls file to do the entries yourself, so you can bug check the coding at the same time?
Or would you like me to do the data entry?
On the easy list: Make the effect card from Kessig Wolf Run, when activated with , say "Target creature gets +4/+0 and gains trample until end of turn."Aswan jaguar wrote:An example of what you mean please.Korath said:
(Actually combining effect cards from separate activations is a little harder; keep those separate, please.)
We tend to work exclusively on the xls files. Because, as you have previously noted in another thread, converting the csv files back to xls from the semicolon delimited csv format can lead to problems. Although, there is a way to do it successfully in Libre Office Calc – but manually restoring the xls formatting is something of a pain.Korath wrote:Best to do the changes to both the code and the data in the same commit.
Which is the canonical source - the xls or csv? That is, do you generate the xls from the csv, the csv from the xls, or go back and forth between them interchangeably?
Sorry Korath. I'm really not versed in the world of collaborative software development. I'll have to wait until you've got this git, or whatever, up and running and then see if I can get my head round how it works.Korath wrote:What we'll do is put the .xls into git and then treat it like any other source file.
(We'll probably also want to put the .csv files in, too. Usually, you don't want to have anything in version control that can be generated from other files there, but A) we'll want to have something that results in human-readable diffs, and B) only the csvs have been distributed with previous patches, so if we don't, we'll lose the history. I can add a pre-commit script that rejects changes to the .xls file unless the corresponding .csv has been updated too, so they don't get out of sync.)
Only be when the next patch is released.Korath wrote:Just the final one for the upcoming patch. (When it's final, of course.)
What I really meant is that there are original cards that can use one Legacy Card and pump each time compliant with modern rules,using each time a separate activation but ONLY one Legacy card in which the power/toughness gets adjusted accordingly.Look Dragon Engine,Rainbow Knights,...Korath wrote:
What Aswan jaguar asked for earlier was to combine the effect cards from multiple activations into just one orange card instead of a whole column of them, like how Shivan Dragon and Frozen Shade worked under fourth edition rules. " : ThisCreature gets +1/+1 until end of turn" meant you could pay to give it +3/+3 in the same activation; a handful of exe-coded cards still work like that. Under modern rules, it's always three separate activations, and that's how most C-coded cards work.