That’s because nanDECK uses centimeters, not inches. I know what you’re thinking: those numbers look odd. nanDECK will use this to lay out our cards. Next, we want to define the size of each card. In this case, we assume that we’re storing the CSV in the same folder as our nanDECK NDE file: link=fog-actions-update20140719.csv We also tell nanDECK where to find that spreadsheet. Next, we tell nanDECK that the “Count” field in our spreadsheet represents the number of copies of each card: linkmulti=Count Multiple card formats probably should be stored in separate layouts and spreadsheets.) =1. The line below might be best read as “ represents a set of cards starting at 1 and ending with the last row that has a Title value.” (I’ve never found a reason not to do this. (Again, if your layout is getting that complex, you’re probably out of the prototyping stage anyway.)įirst, we’ll set up a variable called, which will represent all cards in the set. Order is sometimes important, and you can create conditional blocks, but there’s typically not the sort of “flow control” you think of when programming. Every line starts with a directive (the text on the left side of the equals sign) that is passed a number of values (the list, separated by commas, on the right side of the equals sign). nde file here (you’ll need to provide your own CSV file with Title, Description, and Count columns.)īuilding a template in nanDECK is somewhere between creating a configuration file, programming, and writing HTML. If you want to follow along, you can download the. Note that every directive from this section is explained in the nanDECK manual. Now, let’s take a look at the configuration I’m using for this deck. To do this, go to Save As… and select either “Comma separated values” or “CSV.” Don’t worry too much about options, as the defaults will work for most scenarios–just make sure that the delimiter is CSV. Once we’ve got a spreadsheet set up in Excel or OpenOffice, we need it in a text format that nanDECK can read. etc.” on every card? Applying the label “Item” would be far simpler, and then refer the player to the rulebook. And if I’m introducing multiple keywords, then maybe that needs to be its own column in my CSV, rather than a bold term that appears in the Description.įor example, my Action deck has a few cards that players can keep for semi-permanent effects, so why write out “players can keep this, can only have one copy, etc. Of course, there’s the game design equivalent of a “code smell” here–if I’m regularly using the same mechanics over and over, then I probably need to introduce some keywords. “Description” belies some complexity: I want to be able to include line breaks and, if possible, formatted text. In fact, that’s all that’s really in my spreadsheet: Title, Description, and Count (for the number of copies of each card in the deck). Note that I’ve also got a calculated field in my spreadsheet showing the total number of cards in the deck–in this case, 86. In my last post, I mentioned that Player Actions were simple title-and-description cards. Now, let’s get into the nuts and bolts of building a template. In part 1, I covered why you might want to use nanDECK in prototyping a card game.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |