Add ability to collect resources

.github/PULL_REQUEST_TEMPLATE/add_a_player_animation.md

@@ -0,0 +1,13 @@
+## How to add a new player animation
+
+Roughly...
+
+- [ ] procuring animations (find on asset store)
+- [ ] update mecanim state machine
+- [ ] create new StateBehaviour and add to Player
+- [ ] update player state machine
+- [ ] update resource config
+- [ ] make a new PlayerState enum
+- [ ] assign to resource config
+- [ ] update player animator's list of animation enums
+- [ ] update player tool script to add tool

.github/PULL_REQUEST_TEMPLATE/add_juice_with_feel_framework.md

@@ -0,0 +1 @@
+...

.github/pull_request_template.md → .github/PULL_REQUEST_TEMPLATE/implement_a_user_story.md

@@ -1,6 +1,9 @@
-## Job Story
+## The Job Story
 
-> **Player**: When <code>X</code>, I want to <code>Y</code>, so that <code>Z</code>.
+<details>
+<summary>
+<strong>Player</strong>: When <code>X</code>, I want to <code>Y</code>, so that <code>Z</code>.
+</summary>
 
 ### Notion
 
@@ -10,11 +13,24 @@
 
 > *(link goes here)*
 
+### Deliberate Practice
+
+> Write down one skill that you'd like to improve in this pull request.
+>
+> **Examples**: Knowledge of a package. A sub-skill, such as creating particle effects. Putting in more hours (effort). Working more efficiently. Time estimation.
+
+> *I want to...*
+
 ### Development Checklist
 
 > Run through the following steps to complete your work.
 
-* [ ] **First draft**. Implement a working first pass at the problem. Try to think modularly, and think of which prefab piece you will modify versus the entire scene.
+* [ ] **Product requirements and game design**. Flesh these out in the corresponding Notion block. Make sure to consider:
+    * [ ] **Model**. What is the user story? (See above.)
+    * [ ] **Action**. How does the player perform actions? What inputs are needed?
+    * [ ] **Rules**. The underlying mechanics.
+    * [ ] **Feedback**. The sensory feedback presented to the player.
+* [ ] **First draft**. Implement a working first pass at the problem. Try to think in modules: modify prefabs instead of the entire scene.
 * [ ] **Final draft**. Once done, perform a general review of `Files changed` and revise anything that needs to be cleaned up.
 
 ### Quality Assurance Checklist
@@ -26,6 +42,8 @@
 * [ ] **Debuggable**. Do you have debug views for the prefabs/systems that you are creating?
 * [ ] **Learnable**. Consider how the player will learn what you implement in this pull request. Are the affordances appropriately communicated with signifiers?
 
+</details>
+
 ## Screen Recording
 
 > Record a quick 5 to 10 second clip of your feature in action.
@@ -42,7 +60,7 @@
 
 > Explain what you did, how you did it, and why you did it. Discuss any lessons that might be useful to others.
 >
-> (Note to self: it's easiest to do a stream-of-consciousness write-up of what you did.)
+> (Note to self: it's easiest to do a stream-of-consciousness write-up of what you did. Remember to write for the *Game Codebase Tour* audience!)
 
 ...
 

.gitignore

@@ -58,10 +58,13 @@ sysinfo.txt
 # Crashlytics generated file
 crashlytics-build.properties
 
-# Third-party stuff that is too big to commit to version control.
+# Third-party stuff that is too big to commit to version control,
+# or shouldn't be exposed publicly because of license clauses.
+Assets/Plugins/ADG_Textures/
 Assets/Plugins/Ciathyza/
+Assets/Plugins/Kevin Iglesias/
+Assets/Plugins/Kevin Iglesias More/
 Assets/Plugins/polyperfect/
-Assets/Plugins/ADG_Textures/
 
 # Mac stuff.
 .DS_Store