Skip to content

Commit

Permalink
TacO not Taco
Browse files Browse the repository at this point in the history
  • Loading branch information
HexedHero authored Jan 26, 2024
1 parent f2c1bb5 commit 58664f6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Setting this system up is extremely simple.
* **Step 1.** Click "Use this template" -> "Create a new repository" and enter your repository name, description etc.
* **Step 2.** Change Variables within the repository:
* **Step 2.1**. Open ".github\workflows\build_and_release.yml" and change the variable "OUTPUT_NAME" to be the name of your marker pack such as "OUTPUT_NAME: example" will output a file called example.taco on release.
* **Step 2.2**. Open "install.bat" and change the two variables near the top of the file. One is called "targetLocation" which is the path of where your marker packs are loaded from Taco or Blish HUD, this is where the script will install your marker pack to be tested. Finally, change the "fileName" variable to be the name of your marker pack, it ideally should match with the above changed "OUTPUT_NAME".
* **Step 2.2**. Open "install.bat" and change the two variables near the top of the file. One is called "targetLocation" which is the path of where your marker packs are loaded by TacO or Blish HUD, this is where the script will install your marker pack to be tested. Finally, change the "fileName" variable to be the name of your marker pack, it ideally should match with the above changed "OUTPUT_NAME".
* **Step 3.** Change README.md to fit your marker pack.


Expand Down

0 comments on commit 58664f6

Please sign in to comment.