Game-Making/Testing-Cards.md

+To test cards, play with yourself in 2 tabs.
+
+  
+
+Use the special test url:
+
+http://dulst.com/\[gamename\]/play/test/\[myname\]  
+
+  
+
+You can name test games anything you like, for example:
+
+http://dulst.com/\[gamename\]/play/test/test1  
+
+  
+
+You'll want to use a variety of test names as to not conflict with any other testers.
+
+  
+
+  
+
+  
+
+Testing Commands
+----------------
+
+In a test match, there are some special command available to you. Type these commands into the match chat.
+
+  
+
+  
+
+**Add a new card to the match by its name:**
+
+  
+
+/a cards \[cardName\], \[cardName\]  
+
+  
+
+This command adds the specified card to your hand if that location exists in your game.
+
+  
+
+  
+
+**Add a new card to the match by its ID:**
+
+  
+
+/a \[cardID\]  
+
+  
+
+This command adds the specified card to your hand if that location exists in your game. A card's ID is the ID of the card in the url. It is 15903 in the following example: http://dulst.com/\[gamename\]/cards/**15903**/\[cardname\]
+
+  
+
+You can also add multiple cards on the same line:
+
+/a 15903 15904 15905  
+
+  
+
+The event "test add card" is fired on the card.
+
+  
+
+  
+
+**Replace your current deck with a different deck:**
+
+  
+
+/a deck \[deckID\]  
+
+  
+
+  
+
+**Show the game log:**
+
+  
+
+In testing sometimes you want to see what's actually happening behind the scenes.
+
+  
+
+The game log shows which effects are running throughout the entire game.:
+
+  
+
+Go into your browser devtools console (press F12 on your keyboard and click on the console tab) and run:
+
+dulst.logs()  
+
+  
+
+Every action in the game will be printed out in logs. This lets you trace what's happening in the game step by step and see what worked and what didn't.
+
+  
+
+  
+
+**Show all the properties on the game.**
+
+  
+
+In devtools console:
+
+dulst.view()  
+
+  
+
+  
+
+**Show all the properties of a player.**
+
+  
+
+In devtools console:
+
+dulst.view('player1')  
+dulst.view('player2')  
+
+  
+
+  
+
+**Show all the properties of a card.**
+
+  
+
+In devtools console:
+
+dulst.view(\[ciid\])  
+
+  
+
+Cards are identified in-game by the ciid or Card Instance ID. This is the unique ID for each card. Rule cards also have ciids. This is different from the card id of each card in the url. Multiple copies of the same card in game share the same card ID, also known in the debugger as "nid". Each copy has its individual "ciid". During testing the ciid is typically displayed as the number in brackets before the card name.
+
+  
+
+  
+
+**Stop the card preview from disappearing and making it clickable:**
+
+  
+
+/a keepOpen  
+
+  
+
+  
+
+**Theme the look of the play area via CSS:**
+
+  
+
+/a editCSS  
+
+CSS changes hot-reload while edited from this view.
+
+  
+
+  
+
+  
+
+Differences between test modes and regular play
+-----------------------------------------------
+
+  
+
+*   In test mode you can right click in to bring up the brower's functions. In regular play the right click is controlled by the game rules.
+*   In test mode you can run test commands, you cannot do so in regular games.
+*   In test mode the first turn's player will always be player1. In regular games it is random.
+*   In the Animal Kingdom template game, the test mode starts off with 100 mana to help facilitate testing. In regular games players start with 1 mana.
+
+  
+
+  
+
+Single Tab Testing
+------------------
+
+If you want to test in a single tab use the dev url.
+
+http://dulst.com/\[gamename\]/play/dev/\[myname\]  
+
+or
+
+http://dulst.com/\[gamename\]/play/dev/\[mygamemode\]  
+
+  
+
+This lets you test the game faster but is suitable only for testing scenarios that can be tested on the first turn or vs AI.
+
+  
+
+  
+
+Video Demo
+----------
+
+  
+
+https://www.youtube.com/watch?v=tMjcAnfjrj8
\ No newline at end of file