Initial commit

.gitignore

@@ -0,0 +1,120 @@
+# ---> Node
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+.pnpm-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+.env.production
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
+

LICENSE

@@ -0,0 +1,29 @@
+THE SUBWAY MANIFESTO
+
+* I PLEDGE TO ALWAYS WRITE SIMFILES TO THE BEST OF MY ABILITY
+* I WILL ALWAYS CHOOSE QUALITY MUSIC WHENEVER POSSIBLE
+* I BELIEVE THAT THE PLAYER CAN BE CHALLENGED WITHOUT COMPROMISING ON WHAT IS "FUN"
+* I AM CREATIVE AND ORGANIZED AND THESE TRAITS ARE APPARENT IN MY SIMFILES
+* I WILL NEVER REDUCE MY CHARTS TO BORING "STEP RHETORIC" EVEN WHEN THAT IS POPULAR
+* I BELIEVE THAT GOOD MUSIC IS AN IMPORTANT COMPONENT OF A GOOD CHART
+* I CAN WRITE CHARTS THAT ARE FOR PLAYERS OF ANY EXPERIENCE LEVEL INCLUDEING THE PROS
+* I AM NOT AFRAID TO USE STREAM OR A RUN, SLOW DOWNS, OR FOOT SPEED
+* I AM FAMILIAR WITH CHARTING STYLES OF OLD AND NEW AND I CAN BRING THE BEST OF BOTH WORLDS
+* I WILL NOT RELEASE A FILE IF I AM NOT HAPPY WITH IT
+* I UNDERSTAND THAT GOOD SIMFILES TAKE TIME TO WRITE
+* I DO NOT RELEASE FILES WITH THE HOPE OF BEING POPULAR BUT BECAUSE I KNOW WE NEED GOOD SIMFILES
+* I WRITE FILES THE WAY I WANT TO WRITE THEM AND NOT WHAT SOMEONE ELSE THINKS
+* I AM WILLING TO HELP OTHERS AND BE A GOOD EXAMPLE THROUGH MY CHARTS
+* I UNDERSTAND THE IMPORTANCE OF ACCESSIBILITY WHICH IS WHY I MAKE CHARTS COMPATIBILE WITH ALL STEPMANIAS
+* I WILL NEVER WRITE CROSSOVERS THAT DON'T RESOLVE UNLESS IT IS ARTISTIC
+* I HAVE STUDIED THE FORMAT OF DDR AND ITG SIMFILES AND I KNOW HOW TO MAKE THEM BETTER
+* I NEVER FORGET TO SET THE PREVIEW, MUSIC GRAPHICS, OR THE CD TITLE
+* I KNOW A GOOD CHART WHEN I SEE ONE AND I FORM MY OWN OPINIONS
+* I CAN WRITE FILES TO MAKE THE PLAYERS BETTER AT THE GAME BECAUSE I KNOW WHAT IS GOOD FOR THEM
+* I WILL INCLUDE THE SUBWAY MANIFESTO IN MY CHARTS TO HOLD MYSELF ACCOUNTABLE TO THE TRUTH
+
+THE INCLUSION OF THE SUBWAY MANIFESTO IS A PLEDGE OF QUALITY
+
+INCLUDE THIS IN YOUR SIMFILES IF YOU AGREE 
+
+THIS WAY PLAYERS CAN BE SURE TO PICK OUT QUALITY CHARTS SIMPLY BY LOCATING THE SUBWAY MANIFESTO (CTRL+F)

README.md

@@ -0,0 +1,3 @@
+# draw
+
+640x480 image that you can draw by sending a request (a bad idea)