🐟 East Games United game jam!
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
assets
core
desktop
gradle/wrapper
raw
.gitignore
README.md
build.gradle
gradle.properties
gradlew
gradlew.bat
settings.gradle

README.md

East Games United game jam

Become the king of the ocean!

Control your swarm of herrings! Eat the smaller fish, grow bigger. Be careful - the red ones are trying to stop you.

Menu Game Loss

About

Created in under 30 hours using KTX during the East Games United game jam by three two and half Java backend developers and one cute graphics designer. The jam's topic was "śledź" ("herring") and this one of the games that we came up. The other one is here. We ended up on the third place, which isn't that bad.

Note: we were desperate and sleep deprived. This ain't your Uncle Bob coding exercise. Don't judge us by this code.

Gradle

This project uses Gradle to manage dependencies. Gradle wrapper was included, so you can run Gradle tasks using gradlew.bat or ./gradlew commands. Useful Gradle tasks and flags:

  • --continue: when using this flag, errors will not stop the tasks from running.
  • --daemon: thanks to this flag, Gradle daemon will be used to run chosen tasks.
  • --offline: when using this flag, cached dependency archives will be used.
  • --refresh-dependencies: this flag forces validation of all dependencies. Useful for snapshot versions.
  • build: builds sources and archives of every project.
  • cleanEclipse: removes Eclipse project data.
  • cleanIdea: removes IntelliJ project data.
  • clean: removes build folders, which store compiled classes and built archives.
  • desktop:jar: builds application's runnable jar, which can be found at desktop/build/libs.
  • desktop:run: starts the application.
  • eclipse: generates Eclipse project data.
  • idea: generates IntelliJ project data.
  • test: runs unit tests (if any).

Note that most tasks that are not specific to a single project can be run with name: prefix, where the name should be replaced with the ID of a specific project. For example, core:clean removes build folder only from the core project.