Differences

This shows you the differences between two versions of the page.

--- notes:comporg:spring2023 [2023/02/25 19:15] – ["Tic-ify" instructions] abarbcal
+++ notes:comporg:spring2023 [2023/02/25 19:26] (current) – ["Tic-ify" instructions] abarbcal
@@ Line 81: / Line 81: @@
 Once your code is finished and ready, you must use the **Cartridge Data Assembler (CDA)** to integrate it with the rest of the project. This process is referred to as "tic-ify". Most assets of the project are stored in their own separate files, the CDA assembles all the assets together into **one catridge file**.
 Please follow the next steps:
-. Copy your entire code into a text editor, such as VIM or Notepad.
+  - Copy your entire code into a text editor, such as VIM or Notepad.
-. Once copied, you will declare two new functions at the very end of the code. The name of these functions will depend on the system you're working on.
+  - Once copied, you will declare two new functions at the very end of the code. The name of these functions will depend on the system you're working on.
-    i. The first function will include `_init` as a suffix __after the name of the system__. E.g. `[SYSTEM_NAME]_init()`.
+    - The first function will include ''_init'' as a suffix __after the name of the system__. E.g. ''[SYSTEM_NAME]_init()''.
-        - You will move all the code outside of the main `tic()` function inside the `[SYSTEM_NAME]_init()` function. This includes variable declarations, function declarations, classes, etc.
+      * You will move all the code outside of the main ''tic()'' function inside the ''[SYSTEM_NAME]_init()'' function. This includes variable declarations, function declarations, classes, etc.
-    ii. The second function will have the suffix `_loop` after the system's name. E.g. `[SYSTEM_NAME]_loop()`.
+    - The second function will have the suffix ''_loop'' after the system's name. E.g. ''[SYSTEM_NAME]_loop()''.
-        - You will move all the code inside the `tic()` function inside the `[SYSTEM_NAME]_loop()` function.
+      * You will move all the code inside the ''tic()'' function inside the ''[SYSTEM_NAME]_loop()'' function.
-    iii. Enter a new line.
+    - Enter a new line.
-    iv. On the next line (two lines away from the end of `[SYSTEM_NAME]_loop()`), you will call `make_system("[SYSTEM_NAME]",[SYSTEM_NAME]_init,[SYSTEM_NAME]_loop)`
+    - On the next line (two lines away from the end of ''[SYSTEM_NAME]_loop()''), you will call ''make_system("[SYSTEM_NAME]",[SYSTEM_NAME]_init,[SYSTEM_NAME]_loop)''
-    v. Leave a trailing new line.
+    - Leave a trailing new line.
-. Save this file with the name `[SYSTEM_NAME].lua`.
+  - Save this file with the name ''[SYSTEM_NAME].lua''.
-. Include the file in the `code/` directory of the repo.
+  - Include the file in the ''code/'' directory of the repo.
-. Optionally you could "tic-ify" the current version of the game by running the assembler with the command `java -jar ./ticify.jar` at the root of the repo.
+  - Optionally you could "tic-ify" the current version of the game by running the assembler with the command ''java -jar ./ticify.jar'' at the root of the repo.
 __**These instructions have been included in the project's repo.**__
+======Dialogue Proposal Form=====
+he Confrontation System will be a "battle system", where the Player will engage in arguments with PS Officers. During the arguments, the Officer will accuse or interrogate the Player, and the player must choose a response to defend or incriminate themselves. We are seeking out help for dialogue proposals that may be included in this system.
+A Google Form has been created to submit dialogue proposals.
+[[https://forms.gle/qtn8zKuHdsQQXLYd8]]

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools