From 6599051a4dd3f7b72369fec8405028abc714ec90 Mon Sep 17 00:00:00 2001 From: A Crazy Town <47027981+ACrazyTown@users.noreply.github.com> Date: Mon, 26 Apr 2021 23:15:41 +0200 Subject: [PATCH 01/23] Fix the grammar error in README (executible -> executable) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5c916f83..e24ee2fd 100644 --- a/README.md +++ b/README.md @@ -75,7 +75,7 @@ and you should be good to go there. Once you have all those installed, it's pretty easy to compile the game. You just need to run 'lime test html5 -debug' in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) -To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executible file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: +To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: * MSVC v142 - VS 2019 C++ x64/x86 build tools * Windows SDK (10.0.17763.0) * C++ Profiling tools From bc3f718d67f2eb8a21963a420a9a330f2a40d9a7 Mon Sep 17 00:00:00 2001 From: PurpleButNotALight Date: Sat, 8 May 2021 17:15:29 +0200 Subject: [PATCH 02/23] Delete BeatBattle.hx this file was annoying me --- source/BeatBattle.hx | 0 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 source/BeatBattle.hx diff --git a/source/BeatBattle.hx b/source/BeatBattle.hx deleted file mode 100644 index e69de29b..00000000 From dd373f41f94f598de2f3fe0938673660ebef8f84 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Sat, 15 May 2021 02:28:45 -0400 Subject: [PATCH 03/23] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index e24ee2fd..cbc05b8c 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,8 @@ Play the Ludum Dare prototype here: https://ninja-muffin24.itch.io/friday-night- Play the Newgrounds one here: https://www.newgrounds.com/portal/view/770371 Support the project on the itch.io page: https://ninja-muffin24.itch.io/funkin +IF YOU MAKE A MOD AND DISTRIBUTE THE .EXE, YOU MUST OPEN SOURCE YOUR MOD AS WELL + ## Credits / shoutouts - [ninjamuffin99 (me!)](https://twitter.com/ninja_muffin99) - Programmer From b7e18fd0ef505602497b4d5cb0820a44c8adc493 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Sat, 15 May 2021 03:37:09 -0400 Subject: [PATCH 04/23] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cbc05b8c..46e7ae93 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Play the Ludum Dare prototype here: https://ninja-muffin24.itch.io/friday-night- Play the Newgrounds one here: https://www.newgrounds.com/portal/view/770371 Support the project on the itch.io page: https://ninja-muffin24.itch.io/funkin -IF YOU MAKE A MOD AND DISTRIBUTE THE .EXE, YOU MUST OPEN SOURCE YOUR MOD AS WELL +IF YOU MAKE A MOD AND DISTRIBUTE THE .EXE / .APP, YOU MUST OPEN SOURCE YOUR MOD AS WELL ## Credits / shoutouts From e76fd7e0c82e2da347663503e5263352fd6ea0ab Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Sat, 15 May 2021 03:37:33 -0400 Subject: [PATCH 05/23] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 46e7ae93..0083d4e2 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Play the Ludum Dare prototype here: https://ninja-muffin24.itch.io/friday-night- Play the Newgrounds one here: https://www.newgrounds.com/portal/view/770371 Support the project on the itch.io page: https://ninja-muffin24.itch.io/funkin -IF YOU MAKE A MOD AND DISTRIBUTE THE .EXE / .APP, YOU MUST OPEN SOURCE YOUR MOD AS WELL +IF YOU MAKE A MOD AND DISTRIBUTE A MODIFIED / RECOMIPLED VERSION, YOU MUST OPEN SOURCE YOUR MOD AS WELL ## Credits / shoutouts From d2c30e95ed80b8246951482702db89ca8d26248c Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Sat, 15 May 2021 21:32:37 -0400 Subject: [PATCH 06/23] Update LICENSE --- LICENSE | 202 +------------------------------------------------------- 1 file changed, 1 insertion(+), 201 deletions(-) diff --git a/LICENSE b/LICENSE index 261eeb9e..c15eda99 100644 --- a/LICENSE +++ b/LICENSE @@ -1,201 +1 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. +if u make mods, open source them, lol! From 1b2401adfbcc0a57a85f19b9048d79ecb72c880b Mon Sep 17 00:00:00 2001 From: Luke Date: Sun, 23 May 2021 11:15:53 -0400 Subject: [PATCH 07/23] README grammar fixes Because someone had to do it --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 0083d4e2..b597fb43 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Play the Ludum Dare prototype here: https://ninja-muffin24.itch.io/friday-night- Play the Newgrounds one here: https://www.newgrounds.com/portal/view/770371 Support the project on the itch.io page: https://ninja-muffin24.itch.io/funkin -IF YOU MAKE A MOD AND DISTRIBUTE A MODIFIED / RECOMIPLED VERSION, YOU MUST OPEN SOURCE YOUR MOD AS WELL +IF YOU MAKE A MOD AND DISTRIBUTE A MODIFIED / RECOMPILED VERSION, YOU MUST OPEN SOURCE YOUR MOD AS WELL ## Credits / shoutouts @@ -14,7 +14,7 @@ IF YOU MAKE A MOD AND DISTRIBUTE A MODIFIED / RECOMIPLED VERSION, YOU MUST OPEN - [PhantomArcade3K](https://twitter.com/phantomarcade3k) and [Evilsk8r](https://twitter.com/evilsk8r) - Art - [Kawaisprite](https://twitter.com/kawaisprite) - Musician -This game was made with love to Newgrounds and it's community. Extra love to Tom Fulp. +This game was made with love to Newgrounds and its community. Extra love to Tom Fulp. ## Build instructions @@ -28,11 +28,11 @@ IF YOU WANT TO COMPILE THE GAME YOURSELF, CONTINUE READING!!! ### Installing the Required Programs -First you need to install Haxe and HaxeFlixel. I'm too lazy to write and keep updated with that setup (which is pretty simple). +First, you need to install Haxe and HaxeFlixel. I'm too lazy to write and keep updated with that setup (which is pretty simple). 1. [Install Haxe 4.1.5](https://haxe.org/download/version/4.1.5/) (Download 4.1.5 instead of 4.2.0 because 4.2.0 is broken and is not working with gits properly...) 2. [Install HaxeFlixel](https://haxeflixel.com/documentation/install-haxeflixel/) after downloading Haxe -Other installations you'd need is the additional libraries, a fully updated list will be in `Project.xml` in the project root. Currently, these are all of the things you need to install: +Other installations you'd need are the additional libraries, a fully updated list will be in `Project.xml` in the project root. Currently, these are all of the things you need to install: ``` flixel flixel-addons @@ -50,15 +50,15 @@ You'll also need to install a couple things that involve Gits. To do this, you n You should have everything ready for compiling the game! Follow the guide below to continue! -At the moment, you can optionally fix the transition bug in songs with zoomed out cameras. +At the moment, you can optionally fix the transition bug in songs with zoomed-out cameras. - Run `haxelib git flixel-addons https://github.com/HaxeFlixel/flixel-addons` in the terminal/command-prompt. ### Ignored files -I gitignore the API keys for the game, so that no one can nab them and post fake highscores on the leaderboards. But because of that the game +I gitignore the API keys for the game so that no one can nab them and post fake high scores on the leaderboards. But because of that the game doesn't compile without it. -Just make a file in `/source` and call it `APIStuff.hx`, and copy paste this into it +Just make a file in `/source` and call it `APIStuff.hx`, and copy-paste this into it ```haxe package; @@ -92,7 +92,7 @@ To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. * MSVC v141 - VS 2017 C++ x64/x86 build tools * MSVC v140 - VS 2015 C++ build tools (v14.00) -This will install about 22GB of crap, but once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin +This will install about 22GB of crap, but once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher-end PC), you can run FNF from the .exe file under export\release\windows\bin As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. ### Additional guides From 407c92dd391b77c4a0d7d5478129692bb23ce0e9 Mon Sep 17 00:00:00 2001 From: MisterAlexanderB <79173370+MisterAlexanderB@users.noreply.github.com> Date: Sun, 8 Aug 2021 17:10:06 -0400 Subject: [PATCH 08/23] Describe what the txt file is for because why not --- assets/fonts/fonts-go-here.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/assets/fonts/fonts-go-here.txt b/assets/fonts/fonts-go-here.txt index e69de29b..762afd6d 100644 --- a/assets/fonts/fonts-go-here.txt +++ b/assets/fonts/fonts-go-here.txt @@ -0,0 +1 @@ +You should know what this is for by the title of what it is called. From ff30a3f5b821492790642e05345730c16792b2b1 Mon Sep 17 00:00:00 2001 From: Luke Date: Thu, 19 Aug 2021 15:58:37 -0400 Subject: [PATCH 09/23] =?UTF-8?q?Change=20=E2=80=9Ccopy-paste=E2=80=9D=20t?= =?UTF-8?q?o=20=E2=80=9Ccopy=20&=20paste=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Makes things a bit more clear Co-authored-by: Julian Holfeld --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b597fb43..64babb5f 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,7 @@ At the moment, you can optionally fix the transition bug in songs with zoomed-ou I gitignore the API keys for the game so that no one can nab them and post fake high scores on the leaderboards. But because of that the game doesn't compile without it. -Just make a file in `/source` and call it `APIStuff.hx`, and copy-paste this into it +Just make a file in `/source` and call it `APIStuff.hx`, and copy & paste this into it ```haxe package; From 0267db86444af0701ce3db43d44759f495933cb2 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Thu, 19 Aug 2021 22:51:21 -0400 Subject: [PATCH 10/23] clean up bug template --- .github/ISSUE_TEMPLATE/bug.md | 29 ++++++++++++++++++++++------- 1 file changed, 22 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md index cc4d5b11..4c701be2 100644 --- a/.github/ISSUE_TEMPLATE/bug.md +++ b/.github/ISSUE_TEMPLATE/bug.md @@ -1,21 +1,36 @@ --- name: Bug Report about: Report a bug or critical performance issue -title: 'Bug Report: ' +title: 'Bug Report: [DESCRIBE YOUR BUG IN DETAIL HERE]' labels: bug --- + +[weed]: <> (FILL THIS ISSUE THING OUT AS MUCH AS POSSIBLE) +[weed]: <> (OR ELSE YOUR ISSUE WILL BE LESS LIKELY TO BE SOLVED!) + #### Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue. ### If you are playing the game in a browser, what site are you playing it from? -[Newgrounds](https://www.newgrounds.com/portal/view/770371) or [Itch.io](https://ninja-muffin24.itch.io/funkin)? Specify below. + +[weed]: <> (Put an X in the [ ] thingies to fill out checkbox!) +[weed]: <> (something like [x] pretty much, don't screw up or you will look stupid) + +- [ ] [Newgrounds](https://www.newgrounds.com/portal/view/770371) +- [ ] [Itch.io](https://ninja-muffin24.itch.io/funkin)? Specify below +- - [ ] Windows +- - [ ] Mac +- - [ ] Linux ### If you are playing the game in a browser, what browser are you using? -Chrome (or a Chromium based browser, i.e. Edge, Opera, etc.), Firefox, or Safari? Specify blow. -### If you are playing a downloaded version of the game, what operating system are you using? -Windows (`x86`), Windows (`x86_64`), Linux, or macOS? Specify below. +[weed]: <> (Again, put an x in the [ ] box!) -## What version of the game are you using? Look in the bottom left corner of the main menu. +- [ ] Google Chrome (or chomium based like Brave, vivaldi, MS Edge) +- [ ] Firefox +- [ ] Safari -## Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible. +## What version of the game are you using? Look in the bottom left corner of the main menu. (ex: 0.2.7, 0.2.1, shit like that) + + +## Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible. ## Please describe your issue. Provide extensive detail and images if possible. From 7872fea94c0a80e3d1edbd23809733092feb8f1e Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Thu, 19 Aug 2021 22:52:15 -0400 Subject: [PATCH 11/23] Update bug.md --- .github/ISSUE_TEMPLATE/bug.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md index 4c701be2..8d21888e 100644 --- a/.github/ISSUE_TEMPLATE/bug.md +++ b/.github/ISSUE_TEMPLATE/bug.md @@ -7,6 +7,8 @@ labels: bug [weed]: <> (FILL THIS ISSUE THING OUT AS MUCH AS POSSIBLE) [weed]: <> (OR ELSE YOUR ISSUE WILL BE LESS LIKELY TO BE SOLVED!) +[weed]: <> (DO NOT POST ABOUT ISSUES FROM OTHER FNF MOD ENGINES! I CANNOT AND PROBABLY WON'T SOLVE THOSE!) +[weed]: <> (GO TO THEIR RESPECTIVE GITHUB ISSUES AND REPORT THEM THERE LOL!) #### Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue. ### If you are playing the game in a browser, what site are you playing it from? From 4f39d000004b73e56bfb5266de16fd33a59ce602 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Thu, 19 Aug 2021 23:05:49 -0400 Subject: [PATCH 12/23] Update bug.md --- .github/ISSUE_TEMPLATE/bug.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md index 8d21888e..4c715dd3 100644 --- a/.github/ISSUE_TEMPLATE/bug.md +++ b/.github/ISSUE_TEMPLATE/bug.md @@ -10,6 +10,8 @@ labels: bug [weed]: <> (DO NOT POST ABOUT ISSUES FROM OTHER FNF MOD ENGINES! I CANNOT AND PROBABLY WON'T SOLVE THOSE!) [weed]: <> (GO TO THEIR RESPECTIVE GITHUB ISSUES AND REPORT THEM THERE LOL!) +[weed]: <> (ALSO MAKE SURE THAT YOU USE PROPER LABELS, IF YOU'RE RUNNING INTO COMPILER ISSUES, USE THE compiler issue LABEL!!!) + #### Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue. ### If you are playing the game in a browser, what site are you playing it from? From 455b690d8ac9f5ddada3765ebb9ae8be96f4fb0b Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Thu, 19 Aug 2021 23:16:55 -0400 Subject: [PATCH 13/23] revert to apache 2.0 lol! STILL OPEN SOURCE YOUR MODS YOU GOONS --- LICENSE | 202 +++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 201 insertions(+), 1 deletion(-) diff --git a/LICENSE b/LICENSE index c15eda99..4c9ad980 100644 --- a/LICENSE +++ b/LICENSE @@ -1 +1,201 @@ -if u make mods, open source them, lol! + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. From ceeb5fefd956aa0e7fa02bdb74f149573f6f15f6 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Thu, 19 Aug 2021 23:39:59 -0400 Subject: [PATCH 14/23] readme install cleanup closes #881 I am merely trusting that one commit from kade engine that this is accurate, im too lazy to test myself --- README.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/README.md b/README.md index 0083d4e2..f8ecf583 100644 --- a/README.md +++ b/README.md @@ -80,19 +80,8 @@ Once you have all those installed, it's pretty easy to compile the game. You jus To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: * MSVC v142 - VS 2019 C++ x64/x86 build tools * Windows SDK (10.0.17763.0) -* C++ Profiling tools -* C++ CMake tools for windows -* C++ ATL for v142 build tools (x86 & x64) -* C++ MFC for v142 build tools (x86 & x64) -* C++/CLI support for v142 build tools (14.21) -* C++ Modules for v142 build tools (x64/x86) -* Clang Compiler for Windows -* Windows 10 SDK (10.0.17134.0) -* Windows 10 SDK (10.0.16299.0) -* MSVC v141 - VS 2017 C++ x64/x86 build tools -* MSVC v140 - VS 2015 C++ build tools (v14.00) -This will install about 22GB of crap, but once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin +Once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. ### Additional guides From cd9af8b40835033c2c151e83db3f4b6dbb692e47 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Fri, 20 Aug 2021 00:02:28 -0400 Subject: [PATCH 15/23] Update bug.md --- .github/ISSUE_TEMPLATE/bug.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md index 4c715dd3..efa81b56 100644 --- a/.github/ISSUE_TEMPLATE/bug.md +++ b/.github/ISSUE_TEMPLATE/bug.md @@ -38,3 +38,7 @@ labels: bug ## Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible. ## Please describe your issue. Provide extensive detail and images if possible. + + + +## If you're game is FROZEN and you're playing a web version, press F12 to open up browser dev window, and go to console, and copy-paste whatever red error you're getting From ff5135bb90d8f954a131a24982e647bc1480c415 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Fri, 20 Aug 2021 00:12:31 -0400 Subject: [PATCH 16/23] Create compiling.md --- .github/ISSUE_TEMPLATE/compiling.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/compiling.md diff --git a/.github/ISSUE_TEMPLATE/compiling.md b/.github/ISSUE_TEMPLATE/compiling.md new file mode 100644 index 00000000..14aea44a --- /dev/null +++ b/.github/ISSUE_TEMPLATE/compiling.md @@ -0,0 +1,25 @@ +--- +name: Compiling help +about: If you need help compiling the game, and you're running into issues. (Look through the 'compiling help' label in case it's been solved!) +title: 'Compiling help: [BRIEF DESCRIPTION / ERROR MESSAGE OUTPUT]' +labels: compiling help +--- + +[weed]: <> (FILL THIS ISSUE THING OUT AS MUCH AS POSSIBLE) +[weed]: <> (OR ELSE YOUR ISSUE WILL BE LESS LIKELY TO BE SOLVED!) +[weed]: <> (DO NOT POST ABOUT ISSUES FROM OTHER FNF MOD ENGINES! I CANNOT AND PROBABLY WON'T SOLVE THOSE!) +[weed]: <> (GO TO THEIR RESPECTIVE GITHUB ISSUES AND REPORT THEM THERE LOL!) + +#### Please check for duplicates or similar compiler issues by filtering for 'compiler help' + +[weed]: <> (Put an X in the [ ] thingies to fill out checkbox!) +[weed]: <> (something like [x] pretty much, don't screw up or you will look stupid) + + +- [ ] Windows +- [ ] Mac +- [ ] Linux +- [ ] HTML5 + +## Please describe your issue. Provide extensive detail and images if possible. + From 5ea3602c62f4c6e65194c36b1c7470a3d3c55a5a Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Fri, 20 Aug 2021 00:20:53 -0400 Subject: [PATCH 17/23] Update question.md --- .github/ISSUE_TEMPLATE/question.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md index 0adb3cc2..a257c217 100644 --- a/.github/ISSUE_TEMPLATE/question.md +++ b/.github/ISSUE_TEMPLATE/question.md @@ -4,5 +4,9 @@ about: Ask a general question title: 'Question: ' labels: question --- + +[weed]: <> (This isn't a place for AMA type questions, if you want to ask any of the devs something, reach out to them on twitter prob ) +[weed]: <> (any biz bullshit can go to cameron.taylor.ninja@gmail.com) + #### Please check for duplicates or similar issues before asking your question. ## What is your question? From c0204924cfdb862949ab305f3d18e6eb6ede95d7 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Wed, 25 Aug 2021 19:56:52 -0400 Subject: [PATCH 18/23] Update README.md --- README.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 64babb5f..956faa7e 100644 --- a/README.md +++ b/README.md @@ -78,22 +78,11 @@ and you should be good to go there. Once you have all those installed, it's pretty easy to compile the game. You just need to run 'lime test html5 -debug' in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: -* MSVC v142 - VS 2019 C++ x64/x86 build tools -* Windows SDK (10.0.17763.0) -* C++ Profiling tools -* C++ CMake tools for windows -* C++ ATL for v142 build tools (x86 & x64) -* C++ MFC for v142 build tools (x86 & x64) -* C++/CLI support for v142 build tools (14.21) -* C++ Modules for v142 build tools (x64/x86) -* Clang Compiler for Windows -* Windows 10 SDK (10.0.17134.0) -* Windows 10 SDK (10.0.16299.0) -* MSVC v141 - VS 2017 C++ x64/x86 build tools -* MSVC v140 - VS 2015 C++ build tools (v14.00) -This will install about 22GB of crap, but once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher-end PC), you can run FNF from the .exe file under export\release\windows\bin -As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. + MSVC v142 - VS 2019 C++ x64/x86 build tools + Windows SDK (10.0.17763.0) + +Once that is done you can open up a command line in the project's directory and run lime test windows -debug. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. ### Additional guides From 1b382f9aa3bf2209e73022040adb8e2041fc11fd Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Wed, 25 Aug 2021 19:57:53 -0400 Subject: [PATCH 19/23] lol erm awkward markdown thing!!! --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 956faa7e..9082b3e3 100644 --- a/README.md +++ b/README.md @@ -76,13 +76,12 @@ and you should be good to go there. ### Compiling game Once you have all those installed, it's pretty easy to compile the game. You just need to run 'lime test html5 -debug' in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) - To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: +* MSVC v142 - VS 2019 C++ x64/x86 build tools +* Windows SDK (10.0.17763.0) - MSVC v142 - VS 2019 C++ x64/x86 build tools - Windows SDK (10.0.17763.0) - -Once that is done you can open up a command line in the project's directory and run lime test windows -debug. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. +Once that is done you can open up a command line in the project's directory and run `lime test windows -debug`. Once that command finishes (it takes forever even on a higher end PC), you can run FNF from the .exe file under export\release\windows\bin +As for Mac, 'lime test mac -debug' should work, if not the internet surely has a guide on how to compile Haxe stuff for Mac. ### Additional guides From 6f433977769571c9e758e2e9e8ea73553d55fadb Mon Sep 17 00:00:00 2001 From: AbnormalPoof <86753001+AbnormalPoof@users.noreply.github.com> Date: Mon, 13 Sep 2021 21:50:10 -0500 Subject: [PATCH 20/23] add notice to build section and also fix formatting for build commands since it was off putting --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9082b3e3..d6e748ea 100644 --- a/README.md +++ b/README.md @@ -74,9 +74,10 @@ class APIStuff and you should be good to go there. ### Compiling game +NOTE: If you see any messages relating to deprectated packages, ignore them. They're just warnings that don't affect compiling -Once you have all those installed, it's pretty easy to compile the game. You just need to run 'lime test html5 -debug' in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) -To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run 'lime test linux -debug' and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: +Once you have all those installed, it's pretty easy to compile the game. You just need to run `lime test html5 -debug` in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) +To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run `lime test linux -debug` and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: * MSVC v142 - VS 2019 C++ x64/x86 build tools * Windows SDK (10.0.17763.0) From 121b8d6c4552daeac140fdb6eb506d7049c84e3e Mon Sep 17 00:00:00 2001 From: AbnormalPoof <86753001+AbnormalPoof@users.noreply.github.com> Date: Mon, 13 Sep 2021 22:00:00 -0500 Subject: [PATCH 21/23] also i apparently cant spell lmao --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d6e748ea..9969efc4 100644 --- a/README.md +++ b/README.md @@ -74,7 +74,7 @@ class APIStuff and you should be good to go there. ### Compiling game -NOTE: If you see any messages relating to deprectated packages, ignore them. They're just warnings that don't affect compiling +NOTE: If you see any messages relating to deprecated packages, ignore them. They're just warnings that don't affect compiling Once you have all those installed, it's pretty easy to compile the game. You just need to run `lime test html5 -debug` in the root of the project to build and run the HTML5 version. (command prompt navigation guide can be found here: [https://ninjamuffin99.newgrounds.com/news/post/1090480](https://ninjamuffin99.newgrounds.com/news/post/1090480)) To run it from your desktop (Windows, Mac, Linux) it can be a bit more involved. For Linux, you only need to open a terminal in the project directory and run `lime test linux -debug` and then run the executable file in export/release/linux/bin. For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following: From 8f77095233dbf0bfd491b2ca979267c37abd8c41 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Wed, 14 Sep 2022 17:38:04 -0400 Subject: [PATCH 22/23] Update introText.txt --- assets/preload/data/introText.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/assets/preload/data/introText.txt b/assets/preload/data/introText.txt index 8e2a6ba8..e9323737 100644 --- a/assets/preload/data/introText.txt +++ b/assets/preload/data/introText.txt @@ -39,3 +39,4 @@ pico funny--pico funny updates each friday--on time every time shoutouts to mason--for da homies bonk--get in the discord call +github excluseive intro text--open source forever From 9780a415221eb2922a7243313a84ca42025ccca0 Mon Sep 17 00:00:00 2001 From: Cameron Taylor Date: Wed, 14 Sep 2022 17:38:30 -0400 Subject: [PATCH 23/23] Update introText.txt --- assets/preload/data/introText.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/preload/data/introText.txt b/assets/preload/data/introText.txt index e9323737..44f02b3a 100644 --- a/assets/preload/data/introText.txt +++ b/assets/preload/data/introText.txt @@ -39,4 +39,4 @@ pico funny--pico funny updates each friday--on time every time shoutouts to mason--for da homies bonk--get in the discord call -github excluseive intro text--open source forever +github exclusive intro text--open source forever